The TARGET Group commands for ddkbuild have two parts, a DDK release part
and a platform target part. The DDK release part also as a corresponding
environment variable. A ddk release is one W2K XP WNET (W2k3) and LH
(Longhorn or Vista). A platform target is one of W2K, XP, WNET, LH plus
modifers such as 64bit and WDF. You have to specifiy the correct DDK, have
the correct environment variable set, and specify the correct platform
target.
In your case as you are using the WNET ddk (W2k3 SP1 to be precise) you need
to use -WNETW2K to build a W2K target and -WNETXP to build an XP target and
you need to have the WNETBASE environment variable set to to wherever you
have installed the w2k3sp1 ddk.
To repeat - you have to specify the correct ddk/target command and have the
correct environment variable locating that ddk set. The TARGET Group section
of the help page attempts to make this as clear as possible. “ddkbuild -h”
is your friend.
This platform/ddk complexity is a consequence of ddkbuild’s effort to
support multiple ddk releases and multiple platform targets. The goal (for
me internally at least) is to be able to use this tool across multiple
source control archived project and project releases. My archived project
releases build against specific versions of the ddk - consequently I need a
build tool that can deal with that.
I’m unlikely to do anything about the unicode path issue. If you want to
tackle this problem and provide a solution, please do and I will be happy to
include it in the next release.
=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of macro
Sent: Monday, April 24, 2006 11:31 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Why the DDKBUILD cant out the .sys?
Mark Roddy ??:
> Well first I would get my project out of a path name with
spaces in it
> as that is just asking for trouble.
>
> Second, are you sure that there is no .sys file? Like in
c:\documents
> and
> settings\administrator\eventshare\eventsys\objfre_wxp_x86\i386 ?
>
> Third. is there anything at all in that directory?
>
> Finally, when in doubt open a ddk shell window and build
the project
> from the command line. That is all ddkbuild is doing anyhow.
>
> =====================
> Mark Roddy DDK MVP
> Windows 2003/XP/2000 Consulting
> Hollis Technology Solutions 603-321-1032 www.hollistech.com
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of macro
>> Sent: Monday, April 24, 2006 9:37 PM
>> To: Windows System Software Devs Interest List
>> Subject: [ntdev] Why the DDKBUILD cant out the .sys?
>>
>> Develop Platform :Win 2000,vc6.0,ddk3790,ddkbuild3.13, I build my
>> test driver,but the output text display no errors,but the
.sys file
>> was’t builded.So anyone who encountered the same thing
please help
>> me!TKS!
>>
>> This is my build output text :
>> --------------------Configuration: eventsys - Win32
>> Release--------------------
>> DDKBUILD VERSION 3.13.36 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
>> Comments? Suggestions? xxxxx@hollistech.com DDKBUILD using
W2K DDK in
>> directory .
>> for free version basedir d:\WINDDK\3790 extension fre_wxp_x86
>> commandline: " build -e "
>> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang.
>> BUILD: Object root set to: ==> objfre_wxp_x86
>> BUILD: Compile and Link for i386
>> BUILD: Loading d:\WINDDK\3790\build.dat…
>> BUILD: Computing Include file dependencies:
>> BUILD: Examining c:\documents and
>> settings\administrator\eventshare\eventsys directory for files to
>> compile.
>> c:\documents and
settings\administrator????\eventshare\eventsys
>> c:\documents and
>> settings\administrator????\eventshare\eventsys -
>> 1 source files (553 lines)
>> BUILD: Compiling c:\documents and
>> settings\administrator\eventshare\eventsys directory Compiling -
>> objfre_wxp_x86\i386 for all platforms Compiling -
>> objfre_wxp_x86\i386 for all platforms Compiling -
>> objfre_wxp_x86\i386 for all platforms
>> BUILD: Linking c:\documents and
>> settings\administrator\eventshare\eventsys directory Compiling -
>> objfre_wxp_x86\i386 for all platforms Compiling -
>> objfre_wxp_x86\i386 for all platforms Compiling -
>> objfre_wxp_x86\i386 for all platforms
>> BUILD: Done
>> 3 files compiled
>> =============== build warnings ======================
>>
>>
>> build complete status 0
>>
>> eventsys.sys - 0 error(s), 0 warning(s)
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
>> http://www.osronline.com/article.cfm?id=256
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
Thank for you help,the problem has been done.Maybe others
have the same problem too.Now i explain the problem:
The problem is the Unicode Path Name.In my develop OSthe
language is Chinese,the most path is named by Chinese,so when
build driver with DDKBUILD,the path name cant resolve,the out
file will be failed.
But i have another doubt,if i use the ddkbuild -XP free .
command to build my driver will be failed,but use the
ddkbuild -W2K free . command will be successed.But in my
environment the XPBASE and W2KBASE has the same value is
d:\winddk\3790(ddk 3790 supprot 2000,xp,2003).So how can i
build my driver with multi platform in one develop OS(mine
WIN2000)?3ks
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online
at http://www.osronline.com/page.cfm?name=ListServer