This build tool is not for you
Have you ever seen that meme picture which says "no you can not have a pony" and then shows a pony labeled "not yours" and a crying child? I think that's the right mindset for this particular announcement.
This build tool is not for you.
Odds are, it won't be of any use. After all, who writes C++ in this day and age? Of those who do, who actually arranges their source code into a single "depot"?
Even if your code is in a "depot", who writes their #includes with paths which are relative to the top of that depot instead of the current working directory?
Maybe someone actually does all of that already. Well, those people probably love their automake, autoconf, and Makefiles. Maybe they've gone beyond that and have started using something like CMake or scons. They've already found their solution and they don't need any help from me.
If this sounds familiar, it's because I've already ranted about this and described my own solution at some length in other posts.
July 11, 2011: Moving beyond Make to build C++ programs
January 14, 2012: A C++ tool for building C++ code
March 28, 2012: A better build system
March 30, 2012: Build system: change things or accept the status quo?
April 4, 2012: My C++ style which everyone will probably hate
April 14, 2012: Making C++ coverage builds really easy
April 22, 2012: Using protocol buffers with no drama
July 16, 2012: Dare to move beyond Make
Still with me? Are you interested? I've decided to stop talking about it and post some binaries of this project so others can "play along at home". I even put together a couple of web pages to further explain how all of this works.
It still doesn't have a good name, but that's okay. Projects which tend to find their names first before they have anything working always seem wonky to me. I'll figure out a name later. That's just how I roll sometimes.