Shared library Python on Mac OS X 64-bit
Diez B. Roggisch
deets at nospam.web.de
Tue Mar 3 17:18:08 CET 2009
> 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.
A framework isn't much more than a dynamically shared library. So you
could use it to link against. For example, one can load it using ctypes
without a hitch.
More information about the Python-list