OK, here’s an annoying problem…
I’m wrangling with our “Lord High Executioner” in charge of shooting all
developers who don’t adhere to internal standards regarding folder & file
organization of project source code, etc…, regarding incorporating Windows
DDK based projects into our build environment & source code management
systems [VSS]. For what it’s worth, there’s some embedded whitespace in the
paths leading to where DDK based projects are stored. It appears that the
makefile processing done by the BUILD utility is lacking some double quotes
around the full path name of target files.
Is there a known issue with this with a fix involving modifying the default
makefile? Or, is it a requirement that all Windows DDK based projects must
reside on paths w/o embedded whitespace in their names?
TIA,
Chuck
Chuck,
This is a BUILD restriction that has been there for the 13 years I’ve
used the tool. Modifying the default makefile is not a good idea.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
“Chuck Chopp” wrote in message news:xxxxx@ntfsd…
> OK, here’s an annoying problem…
>
> I’m wrangling with our “Lord High Executioner” in charge of shooting all
> developers who don’t adhere to internal standards regarding folder & file
> organization of project source code, etc…, regarding incorporating
> Windows DDK based projects into our build environment & source code
> management systems [VSS]. For what it’s worth, there’s some embedded
> whitespace in the paths leading to where DDK based projects are stored.
> It appears that the makefile processing done by the BUILD utility is
> lacking some double quotes around the full path name of target files.
>
> Is there a known issue with this with a fix involving modifying the
> default makefile? Or, is it a requirement that all Windows DDK based
> projects must reside on paths w/o embedded whitespace in their names?
>
>
> TIA,
>
> Chuck
>
Don Burn wrote:
Chuck,
This is a BUILD restriction that has been there for the 13 years I’ve
used the tool. Modifying the default makefile is not a good idea.
That’s fair enough. I’ll simply pass that on back to the individual who’s
being a stick in the mud on this issue and let him know that it requires a
path w/o embedded whitespace.
Interestingly enough, this issue came up because of a goal to keep all local
copies of project files located under the user’s profile in Windows, rather
than in some other location on the C: drive. Unfortunately, on WinxP,
that’s under “C:\Documents and Settings”, which is where the problem comes
in. On Vista, it’s a non-issue since it’s under “C:\Users”.
I would say it’s probably a bad idea to use embedded whitespace in your
paths no matter what build environment you’re in. Maybe you could get
away with it using VS, because all the tools come from MS and it’s
reasonable to assume that they were written with a Windows paradigm in
mind. I’ve had problems with Java libraries that wouldn’t link properly
if they were under “C:\Program Files” in the past, and I’m pretty sure
no place I’ve ever worked has even dreamed of using embedded whitespace
in a Unix build environment.
I’m not saying it wouldn’t work, but it relies on every tool and
everything in the Makefile handling the whitespace correctly. Maybe it
would, but it introduces another opportunity to bite you in an
unexpected way. Given that the Unix paradigm has long dispensed with
readability to the gain of brevity, I’m guessing that this would be
playing with fire at best.
~Eric
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Chuck Chopp
Sent: Wednesday, September 19, 2007 8:56 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Long path/file names with embedded whitespace & the DDK
build environment
OK, here’s an annoying problem…
I’m wrangling with our “Lord High Executioner” in charge of shooting all
developers who don’t adhere to internal standards regarding folder &
file organization of project source code, etc…, regarding
incorporating Windows DDK based projects into our build environment &
source code management systems [VSS]. For what it’s worth, there’s some
embedded whitespace in the paths leading to where DDK based projects are
stored. It appears that the makefile processing done by the BUILD
utility is lacking some double quotes around the full path name of
target files.
Is there a known issue with this with a fix involving modifying the
default makefile? Or, is it a requirement that all Windows DDK based
projects must reside on paths w/o embedded whitespace in their names?
TIA,
Chuck
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars (including our new
fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@edsiohio.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
Quoting Chuck Chopp :
> Interestingly enough, this issue came up because of a goal to keep all local
>
> copies of project files located under the user’s profile in Windows, rather
> than in some other location on the C: drive. Unfortunately, on WinxP,
> that’s under “C:\Documents and Settings”, which is where the problem comes
> in. On Vista, it’s a non-issue since it’s under “C:\Users”.
>
You can refer to these nasty long names with funny characters with their short name.
Documents and Settings is typically known as DOCUME~1
If you cd DOCUME~1\MYPROF\WHEREEVER then build should work.
if you have other awkward bits of path DIR /X will list the shortnames used.