I'm no longer running 10.3 on a machine that I can build on. I can test if something built on 10.4 will run on a 10.3 machine.
I have just built Enigma on a 32-bit Intel MacBook and it did run ok. The enigma.dmg was a little more than half the size than the disk space used by the app. Is there something else about the compression that I don't know about? I built according to the instructions using make and then mac macapp. I don't see where it is doing anything to put the documentation into the dmg it produces. The resulting application is Intel only. I've forgotten the procedure to make a Universal build of Enigma. Is that still a manual process? We should add to REAME.macosx instructions for producing a universal build. Until I can do that I can't test my build on a 10.3 machine, as I'm building on Intel and running 10.3 on PPC. I have attached a patch for doc/README.macosx that reflects my experiences getting the latest svn trunk to build on my machine. -- sidney
Index: doc/README.macosx =================================================================== --- doc/README.macosx (revision 694) +++ doc/README.macosx (working copy) @@ -22,11 +22,48 @@ for building Enigma. Neither have we tried the older version of Fink that runs on 10.3.9. -Note that you may need to follow step 6(a) below for building the -static library libxerces-c.a even after installing Xerces-c from Fink -or DarwinPorts. The default distribution of Xerces-c does not as of -this moment provide for building a static library under MacOS. +As of this writing, xerces-c is only in the unstable package tree of +fink. The fink FAQ describes how to temporarily switch to using +unstable so that you can install a package from there even though you +are in general using the stable tree. +The Fink install of Xerces-c does not build the static library +libxerces-c.a so the following additional steps are necessary. + +1. If you have not yet installed xerces-c, install it and some +associated packages using the -k option to keep the build directories +for a later step: + + fink -k install xerces-c xerces-c-dev xerces-c-shlibs + +If you already installed them, rebuild the using the -k option + + fink -k rebuild xerces-c xerces-c-dev xerces-c-shlibs + +2. The xerces-c source tree can now be found under /sw/src/fink.build/ +in a directory that corresponds to the version of xerces that you +installed. cd to it and set the XERCESCROOT environment variable as in +the following example: + + cd /sw/src/fink.build/ xerces-c-2.7.0-1002/xerces-c-src_2_7_0 + export XERCESCROOT=`pwd` + +Put the following in an executable file in the +$XERCESCROOT/src/xercesc directory, cd to that directory and run it, +using sudo if fink is configured to always build as root. + + #!/bin/sh + make -n XML_LIB_DIR=$XERCESCROOT/lib/dummy | + grep 'c++ .*\.dylib' | + tr \ \\n | + grep '\.o$' | + ( cd ../../obj ; xargs ar rcs $XERCESCROOT/lib/libxerces-c.a ) + +Then + + sudo cp $XERCESCROOT/lib/libxerces-c.a /sw/lib/ + sudo ranlib /sw/lib/libxerces-c.a + If you do use Fink or DarwinPorts, as long as the required additional libraries are consistently placed in the same directory, e.g., /usr/fink/lib, then the Enigma build scripts should work. There will
_______________________________________________ Enigma-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/enigma-devel
