On Wed, 2011-12-07 at 14:38 +0100, Jacob Carlborg wrote: [...] > What I see as the advantage of a new build system is that it can be > developed specifically for D which could make the tool very easy to use. > Example: > > $ tool build main.d
Go has gone to the extreme with this, they have a project structure which is mandated. This makes build completely convention driven so there are no build specifications at all, their build tool can deduce all the data needed to complete a build. This is the logical extension of the "convention over configuration" approach developed by Maven and Gradle to such great effect. > That's all that should be needed to build an executable. You could have > the same in a build script: > > // buildfile > main.d Too much data ;-) > $ tool build > > For a library it should be similar: > > $ tool build foo > > Where "foo" is a directory. I don't know if that's possible to have in a > build tool not specifically developed for D. I still worry about a language specific tool. Language plugins to general tools make far more sense to me. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@russel.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part