Thread overview
VisualD and dub imports - module X is in 'X.d' which cannot be read
Feb 16, 2015
Geoff Howland
Feb 17, 2015
Geoff Howland
Feb 19, 2015
Mike Parker
February 16, 2015
Hopefully this is the right forum to use for this question, Im having a problem with VisualD and dub builds.

I made a simple vibe.d project with Dub, it works from CLI and in VisualD.  When I add the "dyaml" package to dub.json, the CLI still works, but the VisualD compiler gives me this error "module yaml is in file 'yaml.d' which cannot be read".

I cant find where dub is putting the dyaml package, and while I found some related answers in forums and SO, but I didnt find a solution to this.

Anyone know how to solve this?  Does dub download the yaml.d file and put it someplace?  It doesnt seem to be under the project directory I created, and it also isnt in the sparse dub directory that the windows dub installer creates.

Things I've tried:

- Finding where yaml.d is put by dub, so I can include it in the build.
- Looking through the .dub directory for anything that looks related to this.
- Searching through the forums here (via Google) and Stack Overflow.

Any help would be appreciated.

-g
February 17, 2015
On Monday, 16 February 2015 at 01:29:32 UTC, Geoff Howland wrote:
> Hopefully this is the right forum to use for this question, Im having a problem with VisualD and dub builds.
>
> I made a simple vibe.d project with Dub, it works from CLI and in VisualD.  When I add the "dyaml" package to dub.json, the CLI still works, but the VisualD compiler gives me this error "module yaml is in file 'yaml.d' which cannot be read".

I solved this:  it requires "dub generate visuald" to be run again.  Apparently needed after any changes to dub.json, as it does not get picked up automatically.  This added the entries to the VisualD project XML files, and then the module/files could be found.

-g
February 19, 2015
On Tuesday, 17 February 2015 at 07:52:47 UTC, Geoff Howland wrote:
> On Monday, 16 February 2015 at 01:29:32 UTC, Geoff Howland wrote:
>> Hopefully this is the right forum to use for this question, Im having a problem with VisualD and dub builds.
>>
>> I made a simple vibe.d project with Dub, it works from CLI and in VisualD.  When I add the "dyaml" package to dub.json, the CLI still works, but the VisualD compiler gives me this error "module yaml is in file 'yaml.d' which cannot be read".
>
> I solved this:  it requires "dub generate visuald" to be run again.  Apparently needed after any changes to dub.json, as it does not get picked up automatically.  This added the entries to the VisualD project XML files, and then the module/files could be found.
>
> -g

For future reference, DUB installs downloaded packages in your app data directory (on Windows 7, C:\Users\UserName\AppData\Roaming\dub\packages)