On 23/08/14 16:09, Reinhard Tartler wrote: > This option facilitates testing shared libarary builds: for instance > fate builders do no longer need to set LD_LIBRARY_PATH as the binaries will > get the right search paths hardcoded into their executable file. > > This option is only meant to be used for testing purposes: The libraries > can no longer be moved around in the file system, and doing so will > cause a lot of subtle problems. For more information why using RPATH is > dangerous, please refer to
I'd suggest using the -rpath just for the binaries if it is enough (we have a mean to do that now) and move it to the expert section. Beside that I'm fine with it. > > https://blog.flameeyes.eu/2010/06/the-why-and-how-of-rpath > --- > configure | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/configure b/configure > index 97b60cd..0a0ccf5 100755 > --- a/configure > +++ b/configure > @@ -86,6 +86,7 @@ Standard options: > --shlibdir=DIR install shared libs in DIR [PREFIX/lib] > --incdir=DIR install includes in DIR [PREFIX/include] > --mandir=DIR install man page in DIR [PREFIX/share/man] > + --enable-rpath use rpath when installing libraries [USE WITH > CARE] > > Licensing options: > --enable-gpl allow use of GPL code, the resulting libs > @@ -1596,6 +1597,7 @@ CMDLINE_SELECT=" > logging > lto > optimizations > + rpath > " > > PATHS_LIST=" > @@ -4293,6 +4295,7 @@ check_disable_warning -Wno-pointer-sign > # add some linker flags > check_ldflags -Wl,--warn-common > check_ldflags > -Wl,-rpath-link=libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil:libavresample > +enabled rpath && add_ldflags -Wl,-rpath,$libdir > test_ldflags -Wl,-Bsymbolic && append SHFLAGS -Wl,-Bsymbolic > > # add some strip flags > _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
