Bug 6074

Summary:	pkg-config 0.20 not finding the correct registry key and default directories
Product:	pkg-config	Reporter:	Daniel K. O. <danielosmari>
Component:	src	Assignee:	Tollef Fog Heen <tfheen>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Windows (All)
Whiteboard:
i915 platform:		i915 features:

Description Daniel K. O. 2006-03-01 16:42:36 UTC

The docs mention the use of the registry keys
"(...)\Software\pkgconfig\PKG_CONFIG_PATH", but the code uses the PACKAGE macro
- that changed to pkg-config. Somebody needs to either fix the docs or the sources.


Makefile.am is being "too clever" to define the PKG_CONFIG_PC_PATH macro; MSYS
converts the "/" to "\", so I end up with this:

---
Adding directory 'c:mingwlibpkgconfig' from PKG_CONFIG_PATH
Adding directory 'c:mingwsharepkgconfig' from PKG_CONFIG_PATH
---

(./configured with --prefix=/mingw, that points to c:\mingw)


Also, the binary provided on Tor's website seems to be compiled with a
hard-coded (instead of the usual relative) and not-working path:

---
Adding directory 'c:/devel/target/pkg-config-0.20/lib/pkgconfig:c:/devel/target/
pkg-config-0.20/share/pkgconfig' from PKG_CONFIG_PATH
---

I'm not really sure if this is the culprit, but it can't find the relative
"../lib/pkgconfig" directory anymore. I believe that on Win32 the
PKG_CONFIG_PC_PATH macro should be defined as relative.

Comment 1 Dan Nicholson 2012-04-16 17:30:26 UTC

I think this has mostly been fixed. Commit 7850aeb03a54a15d07b6c243b61033cd379c39d7 uses some GNU make magic to escape the paths on NATIVE_WIN32. Likewise, the default path used contains "pkgconfig" rather than "pkg-config" like on Linux/Unix.

For the relative paths, I believe the best you can do is set --with-pc-path at build time the way you want. If someone wants to build a binary pkg-config for windows that has a relative path in the default, they can do that. Likewise, you can always set PKG_CONFIG_PATH relative if you need to.

Please reopen if you think this bug is not fixed.

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.