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
When this pkg-config file is consumed in another project to produce an executable or shared lib, rpath is hardcoded in this runtime file. It leads to some inconsistent behaviour where some paths are in rpath and others not depending on whether the lib has been consumed through pkgconf or not in build system of a recipe.
Moreover, those kinds of absolute RPATH hardcoded in runtimes don't make sense at all for binaries produced on another machine.
"Official" pkg-config files usually never have -Wl,-rpath in Libs.
The text was updated successfully, but these errors were encountered:
SpaceIm
changed the title
[feature] pkg_config generator: -Wl,-rpath="${libdir}" should be removed
[feature] pkg_config/PkgConfigDeps generators: -Wl,-rpath="${libdir}" should be removed
Dec 17, 2021
Uh oh!
There was an error while loading. Please reload this page.
Currently (conan 1.30.1, but for a long time), pkg_config generator creates a pkg-config file like this on Linux:
When this pkg-config file is consumed in another project to produce an executable or shared lib, rpath is hardcoded in this runtime file. It leads to some inconsistent behaviour where some paths are in rpath and others not depending on whether the lib has been consumed through pkgconf or not in build system of a recipe.
Moreover, those kinds of absolute RPATH hardcoded in runtimes don't make sense at all for binaries produced on another machine.
"Official" pkg-config files usually never have
-Wl,-rpath
inLibs
.The text was updated successfully, but these errors were encountered: