On Mon, Nov 18, 2019 at 03:30:32PM +0000, Bruce Richardson wrote: > On Mon, Nov 18, 2019 at 04:14:54PM +0100, Thomas Monjalon wrote: > > 12/11/2019 14:15, Ferruh Yigit: > > > This patch functionally reverts the patch in fixes line to not have any > > > hardcoded library path in the final binary for the security reasons, in > > > case this binary distributed to production environment. > > > > What about meson? > > There are these rpaths: > > $ORIGIN/../lib > > $ORIGIN/../drivers > > > > Meson uses relative paths based off the file location "$ORIGIN" as you see > above. This avoids having a user's home path in the search directories. > > However, meson also adjusts the rpath on install, so if you run > test-meson-builds.sh and check the rpath on > build-x64-default/app/dpdk-testpmd and compare against > build-x86-default/install-root/usr/local/bin/dpdk-testpmd you'll see they > are different, with the latter having the final install path encoded in it. > If we do want to control these, they can be set for binaries using the > "build_rpath" and "install_rpath" parameters, though I think the current > values are ok. > > /Bruce
Apologies for the self-reply, but forgot to include the reference to the relevant parameters [1], and they should apply for both executables and libraries [2]. [1] https://mesonbuild.com/Reference-manual.html#executable [2] https://mesonbuild.com/Reference-manual.html#library
