pkg_config_path not consistent in base/cmake and other packages

rock-core / base-cmake

CMake find scripts and macros used in Rock's packages

1 stars 17 forks source link

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

Open mmaurus opened 7 years ago

mmaurus commented 7 years ago

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 commented 7 years ago

As of http://www.pathname.com/fhs/pub/fhs-2.3.pdf see page 10 and 11lib<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)?