On Feb 3, 2005, at 20:07, Chris Barker wrote:
Bob Ippolito wrote:
You have three options:
- make sure the dylibs aren't sitting around in the same location as the .a, and make sure the .a's path is preferred (you could make a local dir, -L to it, symlink the archives in)
I'm going to give this a try.
- change the setup.py relatively significantly and specify them as object files with their full path
This strikes me as very non-portable. Ideally, I'd like to be able to easily re-do this whenever a new version comes out, and even have it be in the standard distro's setup.py
it works with any GCC on any platform...
- don't link statically and install the dylibs too, somehow (possibly by building+installing them with --prefix=/Library/Python/2.3/matplotlib/lib-dynload/ and -L to that when linking.. note that this would require a bdist_mpkg subclass to make a .pkg out of it)
This may be a good option, but then I'd need to figure out bdist_mpkg. I don't suppose you're volunteering?
Not for at least a week or two... it would be a Good Thing To Support in general, but I have other things on my plate.
By the way, how can I tell what a given lib I've just built is expecting to link against? I can do this with ldd on linux.
otool -L
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
