Handling separate debug/release libraries

Thomas Moulard thomas.moulard at gmail.com
Mon Jun 29 19:46:57 PDT 2009

On Tue, Jun 30, 2009 at 10:11 AM, Tollef Fog Heen<tfheen at err.no> wrote:
> ]]
> Hi,
> | I am wondering how pkg-config can handle projects which are installing
> | several (binary compatible) versions of the same library (i.e. release
> | and debug).
> if they're completely binary compatible, pkg-config doesn't need to
> worry at all: you can choose which one you'd like to use at runtime. For
> debug libraries, the usual way to do it (on Unix) is to ship either
> unstripped binaries or detached debug symbols in /usr/lib/debug.

I see, in that case using LD_LIBRARY_PATH seems valid approach.

> If your API and ABI varies on the other hand, you have to make sure to
> choose the right one when compiling and linking.
> Currently, the way people do that is to have different names of the .pc
> files.  I agree this might not be completely optimal, so if anybody has
> a better idea (and implementation), please. :-)
> | But then I did not find a way to retrieve non-standard information
> | using pkg-config.
> you can use --variable and --define-variable, but that is a bit
> cumbersome, IMO.

The only implementation I can think of is having a Libs.debug
additional keyword.

IMHO I think that problem is a "subcase" of the
"Extensions to .pc files" thread.

> | PS: Is there a web browser for the Bazaar repository, I can not see
> | anything on http://pkg-config.freedesktop.org/bzr/.
> No, there isn't.  I'm considering moving to git partially because of
> that.


Thanks a lot for your help,
Thomas Moulard

More information about the pkg-config mailing list