Displaying 3 results from an estimated 3 matches for "cmp0026".
2014 Jul 16
5
[LLVMdev] Fixing LLVM's CMake interface before LLVM3.5 release
...in I as a developer should not need to
care if my project builds against the LLVM build tree or an installed
LLVM.
In [1] I hacked around this by reading the ``LOCATION`` property of
one of the imported targets. Unfortunately CMake 3.0 really doesn't
like this I get warnings like
```
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
```
The CMake docs seem to say that the reason for this is the LOCATION
might not be completely k...
2014 Aug 23
3
[LLVMdev] [3.5 Release] Release Candidate 3 Now Available - CMake build error
> Run it through its phases and report any bugs you find!
[ 1495s] CMake Warning (dev) at projects/dragonegg/CMakeLists.txt:34 (get_target_property):
[ 1495s] Policy CMP0026 is not set: Disallow use of the LOCATION target property.
[ 1495s] Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy
[ 1495s] command to set the policy and suppress this warning.
[ 1495s]
[ 1495s] The LOCATION property should not be read from target "...
2014 Jul 18
2
[LLVMdev] Fixing LLVM's CMake interface before LLVM3.5 release
...> the install-tree interface about what is actually installed, AFAIK.
>
>> In [1] I hacked around this by reading the ``LOCATION`` property of
>> one of the imported targets. Unfortunately CMake 3.0 really doesn't
>> like this I get warnings
>
> As suggested in the CMP0026 documentation:
>
> http://www.cmake.org/cmake/help/v3.0/policy/CMP0026.html
>
> you can use the $<TARGET_FILE:SomeTool> generator expression to
> get the location in a well-defined manner. It works in
> add_custom_command so that should be sufficient for your example
>...