Sean McGovern writes:
> In Darwin/MacOS X, it is advantageous to be able to set a
> custom library install path when embedding a library alongside or
> in a path relative to it's calling binary application
> This allows constructions such as:
> @executable_path/lib
> which is evaluated by dyld at runtime.
> ---
> configure |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/configure b/configure
> index f557482..422128f 100755
> --- a/configure
> +++ b/configure
> @@ -2406,7 +2406,7 @@ case $target_os in
> enable malloc_aligned
> gas="gas-preprocessor.pl $cc"
> enabled ppc && add_asflags -force_cpusubtype_ALL
> -SHFLAGS='-dynamiclib -Wl,-single_module
> -Wl,-install_name,$(SHLIBDIR)/$(SLIBNAME),-current_version,$(LIBVERSION),-compatibility_version,$(LIBMAJOR)'
> +SHFLAGS='-dynamiclib -Wl,-single_module
> -Wl,-install_name,$(INSTALL_NAME_DIR)/$(SLIBNAME),-current_version,$(LIBVERSION),-compatibility_version,$(LIBMAJOR)'
> enabled x86_32 && append SHFLAGS -Wl,-read_only_relocs,suppress
> add_ldflags -Wl,-dynamic,-search_paths_first
> SLIBSUF=".dylib"
> @@ -3258,6 +3258,7 @@ BINDIR=\$(DESTDIR)$bindir
> DATADIR=\$(DESTDIR)$datadir
> MANDIR=\$(DESTDIR)$mandir
> SRC_PATH=$source_path
> +INSTALL_NAME_DIR=${INSTALL_NAME_DIR:=\$(SHLIBDIR)}
> CC_IDENT=$cc_ident
> ARCH=$arch
> CC=$cc
> --
What happened to my outline for fixing this mess properly?
--
Måns Rullgård
m...@mansr.com
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel