-
Notifications
You must be signed in to change notification settings - Fork 16
Executable file doesnt exist #58
Comments
I need more info here. What is the dub.json of your project like? When you save a file (a therefore trigger a build), what is the output of the the "dub build" process that is invoked by Eclipse? This should appear in the console. |
I have the same problem. Here is the console output:
|
Ok I fixed the problem: The dub.json file does not contain the key Hope that helps others. I think it would be nice if DDT would ask for the type of desired configuration when creating a new project. |
if the DUB build doesn't produce an executable, there is nothing DDT can do here, other than perhaps show a nicer error message. If the DUB build produces an executable, but only on certain configurations, then the issue is #49 |
There is a misunderstanding it seems. From what I can see in DDT:
(source being empty) dub.json:
... and following console output:
So in essence, a freshly generated project does not compile, since it seems to be misconfigured. IMHO either the Which leads me to my previously mentioned point, that DDT should provide choice (executable or library) on project creation and configure the dub.json accordingly. Unless I am terribly mistaken. |
I thik I just made a similar suggestion in my comments on #63 |
Note that under DUB rules, if a "app.d" file is present, DUB will try to build with application type, so it's not necessary to explicitly state "targetType" in dub.json |
I am able to complie D programs via the Terminal (I am running Eclipse on Ubuntu 14.04) but every time i try and run a project it fails to build and gives me this error:
"Executable file (/fakepathto/workspace/test/test) doesnt exist."
Build automatically is already selected, but it refuses to compile.
The text was updated successfully, but these errors were encountered: