BLD1007 in the WDK

Gary_Little-2 · January 3, 2007, 1:00pm

Nearly all of my sources files include the line:

BROWSER_INFO=1

DDKBUILD and BUILD -ceFw produce a BLD1007 error when building. The kick in
the head is that there are no BLD errors defined in the WDK documentation
nor in VS 2005 (not really expected here). So the question becomes … how
to get rid of the frigging error and still produce browse files?

–
The personal opinion of
Gary G. Little

Scott_Noone_OSR · January 3, 2007, 1:10pm

It’s because verify.src gets included by default now (you can find all of
the BLD errors listed within that file)

It looks like defining

USER_ENV_BROWSER_INFO=1

In your SOURCES would fix the build warning, though I haven’t tried it to
find out if you still get the result you expect

-scott

–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Gary G. Little” wrote in message
news:xxxxx@ntdev…
> Nearly all of my sources files include the line:
>
> BROWSER_INFO=1
>
> DDKBUILD and BUILD -ceFw produce a BLD1007 error when building. The kick
> in the head is that there are no BLD errors defined in the WDK
> documentation nor in VS 2005 (not really expected here). So the question
> becomes … how to get rid of the frigging error and still produce browse
> files?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>

Gary_Little-2 · January 3, 2007, 1:39pm

Thanks Scott.

It 'coit’nly would help if there were some documentation on BUILD errors.

–
The personal opinion of
Gary G. Little

“Scott Noone” wrote in message news:xxxxx@ntdev…
> It’s because verify.src gets included by default now (you can find all of
> the BLD errors listed within that file)
>
> It looks like defining
>
> USER_ENV_BROWSER_INFO=1
>
> In your SOURCES would fix the build warning, though I haven’t tried it to
> find out if you still get the result you expect
>
> -scott
>
> –
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> “Gary G. Little” wrote in message
> news:xxxxx@ntdev…
>> Nearly all of my sources files include the line:
>>
>> BROWSER_INFO=1
>>
>> DDKBUILD and BUILD -ceFw produce a BLD1007 error when building. The kick
>> in the head is that there are no BLD errors defined in the WDK
>> documentation nor in VS 2005 (not really expected here). So the question
>> becomes … how to get rid of the frigging error and still produce browse
>> files?
>>
>> –
>> The personal opinion of
>> Gary G. Little
>>
>>
>>
>
>
>

Michal_Vodicka-2 · January 3, 2007, 8:06pm

It is documented in the verify.src file Scott mentioned

BROWSER_INFO shouldn’t be in the SOURCES file, it is an environment variable. I had it there for years, too. Then some DDK release started complaining about it (few years before IIRC) so I removed it. It makes sense if you think about it – you can have it set locally to have browser info available during development and still don’t generate these big files on the build machine.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Gary G. Little[SMTP:xxxxx@seagate.com]
Reply To: Windows System Software Devs Interest List
Sent: Wednesday, January 03, 2007 7:34 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] BLD1007 in the WDK

Thanks Scott.

It 'coit’nly would help if there were some documentation on BUILD errors.

–
The personal opinion of
Gary G. Little

“Scott Noone” wrote in message news:xxxxx@ntdev…
> > It’s because verify.src gets included by default now (you can find all of
> > the BLD errors listed within that file)
> >
> > It looks like defining
> >
> > USER_ENV_BROWSER_INFO=1
> >
> > In your SOURCES would fix the build warning, though I haven’t tried it to
> > find out if you still get the result you expect
> >
> > -scott
> >
> > –
> > Scott Noone
> > Software Engineer
> > OSR Open Systems Resources, Inc.
> > http://www.osronline.com
> >
> >
> > “Gary G. Little” wrote in message
> > news:xxxxx@ntdev…
> >> Nearly all of my sources files include the line:
> >>
> >> BROWSER_INFO=1
> >>
> >> DDKBUILD and BUILD -ceFw produce a BLD1007 error when building. The kick
> >> in the head is that there are no BLD errors defined in the WDK
> >> documentation nor in VS 2005 (not really expected here). So the question
> >> becomes … how to get rid of the frigging error and still produce browse
> >> files?
> >>
> >> –
> >> 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
>

OSR_Community_User · January 4, 2007, 10:09am

I disagree. If I want browser files I should be able to build them. Why
should the build process impose this policy on me? Also, making the
choice a global switch rather than sources based makes yet another
policy decision that affects my build processes when it really
shouldn’t. I might very well have some build targets that generate
browser files and some that don’t and all of them built under one build.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Wednesday, January 03, 2007 8:06 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BLD1007 in the WDK

It is documented in the verify.src file Scott mentioned

BROWSER_INFO shouldn’t be in the SOURCES file, it is an environment
variable. I had it there for years, too. Then some DDK release started
complaining about it (few years before IIRC) so I removed it. It makes
sense if you think about it – you can have it set locally to have
browser info available during development and still don’t generate these
big files on the build machine.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Gary G. Little[SMTP:xxxxx@seagate.com]
Reply To: Windows System Software Devs Interest List
Sent: Wednesday, January 03, 2007 7:34 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] BLD1007 in the WDK

Thanks Scott.

It 'coit’nly would help if there were some documentation on BUILD
errors.

–
The personal opinion of
Gary G. Little

“Scott Noone” wrote in message news:xxxxx@ntdev…
> > It’s because verify.src gets included by default now (you can find
all of
> > the BLD errors listed within that file)
> >
> > It looks like defining
> >
> > USER_ENV_BROWSER_INFO=1
> >
> > In your SOURCES would fix the build warning, though I haven’t tried
it to
> > find out if you still get the result you expect
> >
> > -scott
> >
> > –
> > Scott Noone
> > Software Engineer
> > OSR Open Systems Resources, Inc.
> > http://www.osronline.com
> >
> >
> > “Gary G. Little” wrote in message
> > news:xxxxx@ntdev…
> >> Nearly all of my sources files include the line:
> >>
> >> BROWSER_INFO=1
> >>
> >> DDKBUILD and BUILD -ceFw produce a BLD1007 error when building. The
kick
> >> in the head is that there are no BLD errors defined in the WDK
> >> documentation nor in VS 2005 (not really expected here). So the
question
> >> becomes … how to get rid of the frigging error and still produce
browse
> >> files?
> >>
> >> –
> >> 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

Michal_Vodicka-2 · January 4, 2007, 2:47pm

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, January 04, 2007 4:09 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] BLD1007 in the WDK

I disagree. If I want browser files I should be able to build them.

You are. Just “set BROWSER_INFO=1” before running build. Or do it from a batch starting build.exe.

Why should the build process impose this policy on me?

I took it as an advice You can still override it as Scott mentioned.

Also, making the
choice a global switch rather than sources based makes yet another
policy decision that affects my build processes when it really
shouldn’t. I might very well have some build targets that generate
browser files and some that don’t and all of them built under one build.

If you really need it, you can override it. I guess they wanted to handle common case when you want to create browser info for all or none build targets. Personally, I prefer environment variable change instead of SOURCES file change. This is especially important for automated build process which loads sources directly from SCM archives – any such a change would have to be checked in.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]