Thread overview | ||||||||
---|---|---|---|---|---|---|---|---|
|
November 21, 2018 The D program to launch doesn't exist in Visual Studio 2017 | ||||
---|---|---|---|---|
| ||||
I'm just trying to set up a community version of the Visual Studio 2017 on my x64 PC (Windows 10) to program in D based on dmd compiler. In particular, I can build my snippet, but running the code returns the following error: The program to lunch does not exist. Additionally, the output window of my Visual Studio returns this: Building Win32\Debug\Test.exe... OPTLINK (R) for Win32 Release 8.00.17 Copyright (C) Digital Mars 1989-2013 All rights reserved. http://www.digitalmars.com/ctg/optlink.html OPTLINK : Error 8: Illegal Filename ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== My file name is just "Test.d", so I have know idea what it means by illegal file name. Does anybody know anything about this issue? |
November 21, 2018 Re: The D program to launch doesn't exist in Visual Studio 2017 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Roboticist | On Wednesday, 21 November 2018 at 18:34:38 UTC, Roboticist wrote:
> I'm just trying to set up a community version of the Visual Studio 2017 on my x64 PC (Windows 10) to program in D based on dmd compiler. In particular, I can build my snippet, but running the code returns the following error:
>
> The program to lunch does not exist.
>
> Additionally, the output window of my Visual Studio returns this:
>
> Building Win32\Debug\Test.exe...
> OPTLINK (R) for Win32 Release 8.00.17
> Copyright (C) Digital Mars 1989-2013 All rights reserved.
> http://www.digitalmars.com/ctg/optlink.html
> OPTLINK : Error 8: Illegal Filename
> ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
>
> My file name is just "Test.d", so I have know idea what it means by illegal file name.
>
> Does anybody know anything about this issue?
What is the full output path? I mean the complete path as a C:\\whatever\\myproject\\...
You have mentioned that you have Win64(x64) windows 10 and use visual studio 2017. Why would you use optlink anyway? How did you install D?
|
November 22, 2018 Re: The D program to launch doesn't exist in Visual Studio 2017 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Roboticist |
On 21/11/2018 19:34, Roboticist wrote:
> I'm just trying to set up a community version of the Visual Studio 2017 on my x64 PC (Windows 10) to program in D based on dmd compiler. In particular, I can build my snippet, but running the code returns the following error:
>
> The program to lunch does not exist.
>
> Additionally, the output window of my Visual Studio returns this:
>
> Building Win32\Debug\Test.exe...
> OPTLINK (R) for Win32 Release 8.00.17
> Copyright (C) Digital Mars 1989-2013 All rights reserved.
> http://www.digitalmars.com/ctg/optlink.html
> OPTLINK : Error 8: Illegal Filename
> ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
>
> My file name is just "Test.d", so I have know idea what it means by illegal file name.
>
> Does anybody know anything about this issue?
>
As Daniel already mentioned, it's probably something in a full path that optlink does not like. You can see the executed commands in Win32\Debug\Test*.cmd. The exact name depends on the used compilation model.
You can switch to a more standard object file format and usage of the Microsoft linker by enabling "MS-COFF" in the Project->Compiler->Output options. Building for x64 always uses COFF and the MS linker.
|
November 22, 2018 Re: The D program to launch doesn't exist in Visual Studio 2017 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Daniel Kozák | On Wednesday, 21 November 2018 at 20:42:06 UTC, Daniel Kozák wrote: > On Wednesday, 21 November 2018 at 18:34:38 UTC, Roboticist wrote: >> I'm just trying to set up a community version of the Visual Studio 2017 on my x64 PC (Windows 10) to program in D based on dmd compiler. In particular, I can build my snippet, but running the code returns the following error: >> >> The program to lunch does not exist. >> >> Additionally, the output window of my Visual Studio returns this: >> >> Building Win32\Debug\Test.exe... >> OPTLINK (R) for Win32 Release 8.00.17 >> Copyright (C) Digital Mars 1989-2013 All rights reserved. >> http://www.digitalmars.com/ctg/optlink.html >> OPTLINK : Error 8: Illegal Filename >> ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== >> >> My file name is just "Test.d", so I have know idea what it means by illegal file name. >> >> Does anybody know anything about this issue? > > What is the full output path? I mean the complete path as a C:\\whatever\\myproject\\... > > You have mentioned that you have Win64(x64) windows 10 and use visual studio 2017. Why would you use optlink anyway? How did you install D? Here is the full path: C:\users\myUser\source\repos\Test\Test\Win32\Debug\ I just installed D using dmd.exe before installing VS 2017 and D studio plugin. Additionally, I did no specific setting to use optlink. It's just what the d compiler is using by default. |
November 22, 2018 Re: The D program to launch doesn't exist in Visual Studio 2017 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Rainer Schuetze | On Thursday, 22 November 2018 at 06:58:11 UTC, Rainer Schuetze wrote:
>
>
> On 21/11/2018 19:34, Roboticist wrote:
>> I'm just trying to set up a community version of the Visual Studio 2017 on my x64 PC (Windows 10) to program in D based on dmd compiler. In particular, I can build my snippet, but running the code returns the following error:
>>
>> The program to lunch does not exist.
>>
>> Additionally, the output window of my Visual Studio returns this:
>>
>> Building Win32\Debug\Test.exe...
>> OPTLINK (R) for Win32 Release 8.00.17
>> Copyright (C) Digital Mars 1989-2013 All rights reserved.
>> http://www.digitalmars.com/ctg/optlink.html
>> OPTLINK : Error 8: Illegal Filename
>> ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
>>
>> My file name is just "Test.d", so I have know idea what it means by illegal file name.
>>
>> Does anybody know anything about this issue?
>>
>
> As Daniel already mentioned, it's probably something in a full path that optlink does not like. You can see the executed commands in Win32\Debug\Test*.cmd. The exact name depends on the used compilation model.
>
> You can switch to a more standard object file format and usage of the Microsoft linker by enabling "MS-COFF" in the Project->Compiler->Output options. Building for x64 always uses COFF and the MS linker.
Sorry if it's a stupid question, but there's no Compiler->Output option in the Project menu in the VS2017. Can you please indicate where I should apply the change?
|
November 22, 2018 Re: The D program to launch doesn't exist in Visual Studio 2017 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Roboticist |
On 22/11/2018 09:20, Roboticist wrote:
> On Thursday, 22 November 2018 at 06:58:11 UTC, Rainer Schuetze wrote:
>>
>>
>> On 21/11/2018 19:34, Roboticist wrote:
>>> I'm just trying to set up a community version of the Visual Studio 2017 on my x64 PC (Windows 10) to program in D based on dmd compiler. In particular, I can build my snippet, but running the code returns the following error:
>>>
>>> The program to lunch does not exist.
>>>
>>> Additionally, the output window of my Visual Studio returns this:
>>>
>>> Building Win32\Debug\Test.exe...
>>> OPTLINK (R) for Win32 Release 8.00.17
>>> Copyright (C) Digital Mars 1989-2013 All rights reserved.
>>> http://www.digitalmars.com/ctg/optlink.html
>>> OPTLINK : Error 8: Illegal Filename
>>> ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped
>>> ==========
>>>
>>> My file name is just "Test.d", so I have know idea what it means by illegal file name.
>>>
>>> Does anybody know anything about this issue?
>>>
>>
>> As Daniel already mentioned, it's probably something in a full path that optlink does not like. You can see the executed commands in Win32\Debug\Test*.cmd. The exact name depends on the used compilation model.
>>
>> You can switch to a more standard object file format and usage of the Microsoft linker by enabling "MS-COFF" in the Project->Compiler->Output options. Building for x64 always uses COFF and the MS linker.
>
> Sorry if it's a stupid question, but there's no Compiler->Output option in the Project menu in the VS2017. Can you please indicate where I should apply the change?
I'm referring to the respective configuration page in the "project properties". This assumes you have created a "Visual D project", not a "Visual C++ project" with D support.
|
Copyright © 1999-2021 by the D Language Foundation