In other words: with target_link_libraries(executable path) the executable does get an RPATH as expected (and the executable can at least be started in the build dir) but with the target_link_libraries(executable target) it does not. Path /Users/nick/build-circlelabsnl-Desktop_Qt_5_14_1_clang_64bit-Debug/external-libs/inst64/ml-0.1/bin (offset 12) ![]() + path /Users/nick/build-circlelabsnl-Desktop_Qt_5_14_1_clang_64bit-Debug/external-libs/inst64/assimp-5.0.1/lib (offset 12) Magic cputype cpusubtype caps filetype ncmds sizeofcmds flags +++ /tmp/with-path 09:28:59.000000000 -1,7 +1,7 header CMAKEINSTALLPREFIX specifies the default install location thats used for the installation target created by cmake (the logic invoked by make install for the 'Unix Makefile' CMake generator). CMake seems to use the dirname option when linking paths? I made a diff of the output of otool -l linking directly with the IMPORTED_LOCATION instead of with the target: $ diff -u /tmp/with- Sets the default for whether toolchain-defined rpaths should be removed during installation. My only remaining question is why there are some RPATHS in my executable then, but not for this one. A semicolon-separated list specifying the rpath to use in installed targets (for platforms that support it). ![]() ![]() Thanks for the answers so far, very helpful!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |