On 2015-07-29 13:12, Jacob Carlborg wrote:

> I noticed building the installer for OS X relies on that as well.

Never mind, I looked at an old version of the makefile.

-- 
/Jacob Carlborg

On Wednesday, 29 July 2015 at 11:56:34 UTC, Kagamin wrote:
> On Wednesday, 29 July 2015 at 01:55:35 UTC, Joseph Cassman wrote:
>> There is probably an obvious reason this is not possible but I could not see it when reading through the MS licensing information. It seems to me the linker bin could be redistributed.
>
>> 9. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights.
>
> So you should find an expressly granted right to redistribute.

Apparently Intel was able to redistribute it with their fortran compiler.

Intel® Visual Fortran development environment based on Microsoft Visual Studio 2010 Shell is included with Academic and Commercial licenses for Intel® Visual Fortran. It is not included with Evaluation or Student licenses. This development environment provides everything necessary to edit, build and debug Fortran applications. Some features of the full Visual Studio product are not included, such as:
Resource Editor (see ResEdit*, a third-party tool, for a substitute)
Automated conversion of Compaq* Visual Fortran projects

I guess what I mean to say is that they did it, maybe it can be done. Of course VS Shell is still way more than is necessary for our purposes.

On Wednesday, 29 July 2015 at 15:45:19 UTC, Taylor Hillegeist wrote:
> I guess what I mean to say is that they did it, maybe it can be done.

Of course it can be done with an additional license agreement with microsoft.

> Of course VS Shell is still way more than is necessary for our purposes.

I believe VS shell is redistributable, because it was made exactly for that.

On Wednesday, 29 July 2015 at 07:16:39 UTC, Martin Nowak wrote:
> On Wednesday, 29 July 2015 at 07:10:13 UTC, Martin Nowak wrote:
>> You're not allowed to redistribute the VS binaries, only the libc dlls.
>> On Win32 we use our own libc (dmc) and linker (optlink).
>> We could improve our installer so it can optionally start the VS compiler installation.
>
> https://issues.dlang.org/show_bug.cgi?id=14847

Martin, appreciate the help with this issue. I have investigated further and it looks like there is a work-around (item [3] below). Here is a synopsis of what I have found through testing.

1) Windows 7 SDK will not install completely now that I have .NET 4.5.1 installed (it requires version 4). It incorrectly considers the newer runtime as not as up-to-date.

2) Windows 8.1 SDK does not include a console build system (c.f. [1]). Thanks for pointing that out in your previous post. That page coincides with what I found in my testing.

3) The VS Community 2013 with Update 5 installation [2] includes a complete build system that works with the DMD Windows installer (tested with version 2.068.0-b2). This is what should be used with DMD now since it is free and works with the current .NET runtime.

4) The VS 2015 Community 2015 installation [2] also includes a complete build system. However, the DMD Windows installer does not recognize it and fails to update the sc.ini file accordingly. I will file a bug report shortly with details.

It is taking a while to do all of the un/installs to get a relevant test environment. So I thought I would make this post about what I have found. Thought it might help with your trying to get the 068 release out the door. After I have finished my testing I will update the DMD Win64 wiki page with what is currently working.

Thanks again for the help.

Joseph

[1] https://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx
[2] https://www.visualstudio.com/en-us/downloads#d-community

On Wednesday, 29 July 2015 at 18:13:22 UTC, Kagamin wrote:
> On Wednesday, 29 July 2015 at 15:45:19 UTC, Taylor Hillegeist wrote:
>> I guess what I mean to say is that they did it, maybe it can be done.
>
> Of course it can be done with an additional license agreement with microsoft.
>
>> Of course VS Shell is still way more than is necessary for our purposes.
>
> I believe VS shell is redistributable, because it was made exactly for that.

Yeah, if the linker (and other relevant files) for Win64 could be licensed from MS so they could be packaged with the DMD installer that would be a sweet deal. I know D is in bootstrap mode right now but this could be one of the things that helps get it to the necessary polished phase that helps get the acceptance past the 10,000 mark.

It takes a standard half-day or so to install Visual Studio. So any way to make setting up a Win64 environment faster is much appreciated. And I would feel necessary to get wide acceptance.

Joseph

Am 30.07.2015 um 02:59 schrieb Joseph Cassman:
> 4) The VS 2015 Community 2015 installation [2] also includes a complete
> build system. However, the DMD Windows installer does not recognize it
> and fails to update the sc.ini file accordingly. I will file a bug
> report shortly with details.

I think you have an old version of VisualD, perhaps the 0.3.38 from [1]? That just happened to me yesterday, because that page is the number one Google result and the out-of-date note is quite small. I think the dsource project should just be removed, or replaced by nothing than a single link to the new homepage [2].

[1]: http://www.dsource.org/projects/visuald
[2]: http://rainers.github.io/visuald/visuald/StartPage.html

On Thursday, 30 July 2015 at 00:59:16 UTC, Joseph Cassman wrote:
> 4) The VS 2015 Community 2015 installation [2] also includes a complete build system. However, the DMD Windows installer does not recognize it and fails to update the sc.ini file accordingly. I will file a bug report shortly with details.

https://issues.dlang.org/show_bug.cgi?id=14849

Am 30.07.2015 um 09:49 schrieb Sönke Ludwig:
> Am 30.07.2015 um 02:59 schrieb Joseph Cassman:
>> 4) The VS 2015 Community 2015 installation [2] also includes a complete
>> build system. However, the DMD Windows installer does not recognize it
>> and fails to update the sc.ini file accordingly. I will file a bug
>> report shortly with details.
>
> I think you have an old version of VisualD, perhaps the 0.3.38 from [1]?
> That just happened to me yesterday, because that page is the number one
> Google result and the out-of-date note is quite small. I think the
> dsource project should just be removed, or replaced by nothing than a
> single link to the new homepage [2].
>
> [1]: http://www.dsource.org/projects/visuald
> [2]: http://rainers.github.io/visuald/visuald/StartPage.html

Hm, I just installed VisualD on a freshly installed machine and there I get an error "libucrt.lib not found", so I probably just had some files left over from previous VS versions or SDKs.

On Wednesday, 29 July 2015 at 18:13:22 UTC, Kagamin wrote:
> On Wednesday, 29 July 2015 at 15:45:19 UTC, Taylor Hillegeist wrote:
>> I guess what I mean to say is that they did it, maybe it can be done.
>
> Of course it can be done with an additional license agreement with microsoft.
>
>> Of course VS Shell is still way more than is necessary for our purposes.
>
> I believe VS shell is redistributable, because it was made exactly for that.

It's in the name:

https://www.microsoft.com/en-us/download/details.aspx?id=46886

On 29.07.2015 09:10, Martin Nowak wrote:
> On Wednesday, 29 July 2015 at 01:55:35 UTC, Joseph Cassman wrote:
>> There is probably an obvious reason this is not possible but I could
>> not see it when reading through the MS licensing information. It seems
>> to me the linker bin could be redistributed. Why is it (and the other
>> required lib/dll files) not bundled with the Windows installer to make
>> it one-stop-shopping?
>>
>> Seems like this is what is done with Win32.
>
> You're not allowed to redistribute the VS binaries, only the libc dlls.
> On Win32 we use our own libc (dmc) and linker (optlink).
> We could improve our installer so it can optionally start the VS
> compiler installation.

Digger [1] is able to download the installers, but just extract the packages needed to link DMD built executables for win64. I'm not sure whether this is in compliance with the SDK license (you never see it or have to agree to it).

[1] https://github.com/CyberShadow/Digger