I'm just getting started with python, so I'm certainly not qualified to comment
on this specific problem. However, perhaps the following page may be useful to
others getting started with python:
http://wolfpaulus.com/journal/mac/installing_python_osx
The site gives detailed instructions on ins
Marco S Hyman, Stephen J. Butler,
thanks a lot! Indeed, stupid me, I was missing "-L.". I used to use it (as
I copy-pasted above) but somehow when hitting up arrow in terminal I must
have accidentally deleted it. Now it links! So to recap, properly naming
the library ("libpython33.so") and compili
This is an advanced topic which touches on a lot of OS X details. The short
of it is, even if you solve your linking problems your Python 3.3 library
won't work.
What you need to is include the entire Python 3.3 framework in your
Application bundle. Once you've figured out how to do that, linking
Ken Thomases, Ben Kennedy,
thanks for the replies!
Yes, I tried "libpython33.so", "libpython33.dylib", "python33.dylib", ...
But I still get that error, even if the file is "ls -al":
-r-xr-xr-x@ 1 ecir staff 5503912 29 sep 10:27 libpython33.so
That "-v" switch is a good advice but I ca
On Feb 24, 2013, at 2:09 PM, ecir hana wrote:
> and running "file python33" says:
>
>python33 (for architecture i386): Mach-O dynamically linked shared
> library i386
>python33 (for architecture x86_64): Mach-O 64-bit dynamically linked
> shared library x86_64
>
> The problem I have is t
Hello,
I have a simple program which I can compile but when I tried to link it
with a dynamic library the linker is not able to find the library, despite
that it is in the same folder as the program.
The longer version: I want to embed Python 3.3 interpreter into simple C
program. I'm on MacOS 10
