DDK and spaces in path?

Hi,


After converting our driver product build environment from VS.NET 2003
(which compiler is not supported for drivers) into a DDK BUILD project (using
a makefile project and ddkbuild.bat), I notice that all our build servers and
most of our development stations no longer can build this driver, due to
spaces in the build path.

This post is suggesting a workaround to build paths with spaces
http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.development.device.drivers&mid=7a7b1ddb-8d6a-4502-86cc-609ad8870cb3&sloc=en-us

Our driver is not using any Java. Which is safer?
1. Remove the $(MAKEDIR) as suggested in the above posting, or
2. Comment out this entire call to jvc (2 lines) as suggested in the above
posting

Also, can this harm our C/C++ driver?
Is our DDK build environment still "supported" with this change?


Thanks,

/ Hannes.

Mark
Mon Feb 07 14:29:55 CST 2005

My suggestion is to get rid of the spaces in your directory names, use "_".

--
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/
"Hannes" <hannes@nospam.nospam> wrote in message
news:EFE15D19-6D6A-4276-AA31-98861AC172FF@microsoft.com...
> Hi,
>
>
> After converting our driver product build environment from VS.NET 2003
> (which compiler is not supported for drivers) into a DDK BUILD project
> (using
> a makefile project and ddkbuild.bat), I notice that all our build servers
> and
> most of our development stations no longer can build this driver, due to
> spaces in the build path.
>
> This post is suggesting a workaround to build paths with spaces:
> http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.development.device.drivers&mid=7a7b1ddb-8d6a-4502-86cc-609ad8870cb3&sloc=en-us
>
> Our driver is not using any Java. Which is safer?
> 1. Remove the $(MAKEDIR) as suggested in the above posting, or
> 2. Comment out this entire call to jvc (2 lines) as suggested in the above
> posting
>
> Also, can this harm our C/C++ driver?
> Is our DDK build environment still "supported" with this change?
>
>
> Thanks,
>
> / Hannes.

Maxim
Wed Feb 09 00:31:36 CST 2005

Just do not use spaces in pathnames where your project residers. Is it so
complex?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Hannes" <hannes@nospam.nospam> wrote in message
news:EFE15D19-6D6A-4276-AA31-98861AC172FF@microsoft.com...
> Hi,
>
>
> After converting our driver product build environment from VS.NET 2003
> (which compiler is not supported for drivers) into a DDK BUILD project (using
> a makefile project and ddkbuild.bat), I notice that all our build servers and
> most of our development stations no longer can build this driver, due to
> spaces in the build path.
>
> This post is suggesting a workaround to build paths with spaces:
>
http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.development.device.drivers&mid=7a7b1ddb-8d6a-4502-86cc-609ad8870cb3&sloc=en-us
>
> Our driver is not using any Java. Which is safer?
> 1. Remove the $(MAKEDIR) as suggested in the above posting, or
> 2. Comment out this entire call to jvc (2 lines) as suggested in the above
> posting
>
> Also, can this harm our C/C++ driver?
> Is our DDK build environment still "supported" with this change?
>
>
> Thanks,
>
> / Hannes.

James
Wed Feb 09 18:12:38 CST 2005

Although it may be unwelcome work now to change your paths (eg, to use
underscores), it may be less trouble than what you may later run into by
changing the build process -- especially if someone other than you
encounters a problem.

--
James Antognini
Windows Driver Developer Support

This posting is provided "AS IS" with no warranties, and confers no rights.

"Hannes" <hannes@nospam.nospam> wrote in message
news:EFE15D19-6D6A-4276-AA31-98861AC172FF@microsoft.com...
> Hi,
>
>
> After converting our driver product build environment from VS.NET 2003
> (which compiler is not supported for drivers) into a DDK BUILD project
> (using
> a makefile project and ddkbuild.bat), I notice that all our build servers
> and
> most of our development stations no longer can build this driver, due to
> spaces in the build path.
>
> This post is suggesting a workaround to build paths with spaces:
> http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.development.device.drivers&mid=7a7b1ddb-8d6a-4502-86cc-609ad8870cb3&sloc=en-us
>
> Our driver is not using any Java. Which is safer?
> 1. Remove the $(MAKEDIR) as suggested in the above posting, or
> 2. Comment out this entire call to jvc (2 lines) as suggested in the above
> posting
>
> Also, can this harm our C/C++ driver?
> Is our DDK build environment still "supported" with this change?
>
>
> Thanks,
>
> / Hannes.

hannes
Thu Feb 10 10:59:04 CST 2005

I also have to answer this myself, as I found out that:

Even with the JVC change as suggested in the article above, the BUILD
process is still broken, in that that any build errors will be hidden from
output. In other words, "build" will fail at the linker stage (some *.obj
file will be missing) but there will be no output explaining why.

Any errors still get printed in the *.log and *.err files, but part of the
reason we're using DDKBUILD is that we want the output visible (and
browseable) in the VS output window.

So, I must now give up on the spaces.

Now only remains to convince the Draco.NET build server to use a different
build directory than c:\Documents and Settings\... which has those darn
spaces in it...


Thanks to everyone for your input.

/ Hannes.