search

burner / test_migration2

0 stars 0 forks source link

Please add a way to setup a "Dustmite" when project build is failed because of DMD or Link failed because of DMD bug #22

Closed burner closed 1 year ago

burner commented 3 years ago

apz28 reported this on 2021-01-27T13:10:19Z

Transfered from https://issues.dlang.org/show_bug.cgi?id=21588

CC List

Description

Please add a way to generate/create dustmite directory with all source files & command-line (batch file with dustmite command). If you can use the DMD build failed message and add that to dustmine command batch file is even better. When this feature button is clicked, prompt user to select/create a directory for dustmite

burner commented 3 years ago

r.sagitario commented on 2021-01-28T18:36:33Z

Are you aware of the existing integration? See https://rainers.github.io/visuald/visuald/DustMite.html

Does this work for your use case?

burner commented 3 years ago

apz28 commented on 2021-01-29T17:38:31Z

No since it try to check for "internal error ..." but in my case with different error message

main.exe : fatal error LNK1120: 43 unresolved externals Error: linker exited with status 1120

When using that feature, I got following error message object.Exception@DustMite\dustmite.d(367): Intial test fails: Test script "build.dustmite.bat 2>&1 | find \"Internal error\"" exited with exit code 1 (failure)

burner commented 3 years ago

r.sagitario commented on 2021-01-29T19:45:06Z

If you select a text in the output pane, it will use that instead of "internal error".

burner commented 3 years ago

apz28 commented on 2021-01-29T22:20:56Z

The problem is that the error message shown only in command line not in visuald. So if you can create/generate the batch file with actual dustmite command that it is running, then I can tweak it to whatever I need it to run

burner commented 3 years ago

r.sagitario commented on 2021-01-30T09:26:41Z

When you run the "Dustmite build failure" command, the console window shows the generated directory and the dustmite command in the very first line. You can copy and alter this command to check for other output and run it from the command line.

I guess the generated build.dustmite.bat will exhibit the same problem as when building from within Visual Studio, though. My first try would be removing pipedmd.exe wrapping the call to link.exe.