I cloned the package and ran install.bat.

The result is

$ dub build --build=release --config=client
Performing "release" build using ldc2 for x86.
experimental_allocator 2.70.0-b1: building configuration "library"...
Using Visual Studio: C:\Program Files (x86)\Microsoft Visual Studio 14.0\
LINK : fatal error LNK1104: cannot open file '..\..\..\..\Roaming\dub\packages\experimental_allocator-2.70.0-b1\experimental_allocator\.dub\build\library-release-windows-x86-ldc_0-341F845AB271E17D9C62794DCB77B6FB\experimental_allocator.lib'
Error: `C:\WINDOWS\system32\cmd.exe /s /c "C:\D\ldc2\bin\amd64.bat lib.exe"` failed with status: 1104
ldc2 failed with exit code 1104.
Error while compiling DCD.
Program exited with code 1

There is on --config=client for the current version of dub so I went to the location of the source for experimental_allocator and ran dub build --build=release --config=library instead, which generated the missing file. Problem is I don't know how to fix this in your build instructions so that the compellation will resume or continue to completion. Please assist.

Thanks,
Andrew

On Tuesday, 5 July 2016 at 19:14:32 UTC, Andrew Edwards wrote:
> I cloned the package and ran install.bat.
>
> The result is
>
> $ dub build --build=release --config=client
> Performing "release" build using ldc2 for x86.
> experimental_allocator 2.70.0-b1: building configuration "library"...
> Using Visual Studio: C:\Program Files (x86)\Microsoft Visual Studio 14.0\
> LINK : fatal error LNK1104: cannot open file '..\..\..\..\Roaming\dub\packages\experimental_allocator-2.70.0-b1\experimental_allocator\.dub\build\library-release-windows-x86-ldc_0-341F845AB271E17D9C62794DCB77B6FB\experimental_allocator.lib'
> Error: `C:\WINDOWS\system32\cmd.exe /s /c "C:\D\ldc2\bin\amd64.bat lib.exe"` failed with status: 1104
> ldc2 failed with exit code 1104.
> Error while compiling DCD.
> Program exited with code 1
>
> There is on --config=client for the current version of dub so I went to the location of the source for experimental_allocator and ran dub build --build=release --config=library instead, which generated the missing file. Problem is I don't know how to fix this in your build instructions so that the compellation will resume or continue to completion. Please assist.
>
> Thanks,
> Andrew

It fails on installing DCD. On the installation.bat just select 2,3 and get prebuilt DCD binaries from the project page or build them yourself.

I could maybe add an option to compile from source and instead ship pre-built binaries from the github repositories instead.

On Tuesday, 5 July 2016 at 19:25:50 UTC, WebFreak001 wrote:
> On Tuesday, 5 July 2016 at 19:14:32 UTC, Andrew Edwards wrote:
>> [...]
>
> It fails on installing DCD. On the installation.bat just select 2,3 and get prebuilt DCD binaries from the project page or build them yourself.
>
> I could maybe add an option to compile from source and instead ship pre-built binaries from the github repositories instead.

Actually DCD doesn't have any pre-built binaries yet. But following the compilation guide on the project page¹ should help you compile it. Not sure if it works with LDC but it definitely works with DMD*

¹: https://github.com/Hackerpilot/DCD
*: assuming its the newest version

On Tuesday, 5 July 2016 at 19:25:50 UTC, WebFreak001 wrote:
> On Tuesday, 5 July 2016 at 19:14:32 UTC, Andrew Edwards wrote:
>>
>> There is on --config=client for the current version of dub so I went to the location of the source for experimental_allocator and ran dub build --build=release --config=library instead, which generated the missing file. Problem is I don't know how to fix this in your build instructions so that the compellation will resume or continue to completion. Please assist.
>>
> It fails on installing DCD. On the installation.bat just select 2,3 and get prebuilt DCD binaries from the project page or build them yourself.
>

It's more than that. Now, it fails because it can't find DMD. Now, I see no reason to use both DMD and LDC. Ultimately I'd like to use DMD because it is the simplest to install for a newcomer but your workspace-d/code-d requires LDC on windows platforms. If that's the case why would it now be failing because it cannot find DMD?

On Tuesday, 5 July 2016 at 19:34:48 UTC, Andrew Edwards wrote:
> On Tuesday, 5 July 2016 at 19:25:50 UTC, WebFreak001 wrote:
>> On Tuesday, 5 July 2016 at 19:14:32 UTC, Andrew Edwards wrote:
>>>
>>> There is on --config=client for the current version of dub so I went to the location of the source for experimental_allocator and ran dub build --build=release --config=library instead, which generated the missing file. Problem is I don't know how to fix this in your build instructions so that the compellation will resume or continue to completion. Please assist.
>>>
>> It fails on installing DCD. On the installation.bat just select 2,3 and get prebuilt DCD binaries from the project page or build them yourself.
>>
>
> It's more than that. Now, it fails because it can't find DMD. Now, I see no reason to use both DMD and LDC. Ultimately I'd like to use DMD because it is the simplest to install for a newcomer but your workspace-d/code-d requires LDC on windows platforms. If that's the case why would it now be failing because it cannot find DMD?

As you can see in the build.bat from DCD it is hardcoded to DMD: https://github.com/Hackerpilot/DCD/blob/master/build.bat

So I guess you would need to use some DMD argument wrapper for LDC (ldmd) to compile it but I can't guarantee that it will work. Though if you have LDC v1.0.0 it should most probably work.

I would love to support DMD on workspace-d for windows but there is some bug in DMD's phobos causing workspace-d to hang every time you want to start the auto completion service. We found where it hangs but we couldn't find the cause or how to reproduce it yet. My best guess would be some win32 I/O functions are somehow wrongly used in there.

The LDC phobos version doesn't have any issue there.

But if DCD doesn't compile with LDC, I don't think there is a way other than getting both DMD and LDC right now except if you are on linux.

On Tuesday, 5 July 2016 at 19:43:02 UTC, WebFreak001 wrote:
> On Tuesday, 5 July 2016 at 19:34:48 UTC, Andrew Edwards wrote:
>>
>> It's more than that. Now, it fails because it can't find DMD.
>
> As you can see in the build.bat from DCD it is hardcoded to DMD: https://github.com/Hackerpilot/DCD/blob/master/build.bat
>

Maybe I should have been a little clearer. Following your instructions from earlier (skip DCD by selecting 2,3) the process failed again:

'dmd' is not recognized as an internal or external command,
operable program or batch file.
Error while compiling Dscanner.
Program exited with code 1

> But if DCD doesn't compile with LDC, I don't think there is a way other than getting both DMD and LDC right now except if you are on linux.

It's not that LDC cannot compile DCD in this case, it's that your build script is searching for DMD when it cannot use DMD.

On Tuesday, 5 July 2016 at 19:58:03 UTC, Andrew Edwards wrote:
> On Tuesday, 5 July 2016 at 19:43:02 UTC, WebFreak001 wrote:
>> On Tuesday, 5 July 2016 at 19:34:48 UTC, Andrew Edwards wrote:
>>>
>>> It's more than that. Now, it fails because it can't find DMD.
>>
>> As you can see in the build.bat from DCD it is hardcoded to DMD: https://github.com/Hackerpilot/DCD/blob/master/build.bat
>>
>
> Maybe I should have been a little clearer. Following your instructions from earlier (skip DCD by selecting 2,3) the process failed again:
>
> 'dmd' is not recognized as an internal or external command,
> operable program or batch file.
> Error while compiling Dscanner.
> Program exited with code 1
>
>> But if DCD doesn't compile with LDC, I don't think there is a way other than getting both DMD and LDC right now except if you are on linux.
>
> It's not that LDC cannot compile DCD in this case, it's that your build script is searching for DMD when it cannot use DMD.

Oh right it runs the build.bat from the Dscanner repository which is also hardcoded to DMD. So easiest way to build workspace-d right now is just getting DMD and LDC.

On Tuesday, 5 July 2016 at 19:58:03 UTC, Andrew Edwards wrote:
> On Tuesday, 5 July 2016 at 19:43:02 UTC, WebFreak001 wrote:
>> On Tuesday, 5 July 2016 at 19:34:48 UTC, Andrew Edwards wrote:
>>>
>>> It's more than that. Now, it fails because it can't find DMD.
>>
>> As you can see in the build.bat from DCD it is hardcoded to DMD: https://github.com/Hackerpilot/DCD/blob/master/build.bat
>>
>
> Maybe I should have been a little clearer. Following your instructions from earlier (skip DCD by selecting 2,3) the process failed again:
>
> 'dmd' is not recognized as an internal or external command,
> operable program or batch file.
> Error while compiling Dscanner.
> Program exited with code 1
>
>> But if DCD doesn't compile with LDC, I don't think there is a way other than getting both DMD and LDC right now except if you are on linux.
>
> It's not that LDC cannot compile DCD in this case, it's that your build script is searching for DMD when it cannot use DMD.

in the .bat you can try to replace "dmd" with "ldmd2". ldmd2 allows to compile with LDC but with DMD command line interface. I can't guarantee that it gonna work but this is the simpliest option.