On Thursday 28 May 2009 04:53:18 pm troy d. straszheim wrote:
In no particular order:
- There is still the toplevel filesystem.hpp and friends to deal with. You can't move libraries around as a unit (which is the desired capability, right?).
- You can't tell what headers don't belong to any 'project'.
- It is a lot harder to recursively search for function 'foo' in the headers; you're going to get hits from examples, tests, docs, etc.
- It makes it possible to include things you're not supposed to, e.g. private headers from other projects.
One possible way to do this is to stage/install public headers in similar ways as is done with libs: - stage/install all modified headers - build libs with include paths set to staging/install area - stage/install libs - build and run tests -- Bjørn