On Fri, 3 Nov 2017 20:54:32 +0100, Sönke Ludwig wrote:

Am 31.10.2017 um 03:14 schrieb Kyle Heaser:

On Mon, 30 Oct 2017 20:37:07 GMT, Kyle Heaser wrote:

I find it particularly odd that even though I explicitly specify glfw3 3.1.0, dub gives me 3.1.3.


I came across the versioning semantics so it is working the way the ~> is meant to. So why are just these two packages failing but the other ones are fine?

I tried deleting all my dub local caches and starting from scratch, with the same errors.

Can you verify whether that file actually exists, or is just
inaccessible? Depending on who generates that exact error message, it
could also in theory be something that causes the path length limit to
be exceeded. To rule that out, putting the package in a shorter path
should work:

 cd c:
 cd \
 dub fetch derelict-glfw3 --cache=local --version=3.1.3
 dub add-local .\derelict-glfw3

Other than that, does running a normal build instead of defining DFLAGS
perhaps make a different?

The file actually exists. And its permissions are rwx, or the Windows equivalent.

I get this error in the dub add-local command:

C:\>dub fetch derelict-glfw3 --cache=local --version=3.1.3
Fetching derelict-glfw3 3.1.3...

C:\>dub add-local .\derelict-glfw3
No package file found in C:\derelict-glfw3\, expected one of dub.json/dub.sdl/package.json

Does "--cache=local" mean to place the fetched package in the current directory of the command line?