[Cmake-commits] CMake branch, master, updated. v3.12.0-rc2-136-g5fec622

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index bddd027..18440bd 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 12) -set(CMake_VERSION_PATCH 20180704) +set(CMake_VER

Re: [CMake] how to deprecate a target?

Hi Petr, Marc, I guess I could generate a linker warning, it's indeed not-so-nice, but might do the trick ... It seems aliases are only possible on global imported targets. Mine aren't (which is by default I guess). It's probably not a great idea to make them global ... Thanks for the

Re: [cmake-developers] Race between ADD_CUSTOM_COMMAND()

Hi Nils, Thank you for your answer! In my case I can't use target for this. There are any hard limits which block fixing of this behaviour? By the way, can I have two and more targets in one build directory? 04.07.18 20:19, Nils Gladitz пише: > On 04.07.2018 18:52, Oleh Kravchenko wrote: > >>

Re: [cmake-developers] Race between ADD_CUSTOM_COMMAND()

On 04.07.2018 18:52, Oleh Kravchenko wrote: Hello CMake Developers! Looks like I found interesting bug in CMake: - ADD_CUSTOM_TARGET() always creates Makefile rule for ADD_CUSTOM_COMMAND(). - As result build simetimes failed if specified -jN for make. FWIW this is documented behavior (so not

[cmake-developers] Alternative CMake Syntax

Hello everyone, I've been thinking about designing a new syntax for CMake that better expresses some of the functionality that I've seen in modern CMake code. I've started a CMake parsing library and plan on using it to design the new syntax while maintaining support for the traditional syntax as

[cmake-developers] Race between ADD_CUSTOM_COMMAND()

Hello CMake Developers! Looks like I found interesting bug in CMake: - ADD_CUSTOM_TARGET() always creates Makefile rule for ADD_CUSTOM_COMMAND(). - As result build simetimes failed if specified -jN for make. Please find attached simple project which reproduce the problem. > [ 12%] Generate

[cmake-developers] -Wl,-rpath-link and --sysroot on Linux

Hi, I think I may have found a problem related to CMake’s handling of -Wl,-rpath-link on Linux in combination with cross-compiling against a sysroot. You can grab a minimal example that exposes the behavior at https://github.com/neverpanic/cmake-rpath-link-example. The example uses a chain of

Re: [CMake] How to specify library dir for imported interface?

Next version of CMake (3.13) will supports properties LINK_OPTIONS as well as INTERFACE_LINK_OPTIONS. Le mer. 4 juil. 2018 à 16:02, Francis Giraldeau a écrit : > > However, it seems no property exists to actually specify the library dir > > of imported target, nor the linker flags to pass when

[CMake] How to specify library dir for imported interface?

> However, it seems no property exists to actually specify the library dir > of imported target, nor the linker flags to pass when using the > imported target. > > What would be the best way to specify the library dir for an imported > library? My workarround at the moment is to add a global

[CMake] CMAKE_SYSTEM_FRAMEWORK_PATH is not considered when generating iOS XCode SYSTEM_FRAMEWORK_SEARCH_PATH

Hi, I'm not sure if this is a bug or if I have misunderstood something. I'm linking against Qt-Frameworks on iOS. CMake automatically adds the base-path of these Frameworks to the includes of my targets. Because there are warnings in the header files and I am building with -Werror, these

Re: [CMake] Adding a target to 'all' that was previously excluded

Hi Andrew. All that the EXCLUDE_FROM_ALL argument of add_executable() does is set that target's property EXCLUDE_FROM_ALL to TRUE. So all you need to do is set that property to false again: set_property(TARGET blah PROPERTY EXCLUDE_FROM_ALL FALSE) Petr On 4 July 2018 at 08:48, Marc CHEVRIER

Re: [CMake] Adding a target to 'all' that was previously excluded

You can use a new target, built by all, depending on your initial target: add_custom_target(build_blah_X ALL) add_dependencies(build_blah_X blah_X) Le mer. 4 juil. 2018 à 03:33, Andrew White a écrit : > How do I add an excluded (executable) target to the build. I know that if > I add a

Re: [CMake] Changing link flags for one target

LINK_FLAGS property do not support generator expressions. In CMake 3.13, directory and target properties LINK_OPTIONS, supporting generator expressions, managed by commands add_link_options and target_link_options are introduced, . For earlier versions you can use global variables to set flags