Alexander Neundorf wrote: > On Wednesday 08 March 2006 22:17, you wrote: >>CMake by default sets the install_name of a library in the build tree to >>be the full path to its build tree location. When installing targets >>CMake uses the command "install_name_tool" to change the directory part >>(not the filename) of the install_name of each target to that specified >>by the target's INSTALL_NAME_DIR target property. For each library that >>an executable links it also changes the executable's copy of that >>library's install_name so that it may be found in the installed location. > > How is this affected by the RPATh related options ? > AFAIK CMAKE_SKIP_RPATH disabled the install name too. > How about SKIP_BUILD_RPATH and BUILD_WITH_INSTALL_RPATH ? > Apparently they have some effect, since otherwise David wouldn't have seen > any > changes.
Those three options affect INSTALL_NAME_DIR the same way they affect INSTALL_RPATH. This install_name business is (approximately) the OSX equivalent to RPATH. > So, just to make sure: > by default, cmake sets the INSTALL_NAME_DIR to the build dir when building, > and sets it to the contents of CMAKE_INSTALL_NAME_DIR when installing, with > CMAKE_INSTALL_NAME_DIR being empty by default ? Basically yes. When building the install_name is set to the build dir. The target property INSTALL_NAME_DIR is used when installing. This property is initialized when the target is created using the contents of the variable CMAKE_INSTALL_NAME_DIR. -Brad _______________________________________________ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem