On macOS, the most usual thing is for your code to be self-contained in your .app bundle. Perhaps if you described more what kind of thing you are building and why you don't want to do the usual thing, people will have more advice...
On Fri, 19 Jan 2018 19:44:03 +0100, Lucas Soltic said: >Hello, >Should I conclude that there are no recommendations? > >Best regards, >Lucas > >> Le 17 janv. 2018 à 23:49, Lucas Soltic <lucas.sol...@orange.fr> a écrit : >> >> Hello, >> >> By default library install() command uses CMAKE_INSTALL_PREFIX (/usr/ >local by default) as a base for relative install paths. But when you >define install rules for macOS frameworks, it doesn't make much sense to >install them there. I'd rather expect something like /Library/Frameworks. >> >> On the other side, if you have more things to install like a "readme" >or documentation that should go into /usr/local/share, it doesn't make >sense to have them installed in /Library/Frameworks. So you can't just >change CMAKE_INSTALL_PREFIX to be /Library/Frameworks. >> >> What do you recommend to keep installation rules simple (ie. remain >relative) and yet support installation of both frameworks and other things? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
