DMD VS2017 Support

[Mike B Johnson via Digitalmars-d]

On Sunday, 30 April 2017 at 16:52:52 UTC, Igor wrote:
> On Sunday, 30 April 2017 at 16:31:13 UTC, John Chapman wrote:
>>
>> Here are mine, if it helps:
>>
>
> I tried but still the same problem. I also tried reinstalling 
> VisualD after changing sc.ini in DMD but that didn't help 
> either.

You are going to have to figure it out. Visual Studio does some 
stupid path stuff that doesn't make any sense really(seems like 
it could do a much better job).

What you could do is:

1. Create a "library" folder.

e.g.,

C:\DMD\Libs\Coff\x86
C:\DMD\Libs\Coff\x64
C:\DMD\Libs\OMF\x86
C:\DMD\Libs\OMF\x64 <- not used as there is no x64 omf


2. Point sc.ini to these.

3. Copy the lib files from the VS or win SDK to these folders.

4. Do the magic that it takes to get it to work(which is finding 
the right libs that are needed, using procmon to see where dmd is 
looking, etc). This involves building and checking the errors 
then trying to resolve them.


Once done, you have a solid set of libs that once works, won't 
change.  When you update VS you can update the libs here and 
there but it is not needed very often.

Sometimes you'll have to pull in different libs from different 
versions and such. DMD comes with the some libs that you can use 
for x86.

Once you get it working you shouldn't have to mess with it much. 
If you accidentally overwrite sc.ini(which is ridiculous that it 
does this on install), you know EXACTLY where the libs are and 
don't have to go hunt for them again. If you want, you can use 
junctions instead of copying but these might need to be updated 
again when VS changes.