Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkg_config_path not consistent in base/cmake and other packages #38

Open
mmaurus opened this issue Mar 8, 2017 · 1 comment
Open

pkg_config_path not consistent in base/cmake and other packages #38

mmaurus opened this issue Mar 8, 2017 · 1 comment

Comments

@mmaurus
Copy link

mmaurus commented Mar 8, 2017

While updating autoproj under msys2 (mingw64) to version 2 I had the problem that a lot of packages like external/yaml-cpp try to install their pkg_config files to .../install/lib/pkgconfig but PKG_CONFIG_PATH is set to .../install/lib64/pkgconfig.
@2maz wasn't sure about the policy so I put it in here as an issue to discuss.

@2maz
Copy link
Member

2maz commented Mar 8, 2017

As of http://www.pathname.com/fhs/pub/fhs-2.3.pdf see page 10 and 11 lib<qual> is optional.
To go along with this policy PKG_CONFIG_PATH has to contain lib/pkgconfig in any case and should not only contain lib64/pkgconfig. This is then primarily an issue of setting PKG_CONFIG_PATH correctly.
Can you recheck what autoproj envsh is generating when only the package set rock.core is active (and make sure you don't manipulate the PKG_CONFIG_PATH e.g. in init.rb)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants