As far as I can see, all the Unicode stuff is in the CoreFoundation
framework, and it does not seem good to me to install a different and
possibly incompatible unicode framework. I am very much trying to work
towards a version of Swarm which will compile and run on a MacOS X
system
with the minimum modification. Nirvana would be to end up with a Swarm
framework which can be installed and then used to build apps in Project
Builder using it, the AppKit framework and not much else.
I try to keep modifications to pre-release versions of software which
Apple intends to ship - such as the gcc3.1 compiler. If I build a
compiler incorporating libiconv it will be different to the standard
Apple
3.1 compiler which will ship with Jaguar and that may give me problems
down the track.
The obvious exception to this principle is XFree86 which is necessary
right now because of the version incompatablilities between tcl/tk Aqua
and BLT.
Bill Northcott
address@hidden wrote on 02/07/2002 01:05:47 PM:
Ok,
I've just uploaded libiconv and can be downloaded right now.
On Monday, July 1, 2002, at 08:49 PM, address@hidden wrote:
Hi Jacobo
Further to that last message about the problem with your compiler I
have
checked two different computers and libiconv.2.dylib does not exist
anywhere on either of them. They are both running gcc3-1147 which I
compiled this morning.
Do you know where that library came from?
libiconv is not absolutely necessary to compile gcc, but is
recommended.
Bill Northcott
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.