3 days ago

On Tuesday, 29 October 2024 at 18:17:37 UTC, Richard (Rikki) Andrew Cattermole wrote:

>

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

I guess that explains why I've never run into the issue - I've been using LDC but not DMD on Windows.

3 days ago

On Monday, 28 October 2024 at 20:56:03 UTC, DLearner wrote:

>

Just trying ImportC under Windows 10:

#include <stdio.h>

int main()
{
   printf("Hello world.\n");
   return 0;
}

Produces

dmd hello.c
failed launching cl.exe /P /Zc:preprocessor /PD /nologo hello.c /FIC:\D\dmd2\windows\bin64\..\..\src\druntime\import\importc.h /Fihello.i
Error: C preprocess command cl.exe failed for file hello.c, exit status 1

DMD Compiler version?

SDB@79

3 days ago

On Tuesday, 29 October 2024 at 18:57:15 UTC, Salih Dincer wrote:

>

On Monday, 28 October 2024 at 20:56:03 UTC, DLearner wrote:

>

Just trying ImportC under Windows 10:

#include <stdio.h>

int main()
{
   printf("Hello world.\n");
   return 0;
}

Produces

dmd hello.c
failed launching cl.exe /P /Zc:preprocessor /PD /nologo hello.c /FIC:\D\dmd2\windows\bin64\..\..\src\druntime\import\importc.h /Fihello.i
Error: C preprocess command cl.exe failed for file hello.c, exit status 1

DMD Compiler version?

SDB@79

C:\Users\SoftDev>dmd
DMD64 D Compiler v2.106.0-dirty
2 days ago

On Tuesday, 29 October 2024 at 16:14:22 UTC, DLearner wrote:

>

On Tuesday, 29 October 2024 at 15:49:13 UTC, ryuukk_ wrote:

>

https://learn.microsoft.com/en-us/visualstudio/ide/reference/command-prompt-powershell?view=vs-2022

Similar message from Powershell:

Whether it's CMD/Powershell isn't important, but it has to have the Visual Studio environment set up. Do you see this text in the shell when you launch it?

**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.11.5
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************

If not, try to search "Developer Command Prompt for VS" in your start menu.

2 days ago

On Tuesday, 29 October 2024 at 20:26:58 UTC, DLearner wrote:

>

On Tuesday, 29 October 2024 at 18:57:15 UTC, Salih Dincer wrote:

>

On Monday, 28 October 2024 at 20:56:03 UTC, DLearner wrote:

>

Just trying ImportC under Windows 10:

#include <stdio.h>

int main()
{
   printf("Hello world.\n");
   return 0;
}

Produces

dmd hello.c
failed launching cl.exe /P /Zc:preprocessor /PD /nologo hello.c /FIC:\D\dmd2\windows\bin64\..\..\src\druntime\import\importc.h /Fihello.i
Error: C preprocess command cl.exe failed for file hello.c, exit status 1

DMD Compiler version?

SDB@79

C:\Users\SoftDev>dmd
DMD64 D Compiler v2.106.0-dirty

update your compiler, latest version is: 2.109.1

then, and only then you can start wondering what's broken

2 days ago

On Wednesday, 30 October 2024 at 09:21:55 UTC, ryuukk_ wrote:

>

On Tuesday, 29 October 2024 at 20:26:58 UTC, DLearner wrote:

>

On Tuesday, 29 October 2024 at 18:57:15 UTC, Salih Dincer wrote:

>

On Monday, 28 October 2024 at 20:56:03 UTC, DLearner wrote:

>

Just trying ImportC under Windows 10:

#include <stdio.h>

int main()
{
   printf("Hello world.\n");
   return 0;
}

Produces

dmd hello.c
failed launching cl.exe /P /Zc:preprocessor /PD /nologo hello.c /FIC:\D\dmd2\windows\bin64\..\..\src\druntime\import\importc.h /Fihello.i
Error: C preprocess command cl.exe failed for file hello.c, exit status 1

DMD Compiler version?

SDB@79

C:\Users\SoftDev>dmd
DMD64 D Compiler v2.106.0-dirty

update your compiler, latest version is: 2.109.1

then, and only then you can start wondering what's broken

Now upgraded.

  1. I noticed that the installation process also installed both Visual Studio 2019 and Visual Studio 2022. Is one of these preferred?

  2. With 2019:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dmd C:\Users\SoftDev\Documents\BDM\Projects\IT\C\hello.c

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>

ie silence (and no 'hello' files produced either).

  1. With 2022:
C:\Program Files\Microsoft Visual Studio\2022\Community>dmd C:\Users\SoftDev\Documents\BDM\Projects\IT\C\hello.c
C:\Program Files (x86)\Windows Kits\10\include\10.0.22000.0\shared\driverspecs.h(381): warning C4005: '_Kernel_acquires_resource_': macro redefinition
C:\Program Files (x86)\Windows Kits\10\include\10.0.22000.0\shared\no_sal2.h(876): note: see previous definition of '_Kernel_acquires_resource_'
C:\Program Files (x86)\Windows Kits\10\include\10.0.22000.0\shared\driverspecs.h(391): warning C4005: '_Kernel_releases_resource_': macro redefinition

and a large number of similar messages.

2 days ago

On Wednesday, 30 October 2024 at 15:17:56 UTC, DLearner wrote:

>

On Wednesday, 30 October 2024 at 09:21:55 UTC, ryuukk_ wrote:

>

On Tuesday, 29 October 2024 at 20:26:58 UTC, DLearner wrote:

>

On Tuesday, 29 October 2024 at 18:57:15 UTC, Salih Dincer wrote:

>

On Monday, 28 October 2024 at 20:56:03 UTC, DLearner wrote:

>

Just trying ImportC under Windows 10:

#include <stdio.h>

int main()
{
   printf("Hello world.\n");
   return 0;
}

Produces

dmd hello.c
failed launching cl.exe /P /Zc:preprocessor /PD /nologo hello.c /FIC:\D\dmd2\windows\bin64\..\..\src\druntime\import\importc.h /Fihello.i
Error: C preprocess command cl.exe failed for file hello.c, exit status 1

DMD Compiler version?

SDB@79

C:\Users\SoftDev>dmd
DMD64 D Compiler v2.106.0-dirty

update your compiler, latest version is: 2.109.1

then, and only then you can start wondering what's broken

Now upgraded.

  1. I noticed that the installation process also installed both Visual Studio 2019 and Visual Studio 2022. Is one of these preferred?

  2. With 2019:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dmd C:\Users\SoftDev\Documents\BDM\Projects\IT\C\hello.c

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>

ie silence (and no 'hello' files produced either).

  1. With 2022:
C:\Program Files\Microsoft Visual Studio\2022\Community>dmd C:\Users\SoftDev\Documents\BDM\Projects\IT\C\hello.c
C:\Program Files (x86)\Windows Kits\10\include\10.0.22000.0\shared\driverspecs.h(381): warning C4005: '_Kernel_acquires_resource_': macro redefinition
C:\Program Files (x86)\Windows Kits\10\include\10.0.22000.0\shared\no_sal2.h(876): note: see previous definition of '_Kernel_acquires_resource_'
C:\Program Files (x86)\Windows Kits\10\include\10.0.22000.0\shared\driverspecs.h(391): warning C4005: '_Kernel_releases_resource_': macro redefinition

and a large number of similar messages.

why X86 brother, pick the developper prompt for X64

1 day ago

On Tuesday, 29 October 2024 at 20:26:58 UTC, DLearner wrote:

>

On Tuesday, 29 October 2024 at 18:57:15 UTC, Salih Dincer wrote:

>

DMD Compiler version?

SDB@79

C:\Users\SoftDev>dmd
DMD64 D Compiler v2.106.0-dirty

First of all, be sure to get rid of that old version because a lot has changed since that version. There's no harm in having different VSlibs installed. The main problem is that Windows is crap. The address of the solution is: MSYS2. It's simple to install it on your computer and use it safely. Look, there are videos on this subject, here is one of them:

https://youtu.be/OwQobefF-iE?si=QN8sp5SknSROXY83

Yes, now your problems will be solved, insha'Allah

SDB@79

1 2
Next ›   Last »