You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)?
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.
The text was updated successfully, but these errors were encountered: