Creation of a Build tool on top of the D compiler

[kris]

Hasan Aljudy wrote:
> 
> 
> Sean Kelly wrote:
> 
>> kris wrote:
>>
>>> Sure, a build tool is still really handy for generating libs, and so 
>>> on. But the basic compilation/linking task really ought to be handled 
>>> by the compiler itself. I mean, c'mon -- the compiler has an option 
>>> to /run/ the resultant executable ... should at least be able to 
>>> /create/ it first?
>>
>>
>> Good point :-)  I guess the run option currently only works for 
>> single-module apps, huh?
> 
> 
> 
> I thought it'd also work if you pass all the file names at the command 
> line, heh.

heh - it will, but that's impractical to do by hand [1]. Especially when 
you can't successfully utilize certain types of D code from a library -- 
such as templates.

[1] you can always create make files or whatever, but that requires 
setting up the makefile and keeping it up-to-date. Thus, Build/Bud is a 
better solution than makefiles for many people. Yet, there's no need for 
a build tool for the basic compilation cycle, particularly when the 
compiler has already parsed /all/ the relevant files.