www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Development of dmd on windows is painfull.

reply 12345swordy <alexanderheistermann gmail.com> writes:
I am using the visual studio project from rainer for dmd 
development and I am struggling to get run.d to run one test 
instead of all of them, without modifying the run.d file. I have 
talk to other on discord and they seemed to agree with me.

-Alex
Jan 04 2021
parent reply Basile B. <b2.temp gmx.com> writes:
On Tuesday, 5 January 2021 at 03:39:01 UTC, 12345swordy wrote:

 I am using the visual studio project from rainer for dmd 
 development and I am struggling to get run.d to run one test 
 instead of all of them, without modifying the run.d file. I 
 have talk to other on discord and they seemed to agree with me.

 -Alex


How about using an external tool [1] and check the "Prompt for 
arguments" option ?
The argument will be the test to run.

[1] : 
https://docs.microsoft.com/en-us/visualstudio/ide/managing-external-tools?view=vs-2019
Jan 04 2021
parent reply 12345swordy <alexanderheistermann gmail.com> writes:
On Tuesday, 5 January 2021 at 04:20:57 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 03:39:01 UTC, 12345swordy wrote:

 I am using the visual studio project from rainer for dmd 
 development and I am struggling to get run.d to run one test 
 instead of all of them, without modifying the run.d file. I 
 have talk to other on discord and they seemed to agree with me.

 -Alex


 How about using an external tool [1] and check the "Prompt for 
 arguments" option ?
 The argument will be the test to run.

 [1] : 
 https://docs.microsoft.com/en-us/visualstudio/ide/managing-external-tools?view=vs-2019


Have you try it and have it running on your machine?

-Alex
Jan 05 2021
parent reply Basile B. <b2.temp gmx.com> writes:
On Tuesday, 5 January 2021 at 14:09:02 UTC, 12345swordy wrote:

 On Tuesday, 5 January 2021 at 04:20:57 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 03:39:01 UTC, 12345swordy wrote:

 I am using the visual studio project from rainer for dmd 
 development and I am struggling to get run.d to run one test 
 instead of all of them, without modifying the run.d file. I 
 have talk to other on discord and they seemed to agree with 
 me.

 -Alex


 How about using an external tool [1] and check the "Prompt for 
 arguments" option ?
 The argument will be the test to run.

 [1] : 
 https://docs.microsoft.com/en-us/visualstudio/ide/managing-external-tools?view=vs-2019


 Have you try it and have it running on your machine?

 -Alex


I'm on linux but this work similarly.
First goes into the test folder and build the runner

    $ rdmd --build-only run.d

Then setup the tool

Command: run.exe
Arguments: <leave empty>
Initial Directory: <leave empty or select the folder where is 
located run.exe>
and check "Prompt for Arguments"

then when you execute the tool you type the test name, incl. the 
folder, for example "compilable/bug33.d"
Jan 05 2021
parent reply 12345swordy <alexanderheistermann gmail.com> writes:
On Tuesday, 5 January 2021 at 16:13:30 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 14:09:02 UTC, 12345swordy wrote:

 On Tuesday, 5 January 2021 at 04:20:57 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 03:39:01 UTC, 12345swordy wrote:

 I am using the visual studio project from rainer for dmd 
 development and I am struggling to get run.d to run one test 
 instead of all of them, without modifying the run.d file. I 
 have talk to other on discord and they seemed to agree with 
 me.

 -Alex


 How about using an external tool [1] and check the "Prompt 
 for arguments" option ?
 The argument will be the test to run.

 [1] : 
 https://docs.microsoft.com/en-us/visualstudio/ide/managing-external-tools?view=vs-2019


 Have you try it and have it running on your machine?

 -Alex


 I'm on linux but this work similarly.
 First goes into the test folder and build the runner

    $ rdmd --build-only run.d

 Then setup the tool

 Command: run.exe
 Arguments: <leave empty>
 Initial Directory: <leave empty or select the folder where is 
 located run.exe>
 and check "Prompt for Arguments"

 then when you execute the tool you type the test name, incl. 
 the folder, for example "compilable/bug33.d"


I shouldn't have to run this via console in order to test this. 
This is just plan ridiculous. There are developmental virtual 
machines for windows that is free for software development on 
windows. We should not be stuck forever in the console era.
Jan 05 2021
parent reply 12345swordy <alexanderheistermann gmail.com> writes:
On Wednesday, 6 January 2021 at 00:40:24 UTC, 12345swordy wrote:

 On Tuesday, 5 January 2021 at 16:13:30 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 14:09:02 UTC, 12345swordy wrote:

 On Tuesday, 5 January 2021 at 04:20:57 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 03:39:01 UTC, 12345swordy 
 wrote:

 I am using the visual studio project from rainer for dmd 
 development and I am struggling to get run.d to run one 
 test instead of all of them, without modifying the run.d 
 file. I have talk to other on discord and they seemed to 
 agree with me.

 -Alex


 How about using an external tool [1] and check the "Prompt 
 for arguments" option ?
 The argument will be the test to run.

 [1] : 
 https://docs.microsoft.com/en-us/visualstudio/ide/managing-external-tools?view=vs-2019


 Have you try it and have it running on your machine?

 -Alex


 I'm on linux but this work similarly.
 First goes into the test folder and build the runner

    $ rdmd --build-only run.d

 Then setup the tool

 Command: run.exe
 Arguments: <leave empty>
 Initial Directory: <leave empty or select the folder where is 
 located run.exe>
 and check "Prompt for Arguments"

 then when you execute the tool you type the test name, incl. 
 the folder, for example "compilable/bug33.d"


 I shouldn't have to run this via console in order to test this. 
 This is just plan ridiculous. There are developmental virtual 
 machines for windows that is free for software development on 
 windows. We should not be stuck forever in the console era.


I meant "...software development on linux" not windows. 
Regardless I had figure it out already and it is not an idea 
solution.
Jan 05 2021
parent reply Basile B. <b2.temp gmx.com> writes:
On Wednesday, 6 January 2021 at 01:51:04 UTC, 12345swordy wrote:

 On Wednesday, 6 January 2021 at 00:40:24 UTC, 12345swordy wrote:

 On Tuesday, 5 January 2021 at 16:13:30 UTC, Basile B. wrote:

 On Tuesday, 5 January 2021 at 14:09:02 UTC, 12345swordy wrote:

 On Tuesday, 5 January 2021 at 04:20:57 UTC, Basile B. wrote:

 [...]


 Have you try it and have it running on your machine?

 -Alex


 I'm on linux but this work similarly.
 First goes into the test folder and build the runner

    $ rdmd --build-only run.d

 Then setup the tool

 Command: run.exe
 Arguments: <leave empty>
 Initial Directory: <leave empty or select the folder where is 
 located run.exe>
 and check "Prompt for Arguments"

 then when you execute the tool you type the test name, incl. 
 the folder, for example "compilable/bug33.d"


 I shouldn't have to run this via console in order to test 
 this. This is just plan ridiculous. There are developmental 
 virtual machines for windows that is free for software 
 development on windows. We should not be stuck forever in the 
 console era.


 I meant "...software development on linux" not windows. 
 Regardless I had figure it out already and it is not an idea 
 solution.


???

To avoid building manually run.d use directly rdmd as "Command", 
then tweak the "Arguments" fields.

Command: rdmd.exe
Arguments: <path to>\run.d
Initial Directory: <path to run.d>

and check "Prompt for Arguments" and then in the prompt you type 
the particular test to run. This step in unavoidable.
Jan 05 2021
parent reply 12345swordy <alexanderheistermann gmail.com> writes:
On Wednesday, 6 January 2021 at 02:17:50 UTC, Basile B. wrote:

 On Wednesday, 6 January 2021 at 01:51:04 UTC, 12345swordy wrote:

 On Wednesday, 6 January 2021 at 00:40:24 UTC, 12345swordy 
 wrote:

 [...]


 I meant "...software development on linux" not windows. 
 Regardless I had figure it out already and it is not an idea 
 solution.


 ???

 To avoid building manually run.d use directly rdmd as 
 "Command", then tweak the "Arguments" fields.

 Command: rdmd.exe
 Arguments: <path to>\run.d
 Initial Directory: <path to run.d>

 and check "Prompt for Arguments" and then in the prompt you 
 type the particular test to run. This step in unavoidable.


I am using this currently.
https://github.com/rainers/dlangvs/blob/master/vcbuild/dmd/dmd_test.vcxproj
Jan 05 2021
parent reply Basile B. <b2.temp gmx.com> writes:
On Wednesday, 6 January 2021 at 02:57:50 UTC, 12345swordy wrote:

 On Wednesday, 6 January 2021 at 02:17:50 UTC, Basile B. wrote:

 On Wednesday, 6 January 2021 at 01:51:04 UTC, 12345swordy 
 wrote:

 On Wednesday, 6 January 2021 at 00:40:24 UTC, 12345swordy 
 wrote:

 [...]


 I meant "...software development on linux" not windows. 
 Regardless I had figure it out already and it is not an idea 
 solution.


 ???

 To avoid building manually run.d use directly rdmd as 
 "Command", then tweak the "Arguments" fields.

 Command: rdmd.exe
 Arguments: <path to>\run.d
 Initial Directory: <path to run.d>

 and check "Prompt for Arguments" and then in the prompt you 
 type the particular test to run. This step in unavoidable.


 I am using this currently.
 https://github.com/rainers/dlangvs/blob/master/vcbuild/dmd/dmd_test.vcxproj


I don't follow you. What's wrong with the use of a tool ? Use the 
VS solution to build dmd and then use the external tool to run 
the the test suite. I mean it can be launched from the IDE, even 
with a shortcut so the fact that is is external is not blocker.
Jan 05 2021
parent reply 12345swordy <alexanderheistermann gmail.com> writes:
On Wednesday, 6 January 2021 at 03:13:56 UTC, Basile B. wrote:

 On Wednesday, 6 January 2021 at 02:57:50 UTC, 12345swordy wrote:

 On Wednesday, 6 January 2021 at 02:17:50 UTC, Basile B. wrote:

 On Wednesday, 6 January 2021 at 01:51:04 UTC, 12345swordy 
 wrote:

 On Wednesday, 6 January 2021 at 00:40:24 UTC, 12345swordy 
 wrote:

 [...]


 I meant "...software development on linux" not windows. 
 Regardless I had figure it out already and it is not an idea 
 solution.


 ???

 To avoid building manually run.d use directly rdmd as 
 "Command", then tweak the "Arguments" fields.

 Command: rdmd.exe
 Arguments: <path to>\run.d
 Initial Directory: <path to run.d>

 and check "Prompt for Arguments" and then in the prompt you 
 type the particular test to run. This step in unavoidable.


 I am using this currently.
 https://github.com/rainers/dlangvs/blob/master/vcbuild/dmd/dmd_test.vcxproj


 I don't follow you. What's wrong with the use of a tool ? Use 
 the VS solution to build dmd and then use the external tool to 
 run the the test suite. I mean it can be launched from the IDE, 
 even with a shortcut so the fact that is is external is not 
 blocker.


It is much easier for me to explain what the problem is if you 
managed to run visual studio on your local window machine.
Jan 05 2021
parent Basile B. <b2.temp gmx.com> writes:
On Wednesday, 6 January 2021 at 03:28:45 UTC, 12345swordy wrote:

 On Wednesday, 6 January 2021 at 03:13:56 UTC, Basile B. wrote:

 On Wednesday, 6 January 2021 at 02:57:50 UTC, 12345swordy 
 wrote:

 On Wednesday, 6 January 2021 at 02:17:50 UTC, Basile B. wrote:

 On Wednesday, 6 January 2021 at 01:51:04 UTC, 12345swordy 
 wrote:

 [...]


 ???

 To avoid building manually run.d use directly rdmd as 
 "Command", then tweak the "Arguments" fields.

 Command: rdmd.exe
 Arguments: <path to>\run.d
 Initial Directory: <path to run.d>

 and check "Prompt for Arguments" and then in the prompt you 
 type the particular test to run. This step in unavoidable.


 I am using this currently.
 https://github.com/rainers/dlangvs/blob/master/vcbuild/dmd/dmd_test.vcxproj


 I don't follow you. What's wrong with the use of a tool ? Use 
 the VS solution to build dmd and then use the external tool to 
 run the the test suite. I mean it can be launched from the 
 IDE, even with a shortcut so the fact that is is external is 
 not blocker.


 It is much easier for me to explain what the problem is if you 
 managed to run visual studio on your local window machine.


Yes and sorry, there is something not clear. I hope someone on 
Win could help.
To be clear, run.d is used by the different CIs, incl. those 
running Windows tests that's why I have not hesitated to reply 
even if I'm not a Windows user.
Jan 05 2021