Anyone having problems with C include file dependency checking with the
WDK RTM build 6000?
For some reason BUILD doesn’t seem to be checking include files
referenced via paths in the INCLUDES declaration in my sources file.
After believing for a while it must be a problem with my build tree
layout or SOURCES file I decided to try it with the DDK samples. I
believe I can reproduce this with the WDK samples as well. I picked the
1394 samples purely at random:
Environment>
CD src\1394
build -D -e
edit inc\1394api.h
build -D -e
I expect the change to 1394api.h to cause many files to be rebuilt but
they are not. Am I missing something in my SOURCES file or an argument
to BUILD? or is this a bug with WDK build 6000?
Best regards,
Andrew
–
Andrew Lee SolarFlare Communications
mailto:xxxxx@solarflare.com http://www.solarflare.com/
I fwd’ed this to the WDK team, everyone is gone this week so hopefully
we can hear something back next week
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, November 21, 2006 10:16 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Problem with dependency checking with WDK RTM build
6000
Andrew Lee wrote:
Anyone having problems with C include file dependency checking with
the WDK RTM build 6000?
For some reason BUILD doesn’t seem to be checking include files
referenced via paths in the INCLUDES declaration in my sources file.
After believing for a while it must be a problem with my build tree
layout or SOURCES file I decided to try it with the DDK samples. I
believe I can reproduce this with the WDK samples as well. I picked
the 1394 samples purely at random:
> Environment>
> CD src\1394
> build -D -e
>
> edit inc\1394api.h
>
> build -D -e
>
>
> I expect the change to 1394api.h to cause many files to be rebuilt but
> they are not. Am I missing something in my SOURCES file or an
> argument to BUILD? or is this a bug with WDK build 6000?
I can duplicate this, and it certainly looks like a build bug to me.
After building, 1394api.h isn’t listed in the 6000 build.dat, nor is the
1394\inc directory. When running the exact same test in
3790.1830\src\wdm\1394, 1394api.h IS present in build.dat, and touching
1394api.h triggers a rebuild.
This a very, very nasty problem. I do not need to have my confidence in
my tools shaken like this.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
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
Doron Holan wrote:
I fwd’ed this to the WDK team, everyone is gone this week so hopefully
we can hear something back next week
Doron,
Now that Thanksgiving is over have you heard anything from the WDK team
on this issue? I have reproduced the dependency checking issue with WDK
build 5600 (RC1), build 5744 (RC2) and build 6000 (RTM). Currently I’m
still using WDK build 6000 with ‘build -c -Z’ to force a full rebuild
each time, but this is a less than ideal workaround. Your help in
highlighting this particularly serious issue to the right people inside
Microsoft is appreciated.
Many thanks,
Andrew
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, November 21, 2006 10:16 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Problem with dependency checking with WDK RTM build
6000
Andrew Lee wrote:
> Anyone having problems with C include file dependency checking with
> the WDK RTM build 6000?
>
> For some reason BUILD doesn’t seem to be checking include files
> referenced via paths in the INCLUDES declaration in my sources file.
> After believing for a while it must be a problem with my build tree
> layout or SOURCES file I decided to try it with the DDK samples. I
> believe I can reproduce this with the WDK samples as well. I picked
> the 1394 samples purely at random:
>
> >> Environment>
>> CD src\1394
>> build -D -e
>>
>> edit inc\1394api.h
>>
>> build -D -e
>>
>>
>> I expect the change to 1394api.h to cause many files to be rebuilt but
>> they are not. Am I missing something in my SOURCES file or an
>> argument to BUILD? or is this a bug with WDK build 6000?
>
> I can duplicate this, and it certainly looks like a build bug to me.
> After building, 1394api.h isn’t listed in the 6000 build.dat, nor is the
> 1394\inc directory. When running the exact same test in
> 3790.1830\src\wdm\1394, 1394api.h IS present in build.dat, and touching
> 1394api.h triggers a rebuild.
>
> This a very, very nasty problem. I do not need to have my confidence in
> my tools shaken like this.
It is 9 am here ;), so no, I have not yet heard anything from the team.
I would give them a couple of days to respond and get out from under the
email backlog…
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Andrew Lee
Sent: Monday, November 27, 2006 9:02 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Problem with dependency checking with WDK RTM build
6000
Doron Holan wrote:
I fwd’ed this to the WDK team, everyone is gone this week so hopefully
we can hear something back next week
Doron,
Now that Thanksgiving is over have you heard anything from the WDK team
on this issue? I have reproduced the dependency checking issue with WDK
build 5600 (RC1), build 5744 (RC2) and build 6000 (RTM). Currently I’m
still using WDK build 6000 with ‘build -c -Z’ to force a full rebuild
each time, but this is a less than ideal workaround. Your help in
highlighting this particularly serious issue to the right people inside
Microsoft is appreciated.
Many thanks,
Andrew
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, November 21, 2006 10:16 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Problem with dependency checking with WDK RTM
build
6000
Andrew Lee wrote:
> Anyone having problems with C include file dependency checking with
> the WDK RTM build 6000?
>
> For some reason BUILD doesn’t seem to be checking include files
> referenced via paths in the INCLUDES declaration in my sources file.
> After believing for a while it must be a problem with my build tree
> layout or SOURCES file I decided to try it with the DDK samples. I
> believe I can reproduce this with the WDK samples as well. I picked
> the 1394 samples purely at random:
>
> Build
>> Environment>
>> CD src\1394
>> build -D -e
>>
>> edit inc\1394api.h
>>
>> build -D -e
>>
>>
>> I expect the change to 1394api.h to cause many files to be rebuilt
but
>> they are not. Am I missing something in my SOURCES file or an
>> argument to BUILD? or is this a bug with WDK build 6000?
>
> I can duplicate this, and it certainly looks like a build bug to me.
> After building, 1394api.h isn’t listed in the 6000 build.dat, nor is
the
> 1394\inc directory. When running the exact same test in
> 3790.1830\src\wdm\1394, 1394api.h IS present in build.dat, and
touching
> 1394api.h triggers a rebuild.
>
> This a very, very nasty problem. I do not need to have my confidence
in
> my tools shaken like this.
—
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