Am 03.11.2013 02:31, schrieb Andrej Mitrovic:

Using DUB version v0.9.19.

I've tried using this package:

...

And then I've tried running with: 

C:\dev\projects\dchip>dub --config=demo
Checking dependencies in 'C:\dev\projects\dchip'
Building configuration "demo", build type debug
Compiling...
DMD v2.064 DEBUG
Linking...
DMD v2.064 DEBUG
Error: C:\dev\projects\dchip\demo_app: The system cannot find the file specified.

Then I've tried using an absolute path: 

"targetPath" : "C:\demo_app"

Called it again: 

C:\dev\projects\dchip>dub --config=demo
Checking dependencies in 'C:\dev\projects\dchip'
Building configuration "demo", build type debug
Compiling...
DMD v2.064 DEBUG
Linking...
DMD v2.064 DEBUG
Error: Trying to append absolute path.

And then I just tried using the defaults, so I removed targetPath and built: 

C:\dev\projects\dchip>dub --config=demo
Checking dependencies in 'C:\dev\projects\dchip'
Building configuration "demo", build type debug
Compiling...
DMD v2.064 DEBUG
Linking...
DMD v2.064 DEBUG
Running C:\Users\ADMINI~1\AppData\Local\Temp\dub\2055224000\example-app.exe...
Error: Program exited with code -1073741515

Run 'dub help' for usage information.

So I want to inspect what went wrong with the executable, but then I see dub has actually deleted it. Why would it remove the generated exe if it failed to run properly? I can't inspect it if it's gone.

Both of the first two work fine when I try with git master. However, the
behavior for "dub" or "dub run" is currently to ignore "targetPath" and
instead use a temporary directory. This is subject to change (see
#82), but currently
"dub build && demo_app/example-app" needs to be used instead.

BTW (assuming that the package.json doesn't have more configurations),
you don't need to explicitly select the configuration as long as it is
the first in the list that matches the current platform.