|
If you want to use the SilverCity stuff on Mac OS X Jaguar and use the default Python 2.2, you need to fix some problem Apple introduced into their base Makefile that is used for extension building.
You need to edit /usr/lib/python2.2/config/Makefile and remove a -arch i386 parameter that is given in addition to the correct -arch ppc parameter in the LDFLAGS= line.
This is only needed with the Apple supplied python 2.2. There is another problem in the Makefile: extensions are linked with CC not CXX. This creates problems if you want to integrate C++ written modules like SilverCity. You can change that in the config Makefile, too. Look for the LDSHARED= and BLDSHARED= lines and change the $(CC) to $(CXX). This patch might be needed for selfcompiled pythons, too.
The latter change shouldn't pose a problem, as C extensions should just not pull in any stuff from the C++ default libraries, but to be sure you can switch the LDSHARED and BLDSHARED definitions back to their original state after compiling and installing SilverCity.
Please remember that these are only instructions for Python 2.2 - there might be differences with Python 2.3 to get SilverCity running!
I added a way to PyDS to run without SilverCity installed so only people wanting this feature need to jump through those hoops (others won't be able to use code-block, though - but they still can use the pycode directive).
Some links on this stuff:
|
