'dub build' fails with Derelict

[mdparker]

Two cases.

1. When Derelict is not already installed.

Checking dependencies in 'C:\dev\d\projects\libs\Derelict3'
Error: Unknown dependency: derelict:devil

2. When Derelict is already installed.

Checking dependencies in 'C:\dev\d\projects\libs\Derelict3'
The same package is referenced in different paths:
derelict ~master: C:\dev\d\projects\libs\Derelict3
derelict ~master: C:\Users\Mike Parker\AppData\Roaming\dub\packages\derelict-m
aster
Error: Conflicting package multi-references.

This second case will make it difficult to use dub to develop a library and use it in other apps on the same system.

[QAston]

I'm having same problem here, dub can't find subpackage when specified with "packagename:subpackage" dependency.

[MrSmith33]

Derelict can not be built though

Checking dependencies in 'H:\anchovy\deps\derelict-master'
Building configuration "library", build type debug
Error: Assertion failure

Run 'dub help' for usage information.

[s-ludwig]

I broke that again by fixing #92. Correcting now.

[MrSmith33]

Derelict now builds fine, but my project still not. Same error. Anchovy

[s-ludwig]

The first issue is that "anchovy:utils" is referenced as "anchovy:util" in some places. I've fixed the error message.

Unfortunately there is another issue that I'm going to look into now.

[s-ludwig]

Okay next issue is that there is a dependency cycle between "anchovy:core" and "anchovy:utils". I though there is a check for that, but apparently that's missing. Final issue, when doing "dub build" from the package root directory, is that instead of a useful error message, DUB complains about an unset target name (it should really either say that the target type is "none", or build all sub packages). I'll fix that, too, after I've implemented custom build types. Using anchovy in other projects should work with the dependency cycle fixed, though.