Re: [CMake] Getting library name from library target to pass to legacy Makefile

You can use generator expression TARGET_FILE_BASE_NAME, available with version 3.15. Le 22 juil. 2019 à 05:24 +0200, Dustyn Blasig , a écrit : > Hi All, > > I am integrating a legacy Makefile with our CMake flow, and need to pass the > name of a CMake library target to the Makefile via add_custom

[CMake] Getting library name from library target to pass to legacy Makefile

Hi All, I am integrating a legacy Makefile with our CMake flow, and need to pass the name of a CMake library target to the Makefile via add_custom_command(). The library uses the OUTPUT_NAME property to override the default. add_library(foo_lib SHARED ...) set_target_properties(foo_lib PROPERTIES

Re: [CMake] FetchContent/ExternalProject and URL_HASH

Thanks for the info, Craig. I'm not very familiar with the intricacies of network downloads. If the download itself guarantees the file was transferred correctly and the checksum is only be used to verify its authenticity, then we probably don't need it as we're only downloading these artifacts fr

Re: [CMake] getting compiler's include paths

lol c++20 modules 😂🙄 IF users use them modules is just pain in the ass for developers I hope that real developers will simply ignore them headers are here for a good reason, and stupid languages like python that use modules are just stupid it will make more complicated for t

Re: [CMake] FetchContent/ExternalProject and URL_HASH

On Wed, Jul 17, 2019 at 12:59 PM Dustyn Blasig wrote: > Hi All, > > We are pulling some artifacts from Artifactory which provides a checksum > file along with the artifacts at .md5 or .sha256. If I do not > include URL_HASH, does CMake automatically check to see if such a checksum > file exists a