On Mar 4, 2:29 am, Uberman <bhoo...@hotmail.com> wrote: > Graham Dumpleton wrote: > > Why don't you want to use MacOS X Framework libraries? It is the > > better installation method. > > Because I'm not installing Python, I'm building it. If I were just interested > in installing Python, I wouldn't care whether it was static or shared > libraries. > > This is all very specific to my product. We are not just OS X, but Windows > and Linux as well. Because of this, we use an SDK/ folder that has all the > third-party dependencies contained within it (in a non-platform way). > Frameworks are OS X-specific. I build Python within its distribution folder, > and then package that same folder up into an archive that gets deposited into > the SDK/ folder. The product then builds against that.
I don't understand the problem, you can say where it installs the framework, it doesn't have to be under /Library, so can be in your special SDK folder. For example: ./configure --prefix=/usr/local/python-2.5.4 \ --enable-framework=/usr/local/python-2.5.4/frameworks \ --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.5 \ --with-universal-archs=all This would put stuff under /usr/local/python-2.5.4. The only thing am not sure about though is what happens to some MacOS X .app stuff it tries to install. I vaguely remember it still tried to install them elsewhere, so may have to disable them being installed somehow. Graham -- http://mail.python.org/mailman/listinfo/python-list
