Jump to page: 1 2
Thread overview
Digger 1.1
Mar 04, 2015
Vladimir Panteleev
Mar 07, 2015
Robert M. Münch
Mar 07, 2015
Vladimir Panteleev
Mar 08, 2015
Robert M. Münch
Mar 08, 2015
Daniel Murphy
Mar 18, 2015
Vladimir Panteleev
Mar 19, 2015
Robert M. Münch
Mar 19, 2015
Vladimir Panteleev
Mar 25, 2015
Robert M. Münch
Mar 25, 2015
Vladimir Panteleev
Mar 26, 2015
Robert M. Münch
Apr 03, 2015
Robert M. Münch
Apr 03, 2015
Vladimir Panteleev
Mar 18, 2015
Martin Nowak
Mar 18, 2015
Vladimir Panteleev
March 04, 2015
This release brings the following improvements:

An "install" action was added, which can upgrade an existing D install (such as from an official ZIP archive, OS installer or package, or DVM). This allows combining components of D which Digger builds (DMD, Druntime, Phobos and rdmd) with those which rarely change, are more difficult to build, or require external dependencies (e.g. Windows static libraries and ancillary tools). Running `digger install` can also be used as an alternative to adding Digger's result directory to your PATH, and can be safely undone at any time by running `digger uninstall`.

Sergei Nosov contributed a "rebuild" action, which will incrementally rebuild D's components after a few changes. This should make it much easier to use Digger for developing patches for D's components.

Digger now uses ae.utils.funopt (http://blog.thecybershadow.net/2014/08/05/ae-utils-funopt/) for comprehensive, automatically generated --help text, for `digger` itself as well as each of its subcommands.

A --make-args option was added to the "build" commands, as well as a --model option to replace the --64 switch.

`digger-web` learned the --host and --port options to explicitly set how to listen for HTTP requests.

Finally, this is the first stable release with binary downloads for all major platforms:

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

---

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 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
March 07, 2015
On 2015-03-04 04:54:02 +0000, Vladimir Panteleev said:

> 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 with a web interface which makes building D from source trivial even for people new to D, Git or the command line.

Hi, that's pretty cool.

It supports the beta versions as well, right? And I can switch back and forther using it between beta and latest stable?

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

March 07, 2015
On Saturday, 7 March 2015 at 19:19:30 UTC, Robert M. Münch wrote:
> On 2015-03-04 04:54:02 +0000, Vladimir Panteleev said:
>
>> 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 with a web interface which makes building D from source trivial even for people new to D, Git or the command line.
>
> Hi, that's pretty cool.
>
> It supports the beta versions as well, right? And I can switch back and forther using it between beta and latest stable?

That is one of the project's goals. "digger build" will default to git master.
March 08, 2015
On 2015-03-07 22:40:04 +0000, Vladimir Panteleev said:

> That is one of the project's goals. "digger build" will default to git master.

Ok, great. I just tried it on Windows and get this here:

digger: Done installing DigitalMars C++.
digger: dmcDir=dl\dm
digger: Preparing to build...
digger: DMC=D:\develop\d-language\Digger\dl\dm\bin
digger: Building...
digger: PATH=C:\WINDOWS\system32;C:\WINDOWS;D:\develop\d-language\Digger\build\bin;D:\develop\d-language\Digger\dl\dm\bin 

make -fwin32.mak C=backend TK=tk ROOT=root HOST_DC= "OPT=-o" "DEBUG=" "LFLAGS=-L/delexe/la" dmd.exe
run idgen
Error: 'run' not found

--- errorlevel 1
Fatal error: Command ["make", "-f", "win32.mak", "MODEL=32", "dmd"] failed with status 1


Any idea?

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

March 08, 2015
"Robert M. Münch"  wrote in message news:mdi3sn$jh8$1@digitalmars.com...

> make -fwin32.mak C=backend TK=tk ROOT=root HOST_DC= "OPT=-o" "DEBUG=" "LFLAGS=-L/delexe/la" dmd.exe
> run idgen
> Error: 'run' not found

dmd has very recently been changed to required dmd already installed on the system.  Until digger is updated to take this into account, you can probably get it to work by defining the environment variable HOST_DC to point to your installed dmd.

The error message is because it's trying to run this:
$(HOST_DC) -run idgen.d
which expands to this
-run idgen.d 

March 18, 2015
On Sunday, 8 March 2015 at 18:20:07 UTC, Robert M. Münch wrote:
> Ok, great. I just tried it on Windows and get this here:

I've pushed support for DMD bootstrapping, so if you need to build master now, build latest Digger from source. I'll make a binary release after 2.067 is out.
March 18, 2015
On 03/04/2015 05:54 AM, Vladimir Panteleev wrote:
> Finally, this is the first stable release with binary downloads for all major platforms:

Nice, out of curiosity. How did you build the releases for all the platforms?
March 18, 2015
On Wednesday, 18 March 2015 at 18:18:19 UTC, Martin Nowak wrote:
> On 03/04/2015 05:54 AM, Vladimir Panteleev wrote:
>> Finally, this is the first stable release with binary downloads for all
>> major platforms:
>
> Nice, out of curiosity. How did you build the releases for all the platforms?

Natively for Windows and Linux (used the server for that), and virtual machines for FreeBSD and OSX (I do own a Mac though). I managed to get one shell script working on all Posix platforms.

Here's my build script:

http://dump.thecybershadow.net/449edd68e2ad8fe835236de1f3244688/out.sh
March 19, 2015
On 2015-03-18 12:14:01 +0000, Vladimir Panteleev said:

> I've pushed support for DMD bootstrapping, so if you need to build master now, build latest Digger from source. I'll make a binary release after 2.067 is out.

I just tried it and get this here:

Entering 'phobos'
Entering 'tools'
error: Your local changes to the following files would be overwritten by checkout:
       test/d_do_test.d
Please, commit your changes or stash them before you can switch branches.
Aborting
Unable to checkout '229edba461ef6f6e2254e060eb498f302e982563' in submodule path 'dmd'
Fatal error: Command ["git", "--work-tree=D:\\develop\\d-language\\Digger\\repo", "--git-dir=D:\\develop\\d-language\\Di
gger\\repo\\.git", "submodule", "update"] failed with status 1



I don't have done any changes to "test/d_do_test.d" so no idea what this means or where it comes from... any idea?

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

March 19, 2015
On Thursday, 19 March 2015 at 15:40:19 UTC, Robert M. Münch wrote:
> On 2015-03-18 12:14:01 +0000, Vladimir Panteleev said:
>
>> I've pushed support for DMD bootstrapping, so if you need to build master now, build latest Digger from source. I'll make a binary release after 2.067 is out.
>
> I just tried it and get this here:
>
> Entering 'phobos'
> Entering 'tools'
> error: Your local changes to the following files would be overwritten by checkout:
>        test/d_do_test.d
> Please, commit your changes or stash them before you can switch branches.
> Aborting
> Unable to checkout '229edba461ef6f6e2254e060eb498f302e982563' in submodule path 'dmd'
> Fatal error: Command ["git", "--work-tree=D:\\develop\\d-language\\Digger\\repo", "--git-dir=D:\\develop\\d-language\\Di
> gger\\repo\\.git", "submodule", "update"] failed with status 1
>
>
>
> I don't have done any changes to "test/d_do_test.d" so no idea what this means or where it comes from... any idea?

Hmm... Does it happen with a fresh Digger install?

What is your core.autocrlf set to?
« First   ‹ Prev
1 2