[issue15590] --libs is inconsistent for python-config --libs and pkgconfig python --libs
Michael Haubenwallner
report at bugs.python.org
Tue Jun 3 08:33:18 CEST 2014
Michael Haubenwallner added the comment:
Well, they should not be identical, as they are for different use cases.
"pkg-config python" is to build an application containing a python interpreter (like python$EXE):
+ Link against libpython.so. Additionally,
+ re-export symbols from libpython.so for the python-modules (platform-specific).
= This is similar to build against any other library, thus using 'pkg-config python'.
"python-config" is to build a python-module (like build/lib.<platform>-<pyver>/*.so):
+ No need to link against libpython.so, instead
+ expect symbols from libpython.so to be available at runtime, platform specific either
+ as a list of symbols to import from "the main executable" (AIX), or
+ as undefined symbols at build-time (Linux, others), or
= This is specific to python-modules, thus using 'python-config'.
----------
nosy: +haubi
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15590>
_______________________________________
More information about the Python-bugs-list
mailing list