On 02/09/2011 10:30 AM, Michael Wild wrote: > Then don't override it, wrap it in a function instead. This is > semantically clearer (if you give it a good name) and has the advantage > that it's clear what's going on. Iterating over a list of targets to > modify properties in a possibly distant part of the build system isn't > very transparent IMHO.
This is exactly the reason I'm hesitant to add a feature like this. When someone says "all" targets they really want "DWIM". There will always be cases of certain targets being excluded (custom targets, generator executables, etc.) that require target-local decisions. The set of "all" targets only works in toy cases. It is better for targets participating in the DWIM set to be recorded explicitly where they are defined. -Brad _______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
