Configuration Error: Compiler is not properly called

[L0g4n]

Hi Guys,

tried Mono-D today for the first time. So I wanted to compile a sample project, but out of the build output I realized that the Compiler is not properly called. It just calls the compiler with dmd -debug but not with the files as arguments that have to be compiled. So I think this is just a config error, so how can I set up this properly ?

[aBothe]

Hi, is it? I haven't tested the native mono-d project support for ages, all I recently was up to was to support dub and all its features. So, I'd recommend getting your hands on dub and its infrastructure, then using mono-d on top of dub.

[L0g4n]

Hi, how can I do that ? Is there a addin for dub in XS ? I just began to work with the D programming language so I only know that DUB is smt. like Maven for java.

[aBothe]

well, mono-d is actually able to handle dub.json or dub.sdl files as project files and thus can open them like normal projects (read-only by design though).

All you may do is to

• install dub, for instance via your favorite package manager or from over here
• open up a command line and type 'dub init MyProject'
• open the dub.sdl that is inside the newly created MyProject-folder inside Mono-D (via regular Ctrl+O I suppose)
• code & build stuff

Note though that there's no proper debugging functionality built in mono-d atm, pretty much due to my lazyness and economic proportioning of my spare time :stuck_out_tongue: Still, there's Visual D and gdb on linux.

[aBothe]

Still, if you like coding for D in like C#, just take a look on Mono-D's source code. The parser and code completion resolution part is somewhat magic :)

[L0g4n]

OK, made that so far. But compiling through the IDE still does not work. Error Message: "The invoked target caused an exception.". And when I click on the "Code" tab in XS, there are the comments: "// No matching .lst-file found! // Build & execute your project with e.g. dmd's -cov flag set!"

[aBothe]

"The invoked target caused an exception" -- this is strange. On which OS are you working?

The 'dmd -cov' thing is for code coverage highlighting purposes and purely optional, so not related to the current problem.

[L0g4n]

I'm currently on Windows 10.

[aBothe]

For me, building & executing a dummy dub project works flawlessly. Hmm. There's a build log that can be displayed and there are logs that can be read in order to get the error message. Dub can be accessed via %PATH%, right?

[L0g4n]

Hi, yeah dub directory is in the PATH variable. I think this is the suitable exception message: http://pastebin.com/Cjv02Bn3

[aBothe]

Weird issue, never had this before. Oh boy.

[L0g4n]

That does not sound good. Is it an error I can fix by myself ?

[aBothe]

Please activate the D Profiler pad for once, then we'll see if it crashes again - as its GUI constructor might be corrupted by some magic side effects.

[L0g4n]

Hey, surprisingly it works now flawlessly. So do I have to enable the D Profiler every tme again ?

[aBothe]

Just leave it open as some pad in the background - it'll be opened on the next launch of XS.