Notes |
|
(0010494)
|
mnieber
|
2008-02-14 04:30
|
|
Hi, just a small note to let you know I'm still very much interested in this feature! I hope its implementation is not too complicated. |
|
|
(0023956)
|
David Cole
|
2010-12-14 11:28
|
|
Can't you implement this by yourself by simply not adding any include directories or definitions at the top level? |
|
|
(0023963)
|
mnieber
|
2010-12-14 11:54
|
|
Usually this is not possible. CSnake generates a project dependency tree that has many levels. Each project in the tree uses ADD_SUBDIRECTORY for its child projects. In the current CMake, once a project has includes/defines, all its (grand)children will also get them (hence the request for DONT_INHERIT). |
|
|
(0025217)
|
David Cole
|
2011-02-01 16:12
|
|
This request seems too much against the nature of CMake's add_subdirectory and the inheritance of property and variable values that are built-in and automatic.
I think "DONT_INHERIT" would either:
- block some, but not all, inherited values (and it would be confusing to explain why some things are and some things are not inherited)
* OR *
- block all inherited values, including cache variable values, and surprise some folks by not getting what they expect from their parent directories...
I think "DONT_INHERIT" goes against the grain of what developers have come to expect from CMake.
The goal that you have of not sharing defs and include dirs with other directories may be realized simply by re-organizing your calls to add_definitions, include_directories and add_subdirectory. With the understanding that subdirectories ALWAYS inherit properties and variables from the parent.
Feel free to bring this up on the mailing list for a more inclusive discussion with other opinions involved... but for now, I'm going to resolve this one as "won't fix" |
|
|
(0026682)
|
David Cole
|
2011-06-06 18:25
|
|
Closing resolved issues that have not been updated in more than 3 months. |
|