Re: [CMake] Building cmake: why is openssl linked?
https://cmake.org/cmake/help/latest/module/ExternalProject.html since CMake can download stuff, it needs to support https, hence SSL, hence OpenSSL Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Sun, Jan 14, 2018 at 12:15 AM, Paul Smith wrote: > Hi all. > > I build CMake myself. I've noticed that on GNU/Linux by default cmake > will be linked with openssl and require these shared libraries to be > available at runtime. > > Why does cmake link with these libraries? I can't think of a reason it > might need them. What do I lose in functionality if I force > CMAKE_USE_OPENSSL to OFF during the build? > -- > > 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
[CMake] Building cmake: why is openssl linked?
Hi all. I build CMake myself. I've noticed that on GNU/Linux by default cmake will be linked with openssl and require these shared libraries to be available at runtime. Why does cmake link with these libraries? I can't think of a reason it might need them. What do I lose in functionality if I force CMAKE_USE_OPENSSL to OFF during the build? -- 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
Re: [CMake] Querying CMake variables of external CMake projects
Thank you Konstantin. get_target_properties(...) works very well. On Sat, Jan 13, 2018 at 12:06 PM Konstantin Tokarev wrote: > > > 13.01.2018, 06:26, "Saad Khattak" : > > Hi, > > > > Say I find LibA using find_package(LibA) and I now have access to > LibA_DIR, which is the build folder of LibA. Is there a way I can query > additional variables, such as LibA's source directory, install directory > etc. i.e. variables that are defined by CMake when LibA was being > generated/built by CMake? > > If find_package(LibA) provides you target "LibA" (i.e., cmake code under > "if (TARGET LibA)" > condition is being executed), you can query various properties from it and > expect them to > have sane values. See documentation on cmake properties. > > If there is no LibA target, it probably means that find_package(LibA) is > implemented via > FindLibA.cmake module, and you can only use variables that it sets > (usually documented in > the beginning of module) > > > > > Thanks, > > Saad > > ,-- > > > > 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 > > > -- > Regards, > Konstantin > -- 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
Re: [CMake] Making sure dependent projects are up-to-date
Thanks J. That requires me to use ExternalProject_Add. However, in my case, I have all Libraries generated/built independently. Should I just start using ExternalProject_Add for dependencies? If yes, what is the best way to do that in conjunction with 'find_package(...)'? On Sat, Jan 13, 2018 at 10:28 AM J Decker wrote: > maybehttps://cmake.org/cmake/help/v3.2/module/ExternalProject.html > > BUILD_ALWAYS 1No stamp file, build step always runs > > On Fri, Jan 12, 2018 at 7:41 PM, Saad Khattak > wrote: > >> Hi, >> >> Let's say I have several CMake enabled libraries that have their own >> respective build directories and have been installed: >> >> LibA >> LibB (depends on A) >> LibC >> LibD (depends on LibC and LibA) >> >> I then create a new executable project ProjExe that depends on LibD. Now, >> I am working on LibA, LibB, LibC, LibD and ProjExe simultaneously (e.g. >> building up functionality in the libraries that the executable uses, fixing >> bugs etc.). >> >> What I would like, is a way to ensure that when ProjExe is built, it >> first checks whether LibD is up-to-date (i.e. does it have any out of >> source build files?), if not, it builds LibD first. But LibD depends on >> LibC and LibA, and then LibD ensures that LibC and LibA are up-to-date >> before building itself. >> >> Is something like this possible in CMake? This is similar to the >> 'solution' concept in Visual C++ where a 'solution' can have several >> projects. ProjExe in the solution can be dependent on external libraries >> (like the above) and they are part of the 'solution' and are checked to be >> up-to-date before ProjExe is compiled/linked. >> >> Thanks, >> Saad >> >> -- >> >> 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
Re: [CMake] Querying CMake variables of external CMake projects
13.01.2018, 06:26, "Saad Khattak" : > Hi, > > Say I find LibA using find_package(LibA) and I now have access to LibA_DIR, > which is the build folder of LibA. Is there a way I can query additional > variables, such as LibA's source directory, install directory etc. i.e. > variables that are defined by CMake when LibA was being generated/built by > CMake? If find_package(LibA) provides you target "LibA" (i.e., cmake code under "if (TARGET LibA)" condition is being executed), you can query various properties from it and expect them to have sane values. See documentation on cmake properties. If there is no LibA target, it probably means that find_package(LibA) is implemented via FindLibA.cmake module, and you can only use variables that it sets (usually documented in the beginning of module) > > Thanks, > Saad > ,-- > > 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 -- Regards, Konstantin -- 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
Re: [CMake] Making sure dependent projects are up-to-date
maybehttps://cmake.org/cmake/help/v3.2/module/ExternalProject.html BUILD_ALWAYS 1No stamp file, build step always runs On Fri, Jan 12, 2018 at 7:41 PM, Saad Khattak wrote: > Hi, > > Let's say I have several CMake enabled libraries that have their own > respective build directories and have been installed: > > LibA > LibB (depends on A) > LibC > LibD (depends on LibC and LibA) > > I then create a new executable project ProjExe that depends on LibD. Now, > I am working on LibA, LibB, LibC, LibD and ProjExe simultaneously (e.g. > building up functionality in the libraries that the executable uses, fixing > bugs etc.). > > What I would like, is a way to ensure that when ProjExe is built, it first > checks whether LibD is up-to-date (i.e. does it have any out of source > build files?), if not, it builds LibD first. But LibD depends on LibC and > LibA, and then LibD ensures that LibC and LibA are up-to-date before > building itself. > > Is something like this possible in CMake? This is similar to the > 'solution' concept in Visual C++ where a 'solution' can have several > projects. ProjExe in the solution can be dependent on external libraries > (like the above) and they are part of the 'solution' and are checked to be > up-to-date before ProjExe is compiled/linked. > > Thanks, > Saad > > -- > > 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