Review

[dpkristensen]

No description provided.

[dpkristensen]

A few areas I feel need special consideration:

• I don't have any sort of "version" in the file formats. Although I am thinking it might be a better idea to provide individually switchable options with default behavior instead, so people don't have to remember which version number does what.
• Would like to implement some kind of package dependency system. A couple thoughts about this:
  • What is the goal? To reduce the # of files rebuilt when a public header changes? To work around compiler limitations on the number of include paths or the command-line length?
  • Packages provided externally to the project would not have any way to list dependencies.
  • Need to handle mixed dependency specification (some manifests specify them, others do not...)?
  • I think it should be allowed to use without dependencies.
• In my current implementation of the waf tool, I find that I need to have separate project files for each waf target. I don't think this is too bad, as the configuration files can be shared between projects. But it does mean groups of manifests can't be easily shared (at least until I implement the ability to include manifests). Any suggestions for improvement, or is this generally OK?