Brad King wrote:
As things become more target oriented the SET_TARGET_PROPERTIES
command will be used more frequently. Eventually a nicer interface
should be available to set these properties but that interface will be
determined on a per-property basis. I just don't want to jump the gun
a
Brandon J. Van Every wrote:
Since you
only implemented per-target flags recently, your perception is probably
that it's uncommon. Instead you're probably thinking that everyone
makes *.h files and subdirectories.
In CMake's earliest days it was part of a project that had one library
per dir
Brad King wrote:
Brandon J. Van Every wrote:
items in a PROPERTIES list have to come in pairs. I humbly submit
that the following syntax would be of great use to people:
SET_COMPILE_FLAGS(file -DBLAH -DBLLAH -DBLLAAHH)
We cannot add a command for every property.
The question is what are p
Brandon J. Van Every wrote:
SET_TARGET_PROPERTIES(file PROPERTIES COMPILE_FLAGS
"-DBLAH -DBLLAH -DBLLAAHH")
is a very common form that will be used heavily by people in CMake 2.3
onwards. Anybody who has to do lotsa trivial combos of libraries will
be doing it; for instance, shared vs. stati
SET_TARGET_PROPERTIES(file PROPERTIES COMPILE_FLAGS
"-DBLAH -DBLLAH -DBLLAAHH")
is a very common form that will be used heavily by people in CMake 2.3
onwards. Anybody who has to do lotsa trivial combos of libraries will
be doing it; for instance, shared vs. static libraries, and debug vs.
r
