On Wednesday, 25 October 2017 at 16:05:48 UTC, Mike Parker wrote:
In preparation for an upcoming blog series, and partly as a
reaction to the "Windows is a second-class citizen" criticisms
that have been cropping up lately, I've put together a primer
on getting set up to use C and D together on Windows. It
includes some background on why we need to install the MS
toolchain to produce 64-bit binaries.
The blog:
https://dlang.org/blog/2017/10/25/dmd-windows-and-c/
Reddit:
https://www.reddit.com/r/programming/comments/78olka/dmd_windows_and_c_getting_set_up_to_use_d_and_c/
Great post. Small typo in: "https:/www/visualstudio.com."
Most often it's not that I personally have some library in C that
I need to compile and link to D. I'd rather just use D, all else
equal. The problem is that you have some code base written in C
by someone else and I want to use that. For instance, I was
recently looking at LAPACK
http://icl.cs.utk.edu/lapack-for-windows/lapack/
and you just beat your head against the wall figuring out what
you need to do. Okay, I don't have the intel compiler, and I'm
pretty sure a MinGW version won't work. So there's some VS
solution, but that didn't work for me. So then I thought about
building it, but if you look at the instructions it requires
either the Intel compiler or MinGW. After about a half an hour, I
want to throw up my hands and only use Linux, but I have to use
Windows at work.
