Commit 0c54b775 authored by Stephen Kelly's avatar Stephen Kelly
Browse files

Help: Document the purpose of usage requirements clearly.

People will be tempted to put things there for convenience, thereby
causing conflicts similar to

where it is conceivable that the LLVM developers could put a flag on
a target for convenience, which would cause conflicts for some downstreams.
parent 586d2ce8
......@@ -112,6 +112,12 @@ Each command may be invoked with multiple uses of each keyword:
Note that usage requirements are not designed as a way to make downstreams
use particular :prop_tgt:`COMPILE_OPTIONS` or
:prop_tgt:`COMPILE_DEFINITIONS` etc for convenience only. The contents of
the properties must be **requirements**, not merely recommendations or
Target Properties
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment