On Tuesday, February 24, 2015 20:14:23 Stephen Kelly wrote:
Jifeng ZHANG wrote:
Any idea when CMake 4.0 is planned to release? So we can get a general
idea when the old behavior will stop working.
What will you do when it is released and the LOCATION property does stop
working for build
Thank you Steve and NoRulez.
We actually make some manipulations on the string (TEST_PATH) that
returned from get_target_property, before we pass it to add_test.
So if we directly pass the generator expression, it won't work. We
need to change this part obviously.
Any idea when CMake 4.0 is
Jifeng ZHANG wrote:
Any idea when CMake 4.0 is planned to release? So we can get a general
idea when the old behavior will stop working.
What will you do when it is released and the LOCATION property does stop
working for build targets? Whatever it is, any reason not to do it now?
Thanks,
Hi,
We had that problem too.
Look at the great example from Stephen to my question.
His example was great and helped us a lot.
Best Regards
Am 06.02.2015 um 19:18 schrieb Stephen Kelly steve...@gmail.com:
Jifeng ZHANG wrote:
Hi,
I have a question of policy CMP0026. Our project
Hi,
I have a question of policy CMP0026. Our project currently is on CMake
2 and we are planning to move to CMake 3.
When we run CMake3.1.1, we get get a few warnings due to the policy
CMP0026, Disallow use of the LOCATION target property. Even though
with those warnings, our cmake scripts still
Jifeng ZHANG wrote:
Hi,
I have a question of policy CMP0026. Our project currently is on CMake
2 and we are planning to move to CMake 3.
Lot's of questions on that lately. Someone opened the floodgates it seems
:).
When we run CMake3.1.1, we get get a few warnings due to the policy
