On 24.02.2013 14:55, ecir hana wrote:

On Sun, Feb 24, 2013 at 2:30 PM, M.-A. Lemburg mal@egenix.com wrote:

...

Something is wrong here: the library is usually called something like "libpython3.3m.a".

There was "libpython3.3.dylib" which is a symlink to "Python" which I renamed to "python33" so it does not collide with installed "Python" v2.7. I also tried "python33.dylib", "libpython33", "libpython33.dylib", "libpython33.so" to no avail...

Sorry, I can't help with the versions from the Python installer on python.org. Both the Apple provided and the python.org versions have given us too much trouble in the past. We're always compiling our own versions, try to avoid fat binaries and use default settings when compiling Python.

Btw, why ".a"? I thought that for static linking. The binary distribution from python.org only contains some dylibs...

The .a libs are indeed for static linking. You can try to use dylibs for your application, but chances are high that your users will run into problems picking up a dylib from one of the many sources for this file (Apple's Python lib, python.org installer, MacPorts, Homebrew, Fink, etc.). Each of those will likely have been compiled using slightly different settings or even come with internal changes.

You can avoid all that by doing static linking.

Please make sure that you actually have the correct library in

...

your current directory.

I think I have - it just those 3 files from above in the directory.

"gcc -lname" will look for a file libname.a or libname.dylib. Please see the man page for details.