www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - new release doesn't work as advertised

reply "learn" <learn learn.com> writes:
trying to compile the minimal console application generated by 
visuald:


Building Debug\ConsoleApp1.exe...
LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
Building Debug\ConsoleApp1.exe failed!

win10 - vs2015
Aug 13 2015
next sibling parent reply "Gary Willoughby" <dev nomad.so> writes:
On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated by 
 visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
This error has nothing to do with the new D release. For help with visuald please try the learn section here: http://forum.dlang.org/group/learn
Aug 13 2015
next sibling parent reply Rikki Cattermole <alphaglosined gmail.com> writes:
On 13/08/2015 10:44 p.m., Gary Willoughby wrote:
 On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated by visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
This error has nothing to do with the new D release. For help with visuald please try the learn section here: http://forum.dlang.org/group/learn
It was posted there. It's a known issue. Currently no fix for VS2015. However it is being worked upon. Use 2013 instead.
Aug 13 2015
parent reply "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 11:04:21 UTC, Rikki Cattermole 
wrote:
 On 13/08/2015 10:44 p.m., Gary Willoughby wrote:
 On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated 
 by visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
This error has nothing to do with the new D release. For help with visuald please try the learn section here: http://forum.dlang.org/group/learn
It was posted there. It's a known issue. Currently no fix for VS2015. However it is being worked upon. Use 2013 instead.
thank you for your answer and suggestion, but it is not possible for me to uninstall vs 2015 because of D alone.
Aug 13 2015
parent reply "David Nadlinger" <code klickverbot.at> writes:
On Thursday, 13 August 2015 at 16:30:59 UTC, learn wrote:
 On Thursday, 13 August 2015 at 11:04:21 UTC, Rikki Cattermole 
 wrote:
 It was posted there.
 It's a known issue. Currently no fix for VS2015.
 However it is being worked upon.

 Use 2013 instead.
thank you for your answer and suggestion, but it is not possible for me to uninstall vs 2015 because of D alone.
You can install VS 2013 alongside VS 2015 just fine. — David
Aug 13 2015
next sibling parent reply "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 16:44:09 UTC, David Nadlinger 
wrote:
 On Thursday, 13 August 2015 at 16:30:59 UTC, learn wrote:
 On Thursday, 13 August 2015 at 11:04:21 UTC, Rikki Cattermole 
 wrote:
 It was posted there.
 It's a known issue. Currently no fix for VS2015.
 However it is being worked upon.

 Use 2013 instead.
thank you for your answer and suggestion, but it is not possible for me to uninstall vs 2015 because of D alone.
You can install VS 2013 alongside VS 2015 just fine. — David
thank you for the info, but i don't want/need two VS's; this might just wreck the registry and it is a pain to uninstall. i rather be interested in the working working thingy - and so i wait a week or two to try or have lost out on d. thank you again
Aug 13 2015
parent reply "QAston" <qastonx gmail.com> writes:
On Thursday, 13 August 2015 at 17:44:11 UTC, learn wrote:
 On Thursday, 13 August 2015 at 16:44:09 UTC, David Nadlinger 
 wrote:
 On Thursday, 13 August 2015 at 16:30:59 UTC, learn wrote:
 On Thursday, 13 August 2015 at 11:04:21 UTC, Rikki Cattermole 
 wrote:
 It was posted there.
 It's a known issue. Currently no fix for VS2015.
 However it is being worked upon.

 Use 2013 instead.
thank you for your answer and suggestion, but it is not possible for me to uninstall vs 2015 because of D alone.
You can install VS 2013 alongside VS 2015 just fine. — David
thank you for the info, but i don't want/need two VS's; this might just wreck the registry and it is a pain to uninstall. i rather be interested in the working working thingy - and so i wait a week or two to try or have lost out on d. thank you again
Just the redistributable package should be enough. It's a normal practice to install it because vc libs are incompatible. I have all of the redistributables installed atm, no problems.
Aug 13 2015
parent "QAston" <qastonx gmail.com> writes:
On Friday, 14 August 2015 at 06:28:54 UTC, QAston wrote:
 Just the redistributable package should be enough. It's a 
 normal practice to install it because vc libs are incompatible. 
 I have all of the redistributables installed atm, no problems.
http://www.microsoft.com/en-us/download/details.aspx?id=40784 I don't know if d needs anything more than the redistributable package to run :(
Aug 13 2015
prev sibling parent reply "tcak" <1ltkrs+3wyh1ow7kzn1k sharklasers.com> writes:
On Thursday, 13 August 2015 at 16:44:09 UTC, David Nadlinger 
wrote:
 On Thursday, 13 August 2015 at 16:30:59 UTC, learn wrote:
 On Thursday, 13 August 2015 at 11:04:21 UTC, Rikki Cattermole 
 wrote:
 It was posted there.
 It's a known issue. Currently no fix for VS2015.
 However it is being worked upon.

 Use 2013 instead.
thank you for your answer and suggestion, but it is not possible for me to uninstall vs 2015 because of D alone.
You can install VS 2013 alongside VS 2015 just fine. — David
I think, first of all, the reason why it doesn't compile with VS 2015 should be explained. By leaving the reason, and saying to just install VS 2013 is too ignorant for this community. What is the problem about VS 2015? and how can it be solved?
Aug 13 2015
parent reply "kinke" <noone nowhere.com> writes:
On Thursday, 13 August 2015 at 17:56:06 UTC, tcak wrote:
 On Thursday, 13 August 2015 at 16:44:09 UTC, David Nadlinger 
 wrote:
 On Thursday, 13 August 2015 at 16:30:59 UTC, learn wrote:
 On Thursday, 13 August 2015 at 11:04:21 UTC, Rikki Cattermole 
 wrote:
 It was posted there.
 It's a known issue. Currently no fix for VS2015.
 However it is being worked upon.

 Use 2013 instead.
thank you for your answer and suggestion, but it is not possible for me to uninstall vs 2015 because of D alone.
You can install VS 2013 alongside VS 2015 just fine. — David
I think, first of all, the reason why it doesn't compile with VS 2015 should be explained. By leaving the reason, and saying to just install VS 2013 is too ignorant for this community. What is the problem about VS 2015? and how can it be solved?
First of all, the RTM has been released about 3 weeks ago, so how come you expect an entirely community-driven compiler to support it within such a short time frame? Especially as Win64 is not considered a primary target. Secondly, there's been breaking changes in the C runtime, as MS finally almost caught up with all other C runtimes in terms of C99 standard conformance. So D's druntime layer on top of the C runtime is being adapted. LDC is already compatible with VS 2015 (http://forum.dlang.org/thread/sgdyguqpuydnkwtmnyar forum.dlang.org) and the next release will greatly improve its Win64 support. And then there's VisualD apparently missing to detect VS 2015. I know that CTPs have been out for quite some time, I've used one for quite some time myself. But the Windows faction in this community isn't strong, the DMD CI slaves use VS 2010, LDC only has CI tests on Linux etc. learn:
 if you guys want to be with VS by MS you should have the 
 complete headers and working releases or ABANON the voting at 
 MS.
Wow, what arrogance. Nothing prevents MS from taking their first steps towards D, why must we do it all ourselves in our spare time for a proprietary and commercial OS?
Aug 13 2015
parent reply "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 18:32:31 UTC, kinke wrote:
 First of all, the RTM has been released about 3 weeks ago, so 
 how come you expect an entirely community-driven compiler to 
 support it within such a short time frame? Especially as Win64 
 is not considered a primary target.
 Secondly, there's been breaking changes in the C runtime, as MS 
 finally almost caught up with all other C runtimes in terms of 
 C99 standard conformance. So D's druntime layer on top of the C 
 runtime is being adapted. LDC is already compatible with VS 
 2015 
 (http://forum.dlang.org/thread/sgdyguqpuydnkwtmnyar forum.dlang.org) and the
next release will greatly improve its Win64 support.
 And then there's VisualD apparently missing to detect VS 2015.

 I know that CTPs have been out for quite some time, I've used 
 one for quite some time myself. But the Windows faction in this 
 community isn't strong, the DMD CI slaves use VS 2010, LDC only 
 has CI tests on Linux etc.

  learn:
 if you guys want to be with VS by MS you should have the 
 complete headers and working releases or ABANON the voting at 
 MS.
Wow, what arrogance. Nothing prevents MS from taking their first steps towards D, why must we do it all ourselves in our spare time for a proprietary and commercial OS?
don't cry around. i don't care how it's done - i want to use it. maybe you should consider to advertise it differently - by truthfully explaining what works and what not. maybe you should think a little about that your prios are not necessarily the prios of other possible users.
Aug 13 2015
parent reply "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:
On Thursday, 13 August 2015 at 19:14:55 UTC, learn wrote:
 maybe you should consider to advertise it differently - by 
 truthfully explaining what works and what not.
Sounds like a good idea.
Aug 13 2015
parent reply "ZombineDev" <valid_email he.re> writes:
On Thursday, 13 August 2015 at 20:12:57 UTC, Ola Fosheim Grøstad 
wrote:
 On Thursday, 13 August 2015 at 19:14:55 UTC, learn wrote:
 maybe you should consider to advertise it differently - by 
 truthfully explaining what works and what not.
Sounds like a good idea.
MSVCRT 14.0 support isn't advertised anywhere.
Aug 13 2015
parent "Ola Fosheim Grostad" <ola.fosheim.grostad+dlang gmail.com> writes:
On Friday, 14 August 2015 at 03:27:42 UTC, ZombineDev wrote:
 On Thursday, 13 August 2015 at 20:12:57 UTC, Ola Fosheim 
 Grøstad wrote:
 On Thursday, 13 August 2015 at 19:14:55 UTC, learn wrote:
 maybe you should consider to advertise it differently - by 
 truthfully explaining what works and what not.
Sounds like a good idea.
MSVCRT 14.0 support isn't advertised anywhere.
The download page does not list requirements. If it does not one usually will assume that it will work with no hassle. I think it should list requirements for both OSX and Windows.
Aug 13 2015
prev sibling parent "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 10:44:06 UTC, Gary Willoughby 
wrote:
 On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated by 
 visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
This error has nothing to do with the new D release. For help with visuald please try the learn section here: http://forum.dlang.org/group/learn
wow you are a real polite cookie. if you guys want to be with VS by MS you should have the complete headers and working releases or ABANON the voting at MS. the linker bug alone it is disgusting for a new release and it renders the compiler unuasable - what an advertisement for the compiler. you don't even have a fast fix, so that the compiler becomes and that should make any prospective new and old user think twice about using D.
Aug 13 2015
prev sibling parent reply "Tofu Ninja" <emmons0 purdue.edu> writes:
On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated by 
 visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
Sigh... another example of D's tooling holding it back/scaring away newcomers. Though the replies in this thread are probably doing a better job at scaring away newcomers.
Aug 13 2015
next sibling parent reply "bachmeier" <no spam.com> writes:
On Thursday, 13 August 2015 at 19:32:26 UTC, Tofu Ninja wrote:
 On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated by 
 visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
Sigh... another example of D's tooling holding it back/scaring away newcomers. Though the replies in this thread are probably doing a better job at scaring away newcomers.
D is not for everyone. This user needs to be using a commercial compiler with commercial tools, and a special support contract. You can complain about how things should be, but this is reality. Unless you are willing to dump a few million dollars into the development of tools... The replies here are quite tame. Think about what he is demanding. VS 2013 works, and there is no problem installing two versions of VS, but he doesn't want to install it. He wants to use D in VS 2015 only.
Aug 13 2015
next sibling parent reply "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 20:13:59 UTC, bachmeier wrote:
 D is not for everyone. This user needs to be using a commercial 
 compiler with commercial tools, and a special support contract. 
 You can complain about how things should be, but this is 
 reality. Unless you are willing to dump a few million dollars 
 into the development of tools...

 The replies here are quite tame. Think about what he is 
 demanding. VS 2013 works, and there is no problem installing 
 two versions of VS, but he doesn't want to install it. He wants 
 to use D in VS 2015 only.
are you trying to tell me that this compiler isn't good enough for anyone who doesn't want to change his ecosystem that works for everything else i develop? i came here because i read the petitions to have D in VS - and it said it works with VS2015. the mixing of vs's will cause a registry problem and produce tons of work if i want to delete it. some thing might easier on linux, but i use windows. so, by all means, advertise the correct thing and if you want to dink around, than tell people it is only for hobbyist, works only on linux and can not be used for commercial programs on windows. i can live with that, because i will not try it. BUT it will still make think would be nice to use on windows. btw - i still want to use D in VS 2015 only.
Aug 13 2015
next sibling parent reply "bachmeier" <no spam.com> writes:
On Thursday, 13 August 2015 at 20:30:35 UTC, learn wrote:
 are you trying to tell me that this compiler isn't good enough 
 for anyone who doesn't want to change his ecosystem that works 
 for everything else i develop?
 i came here because i read the petitions to have D in VS - and 
 it said it works with VS2015.

 the mixing of vs's will cause a registry problem and produce 
 tons of work if i want to delete it. some thing might easier on 
 linux, but i use windows.

 so, by all means, advertise the correct thing and if you want 
 to dink around, than tell people it is only for hobbyist, works 
 only on linux and can not be used for commercial programs on 
 windows.

 i can live with that, because i will not try it. BUT it will 
 still make think
 would be nice to use on windows.

 btw - i still want to use D in VS 2015 only.
My comment was about the limited resources of this community. If there are false statements about VS 2015 support, then they should be corrected. And if you feel that VS 2015 support is a must, then it is entirely reasonable to not use D. I was responding to what I felt was a harsh response by Tofu Ninja. IMO it is not realistic to think that any developer can sit down and use his preferred setup without any rough edges. It comes with writing D code. Others have told you that the problem is being fixed, told you how you can still use VS, and I don't see what more they should have done.
Aug 13 2015
parent "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 21:04:53 UTC, bachmeier wrote:
 My comment was about the limited resources of this community. 
 If there are false statements about VS 2015 support, then they 
 should be corrected. And if you feel that VS 2015 support is a 
 must, then it is entirely reasonable to not use D.

 I was responding to what I felt was a harsh response by Tofu 
 Ninja. IMO it is not realistic to think that any developer can 
 sit down and use his preferred setup without any rough edges. 
 It comes with writing D code. Others have told you that the 
 problem is being fixed, told you how you can still use VS, and 
 I don't see what more they should have done.
i am sorry if have been to harsh and - i have no problems with "rough edges" - but that also means, that the overall thingy IS working. BUT IT DOESN'T. running on windows, i need the headers and is not only a VS issue - and then - i will have also the painful task to connect to my old code or be willing to port old code and that with seemingly (unknown to me yet) bad (multi D) dll support on windows. i know about rough edges - i used assembler half my life, i wrote the programs for my dissertation with walter's zortech c++ compiler (it had just came out - rough edges at the time) and having said that, i kind of feel old (walter is surely alot younger - but then the hair??). never the less, if you promise something - do at least the QS necessary to keep the overall promise, with, may be the rough edges included. But that does not include that it doesn't work, - that it doesn't have the needed headers and donn’t suggest that others (developers on D) care more for just one OS which isn’t necessarily windows. BOLD don't knowingly steel the time of people (bad QS is knowing/intent), just tell them what is and what is not - rough edges included. they might still go for D - just for that reason and that is an opportunity. BOLD OFF one last remark: a lot of times the old(er) people are the ones who decide about using the rough edges or not. they take a risks that might be the situation D needs. but D is missing QS? lost of it? give your thoughts.
Aug 13 2015
prev sibling next sibling parent reply "rumbu" <rumbu rumbu.ro> writes:
On Thursday, 13 August 2015 at 20:30:35 UTC, learn wrote:
 btw - i still want to use D in VS 2015 only.
You can use D in VS 2015 for building standard 32 bit executables. Trying to build mscoff executables (32 or 64 bit) will lead to various errors like the one you posted. You can easily fix the paths in sc.ini, but this will lead to other linking errors, because MS has changed the C std libs in VS 2015. Uncheck "Use MS-COFF object file format..." in Project Configuration/Compiler/Output and use x86 as platform target in Visual Studio and it should work fine. Anyway, adapting D toolchain to VS2015/Win10 is work in progress, probably the next version will fully support VS2015: https://github.com/D-Programming-Language/druntime/pull/1341 Note to the "Warmest Welcome Group Ever": I'm also using only VS2015 on my tablet, I don't have enough space to keep 2 VS versions. And an extract from the installation page: "... The generated object code is in MS-COFF and is meant to be used with the Microsoft Visual Studio 10 or *later* compiler"." Not later than Visual Studio 13.
Aug 13 2015
parent reply "learn" <learn learn.com> writes:
On Thursday, 13 August 2015 at 22:15:47 UTC, rumbu wrote:
 On Thursday, 13 August 2015 at 20:30:35 UTC, learn wrote:
 btw - i still want to use D in VS 2015 only.
You can use D in VS 2015 for building standard 32 bit executables. Trying to build mscoff executables (32 or 64 bit) will lead to various errors like the one you posted. You can easily fix the paths in sc.ini, but this will lead to other linking errors, because MS has changed the C std libs in VS 2015. Uncheck "Use MS-COFF object file format..." in Project Configuration/Compiler/Output and use x86 as platform target in Visual Studio and it should work fine. Anyway, adapting D toolchain to VS2015/Win10 is work in progress, probably the next version will fully support VS2015: https://github.com/D-Programming-Language/druntime/pull/1341 Note to the "Warmest Welcome Group Ever": I'm also using only VS2015 on my tablet, I don't have enough space to keep 2 VS versions. And an extract from the installation page: "... The generated object code is in MS-COFF and is meant to be used with the Microsoft Visual Studio 10 or *later* compiler"." Not later than Visual Studio 13.
yup - but on other pages visuald is advertised. when you order aspirin you don't want get GABA. i think it is a QS thing - when you release you look at all the advertisements. btw, i need 64bit and your lovely beer (not meant jokingly)
Aug 13 2015
parent "ZombineDev" <valid_email he.re> writes:
On Thursday, 13 August 2015 at 22:32:05 UTC, learn wrote:
 yup - but on other pages visuald is advertised. when you order 
 aspirin you don't want get GABA. i  think it is a QS thing - 
 when you release you look at all the advertisements.
I'm sorry to hear that you had bad out-of-the-box experience on Win10 + VS2015. I want to clear some things up: 1) There's nowhere written on the homepage that DMD (D's reference compiler) supports VS 2015 so I don't know where got that impression from. 2) The problem is not with VisualD itself. VisualD is a VS extension which uses whatever D compiler you have installed to build your project. All the nice features that VisualD provides (http://rainers.github.io/visuald/visuald/StartPage.html) are independent of the compiler. Actually, at the moment *only* VisualD advertises that it has VS2015 support and in fact it works as advertised - VisualD correctly detects that you have VS2015 and registers with it. I've been using Windows 10 x64 + VS2015 + VisualD v0.3.42 for a couple of days now I didn't have any issues with VisualD itself - developing, building and debugging works as advertised (for 32-bit apps that is, though VisualD has no problem telling the compiler to produce 64-bit code, so when you install a version of DMD that *has* MSVCRT 14.0 support it should all work out). 3) The real problem (as others have pointed out) is that MS made breaking changes in their lib C runtime (List of changes: https://msdn.microsoft.com/en-us/library/bb531344.aspx (see CRT, especially the part about <stdio.h> and <conio.h>) Blog post: http://blogs.msdn.com/b/vcblog/archive/2014/06/10/the-great-crt-refactoring.aspx) and we need to add support for this in DMD and the other compilers. MSVC++ was not standards compliant for a long time and now the workarounds for it need to be reworked in druntime. It's not easy as it sounds because we need to support both MSVC++ v14.0 (that comes with VS 2015) and MSVC++ v12.0 and older (otherwise it's a breaking change for out users). According to Steam, Windows 10 x64 users are only 2.2% and those who use VS2015 is an even smaller number, so I don't know why you are expecting first day support for a traditionally non-standards-compliant C runtime with insignificant userbase. Note that for 32-bit DMD ships with a custom C runtime lib and linker that work perfectly fine on Windows 10 and VS 2015. AFAIU, for DMD there are three things that need to be done: a) The installer needs to be able detect VS 2015 and Windows SDK 10 so it can add the correct paths to DMD's configuration file (sc.ini). b) MSVC C stdio runtime support wrapper needs to be put in a separate library from druntime and split in two parts: MSVCRT12 and MSVCRT14. c) DMD needs to able to detect the correct MSVCRT version at link-time and choose the appropriate wrapper to link druntime to. a) could have been easily released with the latest DMD release, but I guess it was decided that it is better to wait till the full MSVCRT v14 support is finished (otherwise you would just get different kind of linker errors). So sum up, support for MSVCRT 14 is in progress and should be complete for DMD v2.068.1 (expected ~1 month from now) or DMD v2.069.0 (expected ~2 months from now). Here you can follow the status of this issue: https://issues.dlang.org/show_bug.cgi?id=14849
Aug 13 2015
prev sibling parent "Kagamin" <spam here.lot> writes:
On Thursday, 13 August 2015 at 20:30:35 UTC, learn wrote:
 the mixing of vs's will cause a registry problem and produce 
 tons of work if i want to delete it
Haha, you mean VS doesn't work for you? What do you want from a couple of enthusiasts from internet when even big scary microsoft can't get it right on their own OS with their billions bucks? I have five VS versions installed on my system and everything works fine. It's even supposed to work this way because no codebase easily jumps from one ecosystem to another. In my experience MS software is quite high quality in this respect, it's usually 3rd party software which does all sorts of horrible things to the system because the developers don't want to think about anything and write whatever compiles.
Aug 14 2015
prev sibling parent "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:
On Thursday, 13 August 2015 at 20:13:59 UTC, bachmeier wrote:
 D is not for everyone. This user needs to be using a commercial 
 compiler with commercial tools, and a special support contract. 
 You can complain about how things should be, but this is 
 reality. Unless you are willing to dump a few million dollars 
 into the development of tools...
It is common for development tools to list what is fully supported, and what is not. This should be known to the user before downloading. Windows is listed on top on the download page with no comments. Commercial has nothing to do with it. Professional tools don't hide maturity level and discourage production use until an acceptable maturity level has been reached. What you basically are saying is that D is not a professional tool and thus professional standards don't apply here…
Aug 13 2015
prev sibling parent "ZombineDev" <valid_email he.re> writes:
On Thursday, 13 August 2015 at 19:32:26 UTC, Tofu Ninja wrote:
 On Thursday, 13 August 2015 at 10:40:08 UTC, learn wrote:
 trying to compile the minimal console application generated by 
 visuald:


 Building Debug\ConsoleApp1.exe...
 LINK : fatal error LNK1104: cannot open file 'libucrtd.lib'
 Building Debug\ConsoleApp1.exe failed!

 win10 - vs2015
Sigh... another example of D's tooling holding it back/scaring away newcomers. Though the replies in this thread are probably doing a better job at scaring away newcomers.
The DMD v2.068.0 installer clearly says that VS 2015 is not supported: [1]: http://pasteboard.co/2HEiD5hs.png [2]: http://pasteboard.co/2HEn0ywS.png
Aug 13 2015