Fri Feb 25 16:21:30 EST 2011
Pattern targets. The pitfall is to not make them too general. How
are ambiguities handled?
What I like to know is how to insert a phony target into a real one.
I.e. some targets do not have a full dependency tree, only a recursive
What I want to do is to build a better build system for ecos.
- If the config file or any of the cdl files change, regenerate the
- For other changes, just perform recursive make.
Maybe it's not really worth it : keep current as is (only rebuild if
config changes) and do manual rebuild when working on eCos source