On Wednesday, 9 December 2015 at 15:31:46 UTC, default0 wrote:
> On Wednesday, 9 December 2015 at 12:10:33 UTC, Vadim Lopatin Thanks for the instructions! I followed them, but when I tried to build in Visual Studio, I got the following error:
> C:\Users\Administrator\Documents\DCode\DlangUI\src\dlangui\graphics\images.d(34): Error: module io is in file 'dlib\image\io\io.d' which cannot be read
...
> I checked the import path[9] it listed, and relative to that path, there is the dlib/image/io/io.d file (ie in "C:\Users\Administrator\Documents\DCode\DlangUI\..\dlib\dlib\image\io\io.d"). I'm not sure why it doesn't find that file, despite listing a path that contains this file in the imports (and has the necessary permissions for reading it, and the file obviously not being used by anything). I'm using Visual D.
>
> Pretty stumped on that right now, building with dub obviously works, and I suppose I could then attach the debugger from within Visual Studio, but that's not a workflow I'm looking forward to (nor do I know if it works the way I hope)...

Looks like you have opened obsolete project.
Deps should be in dlangui/deps, not in dlangui/..
Probably, you have used old build instructions.
See at end of dlangide's README.md
Open dlangui/dlangui-msvc.sln

On Wednesday, 9 December 2015 at 16:26:14 UTC, Vadim Lopatin wrote:
> On Wednesday, 9 December 2015 at 15:31:46 UTC, default0 wrote:
> Looks like you have opened obsolete project.
> Deps should be in dlangui/deps, not in dlangui/..
> Probably, you have used old build instructions.
> See at end of dlangide's README.md
> Open dlangui/dlangui-msvc.sln

I did open that solution (I even double checked I got the right one). So no, that's not it, I'm afraid :/

I should mention that the dlangui\.. is some build artifact, too, the files are in dlangui\deps locally (it probably tries to shorten the path name?)

On Tuesday, 8 December 2015 at 18:18:29 UTC, default0 wrote:
> On Tuesday, 8 December 2015 at 15:58:43 UTC, Vadim Lopatin wrote:
>> Hello,
>>
>> DlangIDE is getting close to usable.
>> DlangIDE is and IDE for D programming language written in D using DlangUI library.
>
> Sweet! Glad you're back and working on this!
> Was wanting to give it a shot, but typing } on my keyboard (german layout, right-alt + 0) did not actually insert the character into the opened document, so I gave up.

As a European, I have a secret trick about keyboards, that I "got for free" with my Kaypro-II computer (the blue-key version), back in 1984.

Always use the en-US keyboard when programming. Period!

Keys, such as []{}\/?|*$ etc. are in very handy and quick places. The inventors of programming languages and operating systems have put the most used characters in easy-to-reach keys. -- And on top of it, all of the funky key combinations just work.

On Linux, I merely press both Shifts to temporarily switch to my native language, which I only need for text strings, nothing else. I'd expect Windows and Mac to provide something similar.

After a couple of weeks, you'll never look back.

On Wednesday, 9 December 2015 at 19:24:19 UTC, default0 wrote:
> I should mention that the dlangui\.. is some build artifact, too, the files are in dlangui\deps locally (it probably tries to shorten the path name?)

I found that I forgot to change project import paths for all configurations.
I used Debug/X64 only so did not notice it. You probably using Debug/win32.

Fixed. Project file is updated.

On Tuesday, 8 December 2015 at 15:58:43 UTC, Vadim Lopatin wrote:
> Hello,
>
> DlangIDE is getting close to usable.
> DlangIDE is and IDE for D programming language written in D using DlangUI library.
>
> Project page: https://github.com/buggins/dlangide

Recent changes:

Settings for DUB, GDB, DMD, LDC, GDC, xterm.
Project settings allow to select toolchain, architecture for building, commandline parameters and working directory for running.
Running of project is done as spawn instead of DUB run. External terminal is supported.
New project wizard is improved.
New source file wizard added.
Workspace tree context menus allow to add/remove projects, files, build/clean/rebuild/run projects.

Current activity: GDB debugging support.

On Tuesday, 8 December 2015 at 15:58:43 UTC, Vadim Lopatin wrote:
> Hello,
>
> DlangIDE is getting close to usable.
> DlangIDE is and IDE for D programming language written in D using DlangUI library.
>
> Project page: https://github.com/buggins/dlangide
>
> To try, use `dub fetch dlangide && dub run dlangide` try to create and run DlangUI Helloworld project, or open Tetris project from workspaces/tetris.

Initial GDB debugging support is implemented.

You can start / stop debugging, set breakpoints, step in/out/over, continue.

TODO: stack trace & local variables display


As well, following features implemented:
- bookmarks in source files (toggle, go to next/prev)
- recent workspace list

On Wednesday, 16 December 2015 at 12:50:25 UTC, Vadim Lopatin wrote:
> On Tuesday, 8 December 2015 at 15:58:43 UTC, Vadim Lopatin wrote:
>> Hello,
>>
>> DlangIDE is getting close to usable.
>> DlangIDE is and IDE for D programming language written in D using DlangUI library.
>>
>> Project page: https://github.com/buggins/dlangide
>>
>> To try, use `dub fetch dlangide && dub run dlangide` try to create and run DlangUI Helloworld project, or open Tetris project from workspaces/tetris.
>
> Initial GDB debugging support is implemented.
>
> You can start / stop debugging, set breakpoints, step in/out/over, continue.
>
> TODO: stack trace & local variables display
>
>
> As well, following features implemented:
> - bookmarks in source files (toggle, go to next/prev)
> - recent workspace list

Exellent progress! Congrats!

On Thursday, 17 December 2015 at 08:27:05 UTC, ZombineDev wrote:
>> Initial GDB debugging support is implemented.
>>
>> You can start / stop debugging, set breakpoints, step in/out/over, continue.
>>
>> TODO: stack trace & local variables display
>>
>>
>> As well, following features implemented:
>> - bookmarks in source files (toggle, go to next/prev)
>> - recent workspace list
>
> Exellent progress! Congrats!

GDB support improvements: stack and local variables windows added.

On Friday, 18 December 2015 at 10:41:13 UTC, Vadim Lopatin wrote:
> On Thursday, 17 December 2015 at 08:27:05 UTC, ZombineDev wrote:
>
> GDB support improvements: stack and local variables windows added.

This is quick progress! Awesome! I finally have some free time on my hands, so I deleted my workspace and tried to set things up following the How to hack on DlangIDE steps again. After doing that and trying to compile on Debug/Win32 I get output with a linker error:
Building Debug\dlangide.exe...
Microsoft (R) Incremental Linker Version 14.00.23026.0
Copyright (C) Microsoft Corporation.  All rights reserved.

"Debug\dlangide.obj,Debug\dlangide.exe,Debug\dlangide.map,C:\Users\Administrator\Documents\DCode\dlangui\Debug\dlangui.lib+"
ole32.lib+
kernel32.lib+
user32.lib+
comctl32.lib+
comdlg32.lib+
psapi.lib+
user32.lib+
kernel32.lib/NOMAP/CO/NOI/DELEXE /SUBSYSTEM:WINDOWS
LINK : fatal error LNK1104: Datei "Debug\dlangide.obj,Debug\dlangide.exe,Debug\dlangide.map,C:\Users\Administrator\Documents\DCode\dlangui\Debug\dlangui.lib+" kann nicht geöffnet werden.
Building Debug\dlangide.exe failed!

The dlangui project builds correctly btw (it's the only one in the solution that does).

If I change to Debug/x64 I get a popup from VS telling me that it couldn't find the right project to launch since there are no startup projects set (even though I did set DlangIDE as startup project and it shows). If I explicitly tell it to build dlangide (right-click the project > build) I get another linker error telling me it cannot open "phobos64.lib". I do have phobos64.lib in the normal directory it is in after installation (ie windows/lib64), but for some reason it doesn't pick up on that. I even tried setting PATH directly to it, but that also didn't help.

I started up ProcessMonitor and looked at where it was searching for phobos64.lib and the results were pretty worrying:
C:\Users\Administrator\Documents\DCode\dlangide\phobos64.lib
C:\Users\Administrator\Documents\DCode\dlangide\phobos64.lib
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\lib\amd64\phobos64.lib
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\lib\amd64\phobos64.lib
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.10150.0\ucrt\x64\phobos64.lib
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.10150.0\ucrt\x64\phobos64.lib
C:\Program Files (x86)\Windows Kits\8.1\Lib\winv6.3\um\x64\phobos64.lib
C:\Program Files (x86)\Windows Kits\8.1\Lib\winv6.3\um\x64\phobos64.lib
C:\Users\Administrator\Documents\DCode\dlangide\phobos64.lib
C:\Users\Administrator\Documents\DCode\dlangide\phobos64.lib
C:\Users\Administrator\Documents\DCode\dlangide\phobos64.lib

Where DCode\dlangide is obviously the path where I set things up. The rest seem to be things coming from automatic configuration VS has done at some point. I'm not sure how or where I can tell it to also look into my dmd installation paths.

Now instead of going for a proper fix I simply attempted copying the phobos64.lib to the dlangide directory just to see if this would get it to compile: Turns out it doesn't. When trying to compile like that, I get a popup saying

std.utf.UTFException@c:\s\d\rainers\phobos\std\utf.d(1109): Invalid UTF-8 sequence (at index 1)

Is this an ICE? Is my Visual D installation broken (I did reinstall Visual D a few times by now already)? I'm using dmd 2.069.2 which is the most recent version to my knowledge.

Pretty stumped about all of this and this looks a lot like something in my VS or VD setup is horribly broken (especially looking at the Win32 linker errors and the lack of properly configured search paths for phobos64.lib), but I'm not sure what exactly or how to go about fixing it/narrowing down the problem.

Any help in somehow getting this all to build would be much appreciated. Oh and of course "dub run" works just fine.