Notes |
|
(0038275)
|
Brad King
|
2015-03-23 09:39
|
|
The ALL option just means that "make" with no other arguments will build the custom target even if it is not a dependency of anything else. No order of custom targets is defined with respect to other targets. You need to use
add_dependencies(target-that-needs-custom-target custom-target)
to specify target ordering dependencies. |
|
|
(0038279)
|
Zhihao Yuan
|
2015-03-23 11:56
|
|
I tried
add_dependencies(nvi headers)
where nvi is the executable target, headers is the custom target depends on headers generated by custom commands, still doesn't work. |
|
|
(0038281)
|
Brad King
|
2015-03-23 13:06
|
|
The project in question uses lots of relative paths in its DEPENDS options. It looks like our documentation fails to specify that DEPENDS must be either absolute paths or target names.
Likely relative DEPENDS values resolve differently after this change in CMake 3.1:
add_custom_command: Normalize OUTPUT and DEPENDS paths.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c4af46b4 [^] |
|
|
(0038282)
|
Brad King
|
2015-03-23 13:13
|
|
I've opened 0015470 to track the fact that we've never documented well-defined behavior for relative paths in DEPENDS. |
|
|
(0039744)
|
Robert Maynard
|
2015-11-02 09:13
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|