DDT-IDE / DDT

DDT is an Eclipse-based IDE for the D programming language:
http://ddt-ide.github.io/
101 stars 16 forks source link

No D std library found and Dub returned with exit code 2, but it correctly compiles #81

Closed MakersF closed 10 years ago

MakersF commented 10 years ago

I'm working on Eclipse Luna (the one with only JDK) and I only added DDT(0.10.2) as plug in on Windows 7. Currently DDT is signalling me errors in the project and auto completion is not working, even if the compilation correctly works. I'm using the --compiler option in order to use a compiler that is not in PATH. I looked around, but didn't find a way to specify where the sources are located for the DDT to find them. When correctly setting the PATH environment with the directory containing the error doesn't show up (but still auto completion is not working)

In any case, the compilation works correctly, so maybe the limitation referenced in https://github.com/bruno-medeiros/DDT/issues/71 doesn't apply any longer? So, would it be possible to add a preference to specify where to look for the standard library?

Here the picture showing the errors: D Standard Library [Error: none found] DUB Dependencies [DUB error]: dub returned non-zero status: 2 error

Here a screenshot when the PATH has C:\dmd2\windows\bin in it error2

MakersF commented 10 years ago

As a temporary solution I'm running Eclipse with a bat file containing

set DUB_COMPILERS_PATH=c:\dmd2\windows\bin
set PATH=%PATH%;C:\dmd2\windows\bin
start "" "C:\mypath\eclipse.exe"

Still, content assist is not working

bruno-medeiros commented 10 years ago

It seems to me the content assist problem is unrelated to the DUB setup (which seems to be correct now). Post me the Eclipse log: "Help/About/Installation Details/Configuration/Error Log"

bruno-medeiros commented 10 years ago

Also the set PATH=%PATH%;C:\dmd2\windows\bin should not be necessary, if DUB_COMPILERS_PATH is already set. In addition, this means you can set DUB_COMPILERS_PATH in your user environment, no need to use a BAT file.

MakersF commented 10 years ago

http://www.pasteall.org/54616/text Here is the configuration

Here is the error log http://www.pasteall.org/54617/text

The home assumption it makes is correct. In all the sessions it wasn't able to autocomplete (even if not in everyone of them was the invalid path error)

bruno-medeiros commented 10 years ago

Hum, why isn't there any relevant error in the log? :S Try running "C:\mypath\eclipsec.exe" -consoleLog , and attempt Content Assist, to see if any message pops up in the console. (note that's eclipsec.exe , not eclipse.exe)

MakersF commented 10 years ago

I don't have the PC with me right now. Will do as soon as I have access to it in a few hours Il 17/ott/2014 19:51 "Bruno Medeiros" notifications@github.com ha scritto:

Hum, why isn't there any relevant error in the log? :S Try running "C:\mypath\eclipsec.exe" -consoleLog , and attempt Content Assist, to see if any message pops up in the console. (note that's eclipsec.exe , not eclipse.exe)

— Reply to this email directly or view it on GitHub https://github.com/bruno-medeiros/DDT/issues/81#issuecomment-59550087.

MakersF commented 10 years ago

Here is the log http://www.pasteall.org/54628/text

Every time I modify the file this two lines get written, but there is no error whatsoever.

ParseCache: Set working copy: C:\Users\Francesco\Desktop\Programmazione\D\Workspace\Prova\source\main.d ParseCache: Parsed module C:\Users\Francesco\Desktop\Programmazione\D\Workspace\Prova\source\main.d [WorkingCopy]

Do you want to send me a debug version with some more logging to understand what's happening? Or I can send you my eclipse + workspace, but it actually is just Eclipse Luna with the DDT plugin added and an empty workspace where I generated a DUB project, and pasted a sample program.

bruno-medeiros commented 10 years ago

Ahhhh, after some head scratching I think I found the cause... is "dub" on the PATH? It has to be, despite the DUB path option in DDT preferences (it's a bug, yes. It's related to #73).

I've added logging to the place where it was missing (There is no debugging version, the standard version should do a basic log of all error events.)

MakersF commented 10 years ago

Confirmed this was the problem. Added DUB to the path in the launcher script and everything works fine now.

Correct issue is now https://github.com/bruno-medeiros/DDT/issues/82