kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document reading LOCATION early as undefined (#11671) 

Reading the LOCATION target property currently locks down the result and
ignores any later changes to properties that affect it.  This may or may
not be expected and may or may not be the behavior in earlier versions
of CMake.  The property is documented as provided only for compatibility
with CMake 2.4 and alternative interfaces are now available for all
originally envisioned use cases.  We want to discourage its use without
outright deprecating it.  Add documentation to explicitly state that
reading the property before other properties are set is undefined.
This commit is contained in:
Brad King 2011-01-10 10:46:15 -05:00
parent 6754b26bf0
commit 7ffe6d77da
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Source/cmTarget.cxx
View File

@ -517,7 +517,17 @@ void cmTarget::DefineProperties(cmake *cm)
"In CMake 2.6 and above add_custom_command automatically recognizes a "
"target name in its COMMAND and DEPENDS options and computes the "
"target location. "
"Therefore this property is not needed for creating custom commands.");
"In CMake 2.8.4 and above add_custom_command recognizes generator "
"expressions to refer to target locations anywhere in the command. "
"Therefore this property is not needed for creating custom commands."
"\n"
"Do not read this property until after all other properties that can "
"affect the location of the target have been set. "
"These include properties whose names match "
"\"(IMPLIB_)?(PREFIX|SUFFIX)\" or "
"\"(RUNTIME|LIBRARY|ARCHIVE)_OUTPUT_(NAME|DIRECTORY)(_<CONFIG>)?\". "
"Failure to follow this rule is not diagnosed and leaves the location "
"of the target undefined.");
cm->DefineProperty
("LOCATION_<CONFIG>", cmProperty::TARGET,