| Summary: | README.win32 <-> code missync | ||
|---|---|---|---|
| Product: | pkg-config | Reporter: | Michał Górny <mgorny> |
| Component: | src | Assignee: | Tollef Fog Heen <tfheen> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Michał Górny
2012-09-03 09:58:00 UTC
Oops, sorry, hit the wrong key. Here are the details: > pkg-config uses some optional entries in the Registry: Firstly, the > path to the pkgconfig installation prefix. This can be either > user-specific in HKCU\Software\pkgconfig\InstallationDirectory or for > the whole machine in HKLM\Software\pkgconfig\InstallationDirectory. I don't see any trace of it in the code. I guess it is fully glib-magic now. > Additionally, in addition to the PKG_CONFIG_PATH environment > variables, any string value in the Registry key > HKLM\Software\pkgconfig\PKG_CONFIG_PATH (or HKCU\...) is assumed to be > a directory name and is searched for .pc files. No trace of that either. Is the doc outdated or am I missing something? Is there a patched version of pkg-config for win32 with the registry access code? The registry entries were removed a few years ago in commit dce0339 as you found. Fixed in 454dd17. Thanks for the report. |
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.