Dear all,

I'm using python in a application (sigrok.org) and want to ship it as a framework with a .app folder. 

I'm building python-3.3b1 from source to a .framework. It is correctly compiled and installed in the given directory. Only the python-3.3.pc is incorrect because it has not the name python-3.3m.pc and includes the following library entries: Libs: -L${libdir} -lpython3.3m

So this results in:
ld: library not found for -lpython3.3m
because of the deployment of the wrong .pc Libs directive:
build/decoders/nunchuk/Makefile
127:CPPFLAGS_PYTHON = -I/Users/jerry/Sigrok/Python.framework/Versions/3.3/include/python3.3m -I/Users/jerry/Sigrok/Python.framework/Versions/3.3/include/python3.3m
159:LDFLAGS_PYTHON = -L/Users/jerry/Sigrok/Python.framework/Versions/3.3/lib/python3.3/config-3.3m -ldl -framework CoreFoundation -lpython3.3m -framework CoreFoundation Python.framework/Versions/3.3/Python
187:PYTHON3_CONFIG = python3.3m-config

Kind regards,
Jerry

Thanks for the report.  The python-3.3.pc file is correct.  It is a symlink to the python-3.3m.pc.  What isn't correct is that OS X framework builds were not creating the proper libpython3.3m.{dylib,a} symlinks for use with python3.x-config and with pkg-config (if installed).  The fixes applied for Issue14197 (for release in 3.2.4 and 3.3.0b2) correct that and ensure that python-3.x-conifg --ldflags returns a useful value.

superseder: OS X framework builds do not create ABI-suffixed libpython3.x
components: + Build
versions: + Python 3.2
messages: + msg166276
type: compile error ->
resolution: duplicate
stage: resolved