>> I haven't seen that documented anywhere. IMHO this
>> behavior is counter-intuitive, in general I expect the scope of a
>> target to not depend on the cmake command I am trying to use.
>
>
> I think it is sensible that the definition of a target is scoped to one
> single directory.
> Where the
On 04.08.2015 23:15, Dan Liew wrote:
foolib is defined in this CMakeLists.txt:
https://github.com/delcypher/cmake_add_custom_command_bug/blob/master/lib/CMakeLists.txt
That is the (only) context in which you can extend the definition of the
target with custom commands.
Since when?
As far as I
For reference I've opened up a bug report
http://www.cmake.org/Bug/view.php?id=15681
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information
> foolib is defined in this CMakeLists.txt:
> https://github.com/delcypher/cmake_add_custom_command_bug/blob/master/lib/CMakeLists.txt
>
> That is the (only) context in which you can extend the definition of the
> target with custom commands.
Since when? I haven't seen that documented anywhere. IM
On 04.08.2015 22:46, Dan Liew wrote:
The target name "foolib" is unknown in this context.
This warning is for project developers. Use -Wno-dev to suppress it
```
This doesn't make sense the target **clearly exists and is in scope**
because the ``simple_test`` executable links against it an
