Visual D cannot build Phobos Browse Info

[Rainer Schuetze via Digitalmars-d-ide]

On 20.09.2014 20:08, DLimited wrote:
> Alright, I need some help because I feel mighty stupid at the moment.
> Please do keep in mind that I just now started up with D and Visual
> Studio in general.
>
> I'm using VS2012 Ultimate with Visual D. During my test project I
> noticed I did not get any value help / displayed info on neither the Gtk
> framework, nor the standard library.
>
> So, it seems to me all the displayed documentation is stored in some
> JSON file somewhere. The "Generate Phobos Browse Info" is supposed to
> generate them for the phobos library, however it fails with the
> following message:
>
>>> Building phobos JSON browse information files to
>>> C:\Users\DLimited\AppData\Roaming\VisualD\json\
>>> dmd.exe not found in DMDInstallDir=C:\dmd\dmd2\windows\bin\ or
>>> through PATH

The DMD installation dir should be set to C:\dmd\dmd2 only, without the 
windows\bin sub-directories. I'm not sure why PATH doesn't work, but 
finding the imports will probably rely on the installation dir anyway.

If you use the default semantic analysis engine (Alexander Bothe's 
engine enabled in the Intellisense settings), JSON information should 
not be necessary anymore and are only used as a fallback if semantic 
analysis fails.

It is important to have the import directories setup correctly (for 
phobos, it is derived from the installation directory; for gtk, it 
should probably be part of the project settings).



>
> DMD is actually located in that directory, though - as well as in the
> path. Starting a random command line knows dmd; also my test project
> compiles (and it can't possibly compile without a compiler, can it?)
>
> I have no idea what the actual generation process is, so I can't do it
> "manually" and place in the JSON import path either.
>
> So, I'd love some help with this, I am at my wits end. I have no idea
> what the problem could be, because the displayed cause cannot be true
> unless the command fucks up the execution environment somehow. It also
> cannot be a read/write error because writing to AppData is always allowed.
>
> Kind regards,
>
> DLimited