On 2015-09-26 01:53, anonymous wrote:

> Compiling one file at a time is yet another thing.
>
> 1) Compile everything into one object file:
> dmd -c -ofresult.o foo.d bar.d
> 2) Compile to multiple object files in one run:
> dmd -c foo.d bar.d
> 3) Compile to multiple object files in multiple runs:
> dmd -c foo.d; dmd -c bar.d
>
> Since you didn't know about 2, I take it that you measured 1 vs 3. 3 is
> bound to be slower when the modules share dependencies, because they have to
> be parsed again and again.
>
> 2 may be faster or slower than 1, I don't know, a quick check didn't show a
> difference. When the template instantiation issue ever gets fixed, I
> wouldn't be surprised if 2 got slower than 1. Of course, any slowness of 2
> must then be weighed against 1 compiling more than necessary.

In theory 2 should be faster when it comes to recompiling because fewer files need to be recompiled.

-- 
/Jacob Carlborg

Am 26.09.2015 um 10:23 schrieb Andy Smith:
> HI Atilla,
>
> Dub's looking interesting! Some of the links are broken when browsing
> from code.dlang.org though.
>
>  From http://code.dlang.org/packages/reggae
>
> click on, say, 'detailed documentation'. ( Where I wanted to go!).
>
> Get ..
>
> 404 - Not Found
>
> Not Found
>
> Internal error information:
> No routes match path '/packages/doc/index.md'
>
>
> Not sure if that's problem with reggae's layout of the site....
>
> Cheers,
>
> A.

That was due to a missing feature (special handling for relative links) of code.dlang.org. Fixed now.

On Saturday, 26 September 2015 at 03:51:11 UTC, Jason White wrote:
> I rarely visit the D forums and even more rarely make a post, but this thread caught my eye.
>
> I've been writing a build system in D too: https://github.com/jasonwhite/brilliant-build (I'm not very fond of the name. Naming is hard!)
>
> It is a general build system with an emphasis on correctness.
>
> It is a work in progress at this point, but I'm very happy with how it is turning out. I'm interested in your guys' thoughts on it.

Looks good as a work-in-progress. A lot of the same ideas I used,
including scripting languages as a way to describe builds.

I'm probably going to use reggae though ;)

Atila