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 sugg

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 u

[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 link_

[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 Frame

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