On Thursday, 10 July 2014 at 10:15:39 UTC, simendsjo wrote:
> On 07/10/2014 11:34 AM, Dicebot wrote:
>> On Thursday, 10 July 2014 at 05:27:56 UTC, simendsjo wrote:
>>> On 07/10/2014 01:22 AM, "Nordlöw" wrote:
>>>> On Wednesday, 9 July 2014 at 18:26:53 UTC, simendsjo wrote:
>>>>> Would it make sense to add them to the dtools repository?
>>>>
>>>> It's already included there as a submodule :)
>>>
>>> Hidden in plain sight.
>> 
>> Wait what? Are you speaking about
>> https://github.com/D-Programming-Language/tools ?
>
> I was mostly thinking about the lack of visibility on the wiki and
> homepage. And while dustmite is there, digger is not.

I was referring to the fact that tools repo has no submodules and
was confused what Nordlöw has in mind.

On Wednesday, 9 July 2014 at 16:00:47 UTC, Andrei Alexandrescu wrote:
> http://www.reddit.com/r/programming/comments/2a8xf4/dconf_2014_day_2_talk_4_reducing_d_bugs_by/
>
> https://www.facebook.com/dlang.org/posts/881813965165619
>
> https://news.ycombinator.com/newest (please find and vote quickly)
>
> https://twitter.com/D_Programming/status/486902390399180801
>

Since this talk I've used Digger twice to find where an issue was incidentally fixed (i.e. reversed search.)

The only hiccup I ran into was when the first slice of history wouldn't build. Simply moving the start/end point was good enough to allow it to find the commit I was looking for.

Digger is awesome. Have never heard of it before this talk.

Unfortunately it's a huge PITA to get a Win64 build with it cause of those stupid hardcoded "\Program Files (x86)\Microsoft Visual Studio 10.0\VC" paths. The modified makefiles etc are always reverted by Digger before building.

On 13.07.2014 19:35, Trass3r wrote:
> Digger is awesome. Have never heard of it before this talk.
>
> Unfortunately it's a huge PITA to get a Win64 build with it cause of
> those stupid hardcoded "\Program Files (x86)\Microsoft Visual Studio
> 10.0\VC" paths. The modified makefiles etc are always reverted by Digger
> before building.

You can add the compiler to the make command line with some magic quoting.

My build script calls

druntime:
make -f win64.mak DMD=../windows/bin/dmd.exe "CC=\"c:\l\vc10\bin64\cl.exe\"" target

phobos:
make -f win64.mak DMD=../windows/bin/dmd.exe "CC=\"c:\l\vc10\bin64\cl.exe\"" MAKE=c:\l\dmc\bin\make "AR=\"c:/l/vc10/bin64/lib.exe\"" LIB=..\lib64\phobos64.lib

> You can add the compiler to the make command line with some magic quoting.
>
> My build script calls
>
> druntime:
> make -f win64.mak DMD=../windows/bin/dmd.exe "CC=\"c:\l\vc10\bin64\cl.exe\"" target
>
> phobos:
> make -f win64.mak DMD=../windows/bin/dmd.exe "CC=\"c:\l\vc10\bin64\cl.exe\"" MAKE=c:\l\dmc\bin\make "AR=\"c:/l/vc10/bin64/lib.exe\"" LIB=..\lib64\phobos64.lib

Isn't the make call hardcoded in Digger?

On 13.07.2014 20:43, Trass3r wrote:
>> You can add the compiler to the make command line with some magic
>> quoting.
>>
>> My build script calls
>>
>> druntime:
>> make -f win64.mak DMD=../windows/bin/dmd.exe
>> "CC=\"c:\l\vc10\bin64\cl.exe\"" target
>>
>> phobos:
>> make -f win64.mak DMD=../windows/bin/dmd.exe
>> "CC=\"c:\l\vc10\bin64\cl.exe\"" MAKE=c:\l\dmc\bin\make
>> "AR=\"c:/l/vc10/bin64/lib.exe\"" LIB=..\lib64\phobos64.lib
>
> Isn't the make call hardcoded in Digger?

I don't know, never used digger so far. I just remembered the problem with win64.mak.

> druntime:
> make -f win64.mak DMD=../windows/bin/dmd.exe "CC=\"c:\l\vc10\bin64\cl.exe\"" target
>
> phobos:
> make -f win64.mak DMD=../windows/bin/dmd.exe "CC=\"c:\l\vc10\bin64\cl.exe\"" MAKE=c:\l\dmc\bin\make "AR=\"c:/l/vc10/bin64/lib.exe\"" LIB=..\lib64\phobos64.lib

That works?
So it probably doesn't need the includes set in the makefile.

Nope doesn't.
Setting VCDIR and SDKDIR via the make command works.

On 14.07.2014 16:55, Trass3r wrote:
> Nope doesn't.
> Setting VCDIR and SDKDIR via the make command works.

Works for me. Maybe you need a newer version of make (there was a silent update in 2012, my version is 5.06).

This kind of escaping also depends a lot on the used shell, I'm just using cmd.exe.

>> Setting VCDIR and SDKDIR via the make command works.
>
> Works for me. Maybe you need a newer version of make (there was a silent update in 2012, my version is 5.06).

Well if you don't set VCDIR you won't get proper include paths.
So no clue why it works for you.