Bug 648 - [PENDING] Support for having pkglibdir as a semicolon-separated string
Summary: [PENDING] Support for having pkglibdir as a semicolon-separated string
Status: RESOLVED FIXED
Alias: None
Product: pkg-config
Classification: Unclassified
Component: src (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Tollef Fog Heen
QA Contact:
URL: http://raw.no/debian/pkgconfig-multia...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-20 20:28 UTC by Tollef Fog Heen
Modified: 2005-03-27 14:13 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Tollef Fog Heen 2004-05-20 20:28:54 UTC
The url refers to a patch to make pkglibdir be able to be a semicolon-separated 
string, so you can have a default search path and not just a default search dir. 
 Note that the patch is made against the Debian package, so I'm not 100% 
everything it applies to the normal upstream sources.
Comment 1 Tollef Fog Heen 2005-03-26 07:05:21 UTC
2005-03-18  Tollef Fog Heen  <tfheen@err.no>

        * main.c (main): Use add_search_dirs for both the compile-time
        defined pc_path and the run-time defined PKG_CONFIG_PATH.

        * pkg.h: Add prototype for add_search_dirs.

        * pkg.c (add_search_dirs): Add new function which takes a
        delimiter-separated list as input and add_search_dir's it.
        (package_init): Remove knowledge about which dirs should be
        initially added.  Moved this to main.c(main)

        * ChangeLog: Add emacs variables to set the date to this
        ChangeLog's standard format

        * Makefile.am (INCLUDES): Pass PKG_CONFIG_PCPATH on to main.c

        * configure.in: Add --with-pc-path to define the default search
        path for .pc files.  (Freedesktop #119, #648)
Comment 2 Tollef Fog Heen 2005-03-28 08:05:32 UTC
pkgconfig 0.16 has been released and contains a fix for this bug.
Comment 3 Tollef Fog Heen 2005-03-28 08:13:46 UTC
Fixed in 0.16


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.