Hooo, a self-contained build tool? That's cool.
1. Are arbitrary make-style commands supported? For example, on
windows one may want to compile resources. Resources consist of a
declaration .rc file, icons and manifest files, which are
compiled into .res file, though only .rc file is passed to the
resource compiler, but other files are still dependencies of
course.
2. How to do heterogeneous linking? Again on windows an
executable can be linked from code .obj's, resource .res and
module definition .def:
gcc main.o r.res mytool.def -o mytool.exe
3. Probably not actual for big projects. Can build workspase be
created automatically by bub instead of explicitly by
bub-config... for some default mode?
4. If a build server does builds from scratch, shouldn't it be
better for performance to compile several source files in one
command? Also applies to user builds: when one wants to install a
project from source, he usually does it only once and from
scratch. Have you any idea, how this affects compilation speed of
c, c++ and d? Though dmd frontend can go out of memory.
