[Dlang Episode 4] D Language - DMD command line and Visual D for Visual Studio (DMD and LDC2)

►Lesson Description: In this lesson I'll show you how to get started with DMD on the command line. The most common use case however, is probably to use the Visual D plugin, which has a nice installer and integrates with Visual Studio (note: Visual Studio is different than Visual Studio Code). I personally would recommend Visual Studio with Visual D if you are focused solely on windows development, it's a very clean experience!

►Please like and subscribe to help the channel!

[bobahop]

Just became aware of this series, which I'm enjoying. Thank you! I would be interested in a simple Windows GUI walkthrough at some point. A window with some buttons that do some things with the file system or something like that.

[meryplays]

There is DlangIDE and InteliJ plugin (and of course code-d) if you do not want the proprietary solutions.

[rontarrant]

It's amazing how often YouTubers say, "go ahead and..." Once you notice, it's really hard to ignore.

[baba_kebaba]

Visual Studio debugging support is HUGE!!
NOTE: for VS2022 i had to update visual studio after extension installation, and disable hot reload feature to stop getting one annoying error message, otherwise it works fine.

[kenshihkeong]

Tried follow step, in the end I get the error: failed to locate: "bin\link.exe" when trying to build the solution. I was using visual studio 2019 community with visual studio SDK installed.

[dmitryponyatov]

and a more complex thing -- how to setup cross-compiling from Linux to Win (mingw + wine32/64) ?

this variant is more interesting as I must make multiplatform tools (and tiny games), but all my users mostly stay seat under Windows, and some of them use retro computers for fan

I searched a bit and still can't find manual on making cross-compile setup (maybe ldc2 as I also need bare metal D for Cortex-M microcontollers)

[dmitryponyatov]

what about MSYS2 and VSCode that gives a light&fast IDE and full-functional UNIX-like working env with GNU make etc?

[zhirovalexander]

Mike, hi! Thank you so much for what you are doing!
I am very interested in the D language and I am trying to write small utilities in it that I use in my work. The environment where I work all the time is Linux. But I had a need to transfer my small project to Windows. Here I ran into some difficulties.
My utility is written using Postgresql via the Adam D. Ruppe - arsd library (I think you've encountered it).
In Linux, my project is building without problems! I decided to try my luck in Windows.
I didn't install VS. To do this, I installed the DMD compiler (everything is as usual). It is clear that I need to have the Postgres library available. To do this, I downloaded the MSYS2 project. There I installed all the necessary tools. I downloaded the Postgres source code and built the library in the MSYS2 environment. As a result, I have both *.dll libraries and *.a libraries. But when building my D-project, for some reason it is necessary to specify *.lib libraries. That's where I hit a dead end. After suffering with the assembly for a couple of days, I decided to write here.
Could you make a separate video on this topic - linking third-party libraries both in Visual Studio and OUTSIDE, so that you can do it in the CLI or in a dub project.
Could you take a video of how to build the ldc compiler correctly?
In Linux, all these things can be done without problems, but in Windows everything is too tied to Visual Studio. But when there is a dub project, it is convenient to use it in the CLI, because everything is already configured there.

[dmitryponyatov]

I see C compiler included in extra options -- does it runs under modern x64 systems and able to build some extra libs without installing ugly huge VS?

[ErwinLee-]

Thanks for this video! How can I adjust the stack size of my Visual D project?

[GaryChike]

Good stuff Mike! Don't you think it's interesting that writeln, write and readln are same key words in Pascal? I threw in a readln to prevent my console from closing prematurely, but I like how you used the debugger, you know, the more pro way. 🙃 Really looking forward to the rest of the series .. 🚀