Differences From Artifact [8914ce1316]:
- File
m4/buildsys.m4
— part of check-in
[f23a2d808f]
at
2014-05-15 01:09:37
on branch trunk
— Use @rpath/foo.dylib as install_name
This makes it behave like on ELF systems where rpath is used to tell the
linker where to look for libraries. (user: js, size: 7075) [annotate] [blame] [check-ins using]
To Artifact [b446dc0e74]:
- File
m4/buildsys.m4
— part of check-in
[be6fab977d]
at
2014-05-15 15:52:30
on branch trunk
— @rpath is not even needed as install_name
It is possible to set it to the path where the library will be installed
and still have in-tree applications work by setting DYLD_LIBRARY_PATH.
Even if the library is already installed, it will use the in-tree
library if DYLD_LIBRARY_PATH is set. (user: js, size: 7078) [annotate] [blame] [check-ins using]
︙ | |||
116 117 118 119 120 121 122 | 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 | - + | AC_DEFUN([BUILDSYS_SHARED_LIB], [ AC_REQUIRE([AC_CANONICAL_HOST]) AC_MSG_CHECKING(for shared library system) case "$host_os" in darwin*) AC_MSG_RESULT(Darwin) LIB_CFLAGS='-fPIC -DPIC' |
︙ |