Bug 2249 – DMD can't handle include paths with spaces in them

Symptom: When 'dmd somefile.d' get: object.d: module object cannot read file 'object.d' Probable reason: probably does not handle spaces in path in -I for DFLAGS in sc.ini coming from %@P% which I believe to be the path of DMD. I tried to write full path to -IC:\... in sc.ini, but that did not helped. I use an openshell.bat file: ========== @echo off PATH=%CD%\bin;%PATH% PROMPT=%USERNAME%@%COMPUTERNAME%:$P$G$S COLOR 0F ECHO Shell setup for Digital Mars D Compiling and Debugging ECHO change which drive you're on: [Drive Letter]:\ ECHO eg. C:\ to change to C drive %HOMEDRIVE% CD %HOMEPATH% CMD ============ Does not work on my Desktop (probably because of "Documents and Settings"). So I tried do decompress to "C:\OKTANGO" the whole thing. Was working fine there. Then renamed to "C:\BAD TANGO" and rerun openshell.bat and recompile hello.d, with the "object.d: module object cannot read file 'object.d'" message. I am using tangobos-0.99.7-bin-win32-dmd.1.033.

Yup, dmd can't handle include paths with spaces in them, at least not when settings them in sc.ini. It's annoying, but more or less documented here: http://www.digitalmars.com/d/1.0/dmd-windows.html#problems It's likely that the linker (optlink) can't handle paths with spaces either, and that's not likely to be fixed anytime soon. So avoiding spaces is the way to go.

This problem will be fixed in future releases?

(In reply to comment #2) > This problem will be fixed in future releases? No. Optlink hasn't been changed in a decade, AFAIK; its bugs will probably never get fixed.

I think that the linker is a separate issue -- importing modules is strictly a front-end issue, and an annoying one, if one is foolish enough to install D in, say, c:\Program Files\Digital Mars\

Is this problem will be forever? This will impose restrictions on the IDE for D and installers. If the linker can be used other (not Optlink) that the compiler - no. Walter, please, fix it.

It's working with the latest dmd.