Closed ghost closed 9 years ago
Hold on, they all return with a build error? That's awkward. There's a second issue related to this, so I'd be really interested in seeing what's going on there.
Yes. I'm not exactly sure what's going on, but here is the error message. (Changed name to X).
Building: X (Default) Performing main compilation... /usr/local/bin/dub build "X" "--build=plain" Error executing command build: Failed to find a package named 'X'.
Exit code 2 Build complete -- 1 error, 0 warnings
---------------------- Done ----------------------
Build: 1 error, 0 warnings
So for some reason, it is trying to do dub build "X" instead of just dub build
If there is any better information I can give you, I am more than happy to get that to you.
well, these arguments are intended to be there.
In my test project, it's invoking dub build "dubtest" "--build=plain"
successfully.
So..what's your package named then - in dub.json, as well as the folder name?
Okay, that actually helped. I think my problem was that my project name was all caps. I changed the name in the dub file to all lowercase, and everything works fine! I am closing.
Nice :) Am 05.11.2014 18:00 schrieb JonathanGallagher notifications@github.com:Okay, that actually helped. I think my problem was that my project name was all caps. I changed the name in the dub file to all lowercase, and everything works fine! I am closing.
—Reply to this email directly or view it on GitHub.
On Ubunt 14.04. I open a "dub.json" package in Mono-D, and then, selecting, build, run, or run tests, all give a build error.
Open a dub.json file via File>Open.
Note that under Edit>Preferences>D>Dub Options: dub executable: /usr/local/bin/dub Edit>Preferences>D>Unittests Unittest command: /usr/local/bin/dub test
I can fix building and running by going to Project>MyProject Options>Build>Custom Commands And in the dropdown menu, choose "Build" and enter the command /usr/local/bin/dub build And under Project>MyProject Options>Run>Custom Commands To the dropdown for "Execute" Add the exact name of the executable ... somethine like "$HOME/projects/MyProject/executable"
This seems to be a fine workaround. However, there is no custom command for unittest. So, how can I get unittests working, or better, how can I get the IDE's build options sorted the correct way.