Are you just checking if the compiler is GCC? if so I would use COMPILER_ID https://cmake.org/cmake/help/v3.8/variable/CMAKE_LANG_COMPILER_ID.html
On Wed, Jan 17, 2018 at 6:19 PM, J Decker <[email protected]> wrote: > It's not entirely related other than Mac.... > > I had to test > > if( __COMPILER_GNU AND NOT CMAKE_COMPILER_IS_GNUCC ) > > instead of just CMAKE_COMPILER_IS_GNUCC (which was unset) > > __COMPILER_GNU was found after doing a dump... > > I suppose there's some modern way I'm supposed to test GCC that works on all > systems? > > > On Wed, Jan 17, 2018 at 2:49 PM, Lucas Soltic <[email protected]> > wrote: >> >> 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? >> >> Best regards, >> Lucas >> -- >> >> 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 > > > > -- > > 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 > -- 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
