You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using dub with --compiler=gdc on Windows fails due to path separator issues. Here a sample of the verbose output:
Building configuration "application", build type debug
Application output name is 'D:\projects\D.Scratchpad\DubBasicTest\dub_basic_test.exe'
Running gdc...
gdc -o D:\projects\D.Scratchpad\DubBasicTest\dub_basic_test.exe -fversion=Have_dub_basic_test -ID:\projects\D.Scratchpad\DubBasicTest\source source\app.d source\func_mod.d
gdc: error: sourceapp.d: No such file or directory
gdc: error: sourcefunc_mod.d: No such file or directory
gdc: fatal error: no input files
compilation terminated.
Error: Build command failed with exit code 1
Someone is interpreting those backlashes as escape characters. And it seems to be dub, since if I invoke gdc directly from the cmd-line, with the gdc line above, works.
The text was updated successfully, but these errors were encountered:
Using dub with --compiler=gdc on Windows fails due to path separator issues. Here a sample of the verbose output:
Someone is interpreting those backlashes as escape characters. And it seems to be dub, since if I invoke gdc directly from the cmd-line, with the gdc line above, works.
The text was updated successfully, but these errors were encountered: