| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It puts a slimmed down makefile into the tarball, along with all of the checked
out libbu++ files, so you should just need to compile (if you have the right
flex and bison).
|
|
|
|
nothing else. It will automatically wget the necesarry files from libbu++ and
put them right in your src dir... make clean will delete them as well.
|
|
|
|
|
|
|
|
|
|
Makefile later that I won't have to keep updating...
|
|
cool looking.
|
|
maybe more later. -c or --clean will set all of the commands in the current
action to clean, so now you don't have to create clean rules.
Also, every viewer should now support stacks of targets, they don't now, and it
can look a little funny.
|
|
a requirement is set for a target that needs to be built, and that requirement
is another target, that target will be processed when it is needed.
|
|
|
|
|
|
|
|
|
|
|
|
levels of contextual inheritance, so now sub-targets automatically get their
parent target's context variables, if they need them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fortunately, filtering is more of a nicety, and build is still useful. I'll put
filtering back in next.
|
|
|
|
Now we have to add cleaning, caching, and more viewer hooks / viewers.
|
|
"extra" variables.
|
|
|
|
|
|
that's done, we can actually run the performs, and, most likely build things.
|
|
related build-time components!
|
|
pre parser, and whatever.
|
|
generic base class for anything that could create a build object.
|
|
the whole thing official.
|
|
rules.
|
|
|
|
going pretty quickly, we'll see how the targets go, they'll be the only tricky
part.
|
|
|
|
|
|
parser and scanner are using the new system so they actually match functions
and whatnot and pass that data to the parser, it's very cool.
|
|
debugging mode. If you wanted something intelligable, don't use this one.
|
|
builder itself tells the lexer which tokens are functions, and which are target
types.
|
|
see what happens next.
|
|
continuation token.
|
