python31, python32: Make Framework creation optional

[jerkejacobs@…]

Dear all,

I'm building the dylib python 3x for a bundling with a other project. The dependencies for this project are packed with dylibbundler. The problem is that the framework path is not copied and fixed. It would be nice to make it optional to enable/disable the framework building because I only need a working dylib of python core.

Kind regards, Jerry

[ryandesign (Ryan Carsten Schmidt)]

Wouldn't turning off the framework build change the location into which all of the python 3x modules install? Surely we don't want to open that can of worms.

[jerkejacobs@…]

I agree that disabling framework building is bad because of the hardcoded path stuff. I think why I got stuck, because the guys at python doing very weird stuff.

They have a pkgconfig file for 2 meta-versions, they point to a library name which is a symbolic link to the root of the framework (Python.framework/Versions/3.2) version directory a file named Python. This is very bad practice because I had no idea what this was until I invoked file on Python and it popped: Python: Mach-O 64-bit dynamically linked shared library x86_64.

Maybe nobody noticed this but I got very close and the snake did almost bite me !

Kind regards, Jerry

[ned-deily (Ned Deily)]

The canonical way to find the Python shared library is to use pythonx.y-config --libs. Note, however, there is currently an open upstream bug that the wrong path is being returned for framework builds in 3.2+ (​http://bugs.python.org/issue14197).