On 14/06/2006, at 5:52 AM, Joey Mukherjee wrote:
> I know its been a while, but I am just now getting back to this...
> See below:
> On May 19, 2006, at 2:02 AM, Steve Landers wrote:
>>> yes, i386 only; recent critcl has an option to build universal
>>> binaries, if that's not in critcl CVS yet, Steve Landers can tell
>>> you where to get it...
>> I still haven't integrated it with the Critcl CVS, so it is still
>> "pre-release" but nevertheless useful :)
>> You can get it from http://www.digitalsmarties.com/pub/critcl-new.kit
>> You'll need to select the appropriate target via the -target flag
>> critcl -target universal-macosx -pkg yourpkg
>> The config definitions are stored in critcl.vfs/lib/critcl/Config -
>> if you find the build options need tweaking.
>> Although it is pre-release, I've used it to build the various
>> Critcl packages I have here - including Cryptkit, Muze, busy and
>> bgexec, on a variety of platforms (OSX, OSX x-compile for win32,
>> Linux, Linux x-compile for arm, Windows using mingw).
> Ok, I tried this and no luck. I am trying to create a universal
> build of tclCarbonProcesses and it will not build a universal dylib
> for nothing. I had to change the Config file to add in -arch's since
> -i386 and -ppc did not work.
The framework is there for universal binary support, but clearly we
haven't got the right cmdline args yet.
> I also had to add a -framework Carbon
> so it would compile and link, but the resulting binary .dylib is not
> a universal one. I feel like the compiling was working, but in the
> link phase, it just links the single platform.
It's best to use the framework command in your application instead of
changing the config ...
> Does anyone have any idea what I might be doing wrong? Is there a
> way to make the critcl-new.kit echo the command line it is using?
you could try "critcl -show", or look at the log file in ~/.critcl/
powerpc-macosx (assuming you are building on a PPC). I'll make a note
to implement a "-trace" flag to output the commands to stderr too.
I won't get a chance to look at universal binary support for a little
while longer, so I'd appreciate if anyone with experience in that
area can pass on the correct command line arguments (both for the
compile and link phase).