obj_path when using BUILD in WDK 6000

NTDEV
1

I looked and searcehd, but I can find nothing on this … well … I find a
hell of a lot of meaningless jargon about managed code and things not
DDK/WDK/driver centric, in the WDK documentation. This is a project SOURCES
file that works when built using the 3790.1830 DDK for a Server 2003 driver.
The WDK build produces obj and lib files as per the DDK build but these
niggling red lines bother me and I’d like to understand how to eleminate
them. How have the sources files for KMDF101 changed for 6000?

“errors in directory c:\projects<path>
obj_path is set for you. You may not set it.”
–
The personal opinion of
Gary G. Little

2

Are you calling set_wdf_env.bat in your build env under the WDK? If so,
that is the problem. This batch file should not be run under the WDK
build env b/c KMDF is fully integrated into the kit

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Wednesday, December 06, 2006 2:19 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] obj_path when using BUILD in WDK 6000

I looked and searcehd, but I can find nothing on this … well … I
find a
hell of a lot of meaningless jargon about managed code and things not
DDK/WDK/driver centric, in the WDK documentation. This is a project
SOURCES
file that works when built using the 3790.1830 DDK for a Server 2003
driver.
The WDK build produces obj and lib files as per the DDK build but these
niggling red lines bother me and I’d like to understand how to eleminate

them. How have the sources files for KMDF101 changed for 6000?

“errors in directory c:\projects<path>
obj_path is set for you. You may not set it.”
–
The personal opinion of
Gary G. Little

—
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

3

Doron Holan wrote:

Are you calling set_wdf_env.bat in your build env under the WDK? If so,
that is the problem. This batch file should not be run under the WDK
build env b/c KMDF is fully integrated into the kit

There’s one other thing as well. The unintegrated KMDF examples had
this line in their “sources” files:

!include $(WDF_ROOT)\project.mk

If you use that “sources” file with the WDK, it will cause the problem
the OP described. If you are switching to the WDK permanently, you can
remove that line. I added the following, to let it work with either:

!ifdef WDF_ROOT
!include $(WDF_ROOT)\project.mk
!endif

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

4

Ah ha … thanks guys.

It’s a porting problem, in that shortly we should be moving everything to
the WDK, but still building for Server 2003 drivers. Once I, as the guinea
pig, have figured it all out, we can then move everyone to the WDK, kicking,
screaming and grumbling.

–
The personal opinion of
Gary G. Little

“Tim Roberts” wrote in message news:xxxxx@ntdev…
> Doron Holan wrote:
>> Are you calling set_wdf_env.bat in your build env under the WDK? If so,
>> that is the problem. This batch file should not be run under the WDK
>> build env b/c KMDF is fully integrated into the kit
>>
>
>
> There’s one other thing as well. The unintegrated KMDF examples had
> this line in their “sources” files:
>
> !include $(WDF_ROOT)\project.mk
>
> If you use that “sources” file with the WDK, it will cause the problem
> the OP described. If you are switching to the WDK permanently, you can
> remove that line. I added the following, to let it work with either:
>
> !ifdef WDF_ROOT
> !include $(WDF_ROOT)\project.mk
> !endif
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>

5

Doron,

My first shot was to simply start the Server 2003 checked build environment
for the WDK, so it that batch file was run it was run as part of the 6000
set up for that environment. I’m just at the beginning of the port so I’m
not even using Mark’s DDKBUILD, which does not look to be functional either.

I modified one source file per Tem’s recommanedation and then deleted the
WDF_DDK variable from the environment and ran BLD again with the same
results. Cuious’r and curious’r.

–
The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
Are you calling set_wdf_env.bat in your build env under the WDK? If so,
that is the problem. This batch file should not be run under the WDK
build env b/c KMDF is fully integrated into the kit

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Wednesday, December 06, 2006 2:19 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] obj_path when using BUILD in WDK 6000

I looked and searcehd, but I can find nothing on this … well … I
find a
hell of a lot of meaningless jargon about managed code and things not
DDK/WDK/driver centric, in the WDK documentation. This is a project
SOURCES
file that works when built using the 3790.1830 DDK for a Server 2003
driver.
The WDK build produces obj and lib files as per the DDK build but these
niggling red lines bother me and I’d like to understand how to eleminate

them. How have the sources files for KMDF101 changed for 6000?

“errors in directory c:\projects<path>
obj_path is set for you. You may not set it.”
–
The personal opinion of
Gary G. Little

—
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

6

DDKBUILD works fine with the WDK.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Thursday, December 07, 2006 10:39 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] obj_path when using BUILD in WDK 6000

Doron,

My first shot was to simply start the Server 2003 checked build
environment
for the WDK, so it that batch file was run it was run as part of the
6000
set up for that environment. I’m just at the beginning of the port so
I’m
not even using Mark’s DDKBUILD, which does not look to be functional
either.

I modified one source file per Tem’s recommanedation and then deleted
the
WDF_DDK variable from the environment and ran BLD again with the same
results. Cuious’r and curious’r.

–
The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
Are you calling set_wdf_env.bat in your build env under the WDK? If so,
that is the problem. This batch file should not be run under the WDK
build env b/c KMDF is fully integrated into the kit

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Wednesday, December 06, 2006 2:19 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] obj_path when using BUILD in WDK 6000

I looked and searcehd, but I can find nothing on this … well … I
find a
hell of a lot of meaningless jargon about managed code and things not
DDK/WDK/driver centric, in the WDK documentation. This is a project
SOURCES
file that works when built using the 3790.1830 DDK for a Server 2003
driver.
The WDK build produces obj and lib files as per the DDK build but these
niggling red lines bother me and I’d like to understand how to eleminate

them. How have the sources files for KMDF101 changed for 6000?

“errors in directory c:\projects<path>
obj_path is set for you. You may not set it.”
–
The personal opinion of
Gary G. Little

—
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

—
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

7

Gary G. Little wrote:

Doron,

My first shot was to simply start the Server 2003 checked build environment
for the WDK, so it that batch file was run it was run as part of the 6000
set up for that environment. I’m just at the beginning of the port so I’m
not even using Mark’s DDKBUILD, which does not look to be functional either.

I modified one source file per Tem’s recommanedation and then deleted the
WDF_DDK variable from the environment and ran BLD again with the same
results. Cuious’r and curious’r.

Really? With that one change in my “sources” file, I can start a
3790.1830 environment, run “set_wdf_env.cmd”, and then run build, OR I
can start a 6000 environment, and run build. Both work.

I don’t know what the WDF_DDK variable is. Do you mean WDF_ROOT? That
should only be defined if you ran “set_wdf_env.cmd”, which you do not
want to do with the 6000 DDK.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

8

Mark — assumptions on my part … apologies rendered.

Tim — oh yuck … I was writing that on the fly, and it appears my memory
fades faster than my hair is turning gray and falling out. We use WDF_DDK as
an internal var.

–
The personal opinion of
Gary G. Little

9

Mark — assumptions on my part … apologies rendered.

Tim — oh yuck … I was writing that on the fly, and it appears my memory
fades faster than my hair is turning gray and falling out. We use WDF_DDK as
an internal var.

–
The personal opinion of
Gary G. Little