Georg Wrede:
> bearophile wrote:
> > [...] despite LDC looks like the best bet for the close future of D.
>
> Would you care to elaborate?
I know very little about compilers, so it's better for you to ask similar
questions to LDC developers or other people. Most people around here seems to
know
bearophile wrote:
[...] despite LDC looks like the best bet for the close future of D.
Would you care to elaborate?
grauzone wrote:
Jarrett Billingsley wrote:
On Sat, Mar 21, 2009 at 2:50 PM, grauzone wrote:
What I need is to make dsss completely recompile the project, even if
only a
single source file was modified. This way, no errors should occur,
and it
would still be faster than with oneatatime=yes.
Brian wrote:
On Sat, 21 Mar 2009 15:44:41 +0100, grauzone wrote:
I'm using dsss (with dmd under Linux) to compile my project, and
build/compile times are reaching unacceptable highs.
out of curiosity, how much code do you actually have? im using D for
something with ~12,000 lines of code rig
On Sat, 21 Mar 2009 15:44:41 +0100, grauzone wrote:
> I'm using dsss (with dmd under Linux) to compile my project, and
> build/compile times are reaching unacceptable highs.
out of curiosity, how much code do you actually have? im using D for
something with ~12,000 lines of code right now, sprea
I use bud, which builds everything with a single run of dmd, but uses
incremental compilation. If I get linker errors, I just run my cleanup
script and try again. Or add -full to bud's command line.
In my case, this practically always causes linker errors. Of course I
don't know why.
Jarrett Billingsley wrote:
On Sat, Mar 21, 2009 at 2:50 PM, grauzone wrote:
What I need is to make dsss completely recompile the project, even if only a
single source file was modified. This way, no errors should occur, and it
would still be faster than with oneatatime=yes.
-full
Sorry for
On 21.03.2009 19:50, grauzone wrote:
Christopher Wright wrote:
grauzone wrote:
PS: another thing that possibly would bring a speed gain would be to
make dsss compile the whole project in one run, instead of invoking a
new dmd process for each source file. How do I need to change the
rebuil
On Sat, Mar 21, 2009 at 2:50 PM, grauzone wrote:
> What I need is to make dsss completely recompile the project, even if only a
> single source file was modified. This way, no errors should occur, and it
> would still be faster than with oneatatime=yes.
-full
Christopher Wright wrote:
grauzone wrote:
PS: another thing that possibly would bring a speed gain would be to
make dsss compile the whole project in one run, instead of invoking a
new dmd process for each source file. How do I need to change the
rebuild configuration to achieve this?
oneata
grauzone wrote:
PS: another thing that possibly would bring a speed gain would be to
make dsss compile the whole project in one run, instead of invoking a
new dmd process for each source file. How do I need to change the
rebuild configuration to achieve this?
oneatatime = [yes|no]
You want '
grauzone schrieb:
The closest thing that I know is "dsss build -v"
Thanks, that's what I needed.
The cause seems to be that it uses dsss/include/d but links to the
libraries in the dmd directory.
test.d => test_lyla
+ D:\dmddwt\dsss\bin\rebuild.exe -Idsss_imports\ -I. -S.\
-ID:\dmddwt\dsss
The closest thing that I know is "dsss build -v"
I'm using dsss (with dmd under Linux) to compile my project, and
build/compile times are reaching unacceptable highs.
What are some tips to speed up the build process?
For example, I could imagine that heavy use of templates and CTFE slows
the compiler down. Maybe string mixins with CTFE on th
Is there a verbose mode for DSSS to see which commands it actually executes?
The dsss.conf is simply
name=lyla
[lyla]
[test.d]
I'm getting some linker errors that don't come up when compiling
manually with dmd (using the lyla lib created by dsss, just passing it
to dmd along with test.d).
O
15 matches
Mail list logo
