Most notable change since DConf is that on Windows, Digger can now build D from source (including x64 versions) without requiring Git or Visual Studio to be installed. It achieves this by downloading and locally installing (unpacking) all the software it needs.

Windows binaries:

https://github.com/CyberShadow/Digger/releases/tag/1.0

Digger is a tool for working with D's source code and its history. It can build D (including older D versions), customize the build with pending pull requests or forks, and find the exact pull request which introduced a regression (or fixed a bug). It comes together with a web interface which makes building D from source trivial even for people new to D, Git or the command line.

https://github.com/CyberShadow/Digger

On Friday, 19 September 2014 at 01:36:54 UTC, Vladimir Panteleev wrote:
> Windows binaries:
>
> https://github.com/CyberShadow/Digger/releases/tag/1.0

Yet another release ruined by a DMD -inline wrong-code bug :(

Reuploaded new .zip file without -inline.

On 19.09.2014 03:36, Vladimir Panteleev wrote:
> Most notable change since DConf is that on Windows, Digger can now build
> D from source (including x64 versions) without requiring Git or Visual
> Studio to be installed. It achieves this by downloading and locally
> installing (unpacking) all the software it needs.
>
> Windows binaries:
>
> https://github.com/CyberShadow/Digger/releases/tag/1.0
>
> Digger is a tool for working with D's source code and its history. It
> can build D (including older D versions), customize the build with
> pending pull requests or forks, and find the exact pull request which
> introduced a regression (or fixed a bug). It comes together with a web
> interface which makes building D from source trivial even for people new
> to D, Git or the command line.
>
> https://github.com/CyberShadow/Digger

I tried it on Windows and Digger does an amazing job at installing dependencies. I think we should recommend it as the first thing to run when trying to get your hands on building dmd/phobos.

In case someone starts creating patches: Would it be possible to also write a batch file into the repository folder to redo a build of dmd, druntime and phobos without checking all the dependencies?

How about running the test suite?

On Sunday, 21 September 2014 at 17:43:14 UTC, Rainer Schuetze wrote:
> How about running the test suite?

+1
Would make me far more happier of starting seriously getting into dmd bug fixing.

On 21/09/2014 18:43, Rainer Schuetze wrote:
> I tried it on Windows and Digger does an amazing job at installing
> dependencies. I think we should recommend it as the first thing to run
> when trying to get your hands on building dmd/phobos.

+1

> In case someone starts creating patches: Would it be possible to also
> write a batch file into the repository folder to redo a build of dmd,
> druntime and phobos without checking all the dependencies?

Sometimes my Windows machine with 2 GB RAM gets OOM when trying to link phobos.lib (I have to close most programs and start again), it would be nice if there was a way to continue a failed build without starting from scratch.

I also hope there's a way of making the link take less memory, perhaps by making sub-libraries first and linking those together.

> How about running the test suite?

AFAICT the test suite needs a separate MSYS install from the one Git uses, e.g. for a newer version of 'diff'. Not sure if that makes it harder for Digger to support.

On 09/22/2014 12:50 PM, Nick Treleaven wrote:
(...)
> Sometimes my Windows machine with 2 GB RAM gets OOM when trying to link phobos.lib (I have to close most programs and start again), it would be nice if there was a way to continue a failed build without starting from scratch.

My guess is the average for developers is ~8GB. 2GB RAM is really not enough for pretty much anything these days - the browser alone easily chews 3-4GB on moderate use. I recommend you just upgrade your computer (or compile on a better iron).

On Mon, 22 Sep 2014 15:24:55 +0200
simendsjo via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> My guess is the average for developers is ~8GB. 2GB RAM is really not enough for pretty much anything these days - the browser alone easily chews 3-4GB on moderate use. I recommend you just upgrade your computer (or compile on a better iron).
are your primary language is java? i'm asking just out of curiousity.

On Monday, 22 September 2014 at 10:50:51 UTC, Nick Treleaven wrote:
> AFAICT the test suite needs a separate MSYS install from the one Git uses, e.g. for a newer version of 'diff'. Not sure if that makes it harder for Digger to support.

It shouldn't be too hard. The difficult part is getting the environment right (e.g. the DMD test suite needs GNU make.exe but DigitalMars link.exe).

Downloading / installing more stuff should be easy. See e.g. the code for the Git installer:

https://github.com/CyberShadow/ae/blob/master/sys/install/git.d

On 09/22/2014 07:28 PM, ketmar via Digitalmars-d-announce wrote:
> On Mon, 22 Sep 2014 15:24:55 +0200
> simendsjo via Digitalmars-d-announce
> <digitalmars-d-announce@puremagic.com> wrote:
> 
>> My guess is the average for developers is ~8GB. 2GB RAM is really not enough for pretty much anything these days - the browser alone easily chews 3-4GB on moderate use. I recommend you just upgrade your computer (or compile on a better iron).
> are your primary language is java? i'm asking just out of curiousity.
> 

C#. Visual Studio requires quite a bit of memory; but template-heavy D isn't exactly light on memory either.

On Monday, 22 September 2014 at 17:28:50 UTC, ketmar via Digitalmars-d-announce wrote:
> On Mon, 22 Sep 2014 15:24:55 +0200
> simendsjo via Digitalmars-d-announce
> <digitalmars-d-announce@puremagic.com> wrote:
>
>> My guess is the average for developers is ~8GB. 2GB RAM is really not
>> enough for pretty much anything these days - the browser alone easily
>> chews 3-4GB on moderate use. I recommend you just upgrade your
>> computer (or compile on a better iron).
> are your primary language is java? i'm asking just out of curiousity.

That was uncalled for.

Firefox requires 4GB of memory to build.
Chromium requires 8GB of memory to build.
Android requires 16GB of memory to build.

If you want to work on big projects, you WILL need a decent computer.

I think 4GB for a modern programming language's implementation is not an unreasonable requirement, even if it could be brought down in the future. Especially considering that you can't even buy a new laptop today with less than 4GB of RAM, and 3GB is becoming the norm for smartphones.