_CL_ settings in DDK's setenv.bat

Wondering if anyone can shed some lights about these explicit settings in
the DDK’s setenv.bat (3790):

set ML=/Zvc6
set CL=/Ztmp
set LINK=/Tmp

There seems to be no documentation of any of them anywhere, and the only
reference appears to be in “i386mk.inc” in the entire DDK. I believe they
have stayed like that for a while.

It gives a warning (warning D4002 : ignoring unknown option ‘/Ztmp’) for
each and every single user-mode component that I build with PREfast.

Therefore I’ve come to a point that I’d like to understand better the intent
behind these settings and what to do to get rid of the warning without
introducing problems down the road (yep, I cannot bear with any dust in the
code, and am living in a glass house :sunglasses:

Thanks in advance for any insight. Apologize if this is a wrong forum for
the question, or if it was answered before (I did look left and right before
the post).

Regards,
-Brian

These have been removed from Windows Server 2003 Service Pack 1 DDK and
the Windows Longhorn kit.

They were originally added to support building VC6 style debug
information that windbg required at that time. This is no longer
necessary.

Thanks,
Richard Moore
WDK Team

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian
Sent: Monday, March 14, 2005 10:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] CL settings in DDK’s setenv.bat

Wondering if anyone can shed some lights about these explicit settings
in
the DDK’s setenv.bat (3790):

set ML=/Zvc6
set CL=/Ztmp
set LINK=/Tmp

There seems to be no documentation of any of them anywhere, and the only
reference appears to be in “i386mk.inc” in the entire DDK. I believe
they
have stayed like that for a while.

It gives a warning (warning D4002 : ignoring unknown option ‘/Ztmp’) for
each and every single user-mode component that I build with PREfast.

Therefore I’ve come to a point that I’d like to understand better the
intent
behind these settings and what to do to get rid of the warning without
introducing problems down the road (yep, I cannot bear with any dust in
the
code, and am living in a glass house :sunglasses:

Thanks in advance for any insight. Apologize if this is a wrong forum
for
the question, or if it was answered before (I did look left and right
before
the post).

Regards,
-Brian


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Richard, thanks much for the response.

While we’re at this, is there any way to work around the PREfast warnings,
with the plain, old WS03 DDK?? I don’t get to change our build
environments, not that easily.

I tried a few approaches, and none prevails.

While I understand those warnings are harmless, I do like to get rid of them
if there is a way. Thanks in advance, again.
-Brian

----- Original Message -----
From: “Richard Moore (DDK)”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 15, 2005 12:50
Subject: RE: CL settings in DDK’s setenv.bat

These have been removed from Windows Server 2003 Service Pack 1 DDK and
the Windows Longhorn kit.

They were originally added to support building VC6 style debug
information that windbg required at that time. This is no longer
necessary.

Thanks,
Richard Moore
WDK Team

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian
Sent: Monday, March 14, 2005 10:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] CL settings in DDK’s setenv.bat

Wondering if anyone can shed some lights about these explicit settings
in
the DDK’s setenv.bat (3790):

set ML=/Zvc6
set CL=/Ztmp
set LINK=/Tmp

There seems to be no documentation of any of them anywhere, and the only
reference appears to be in “i386mk.inc” in the entire DDK. I believe
they
have stayed like that for a while.

It gives a warning (warning D4002 : ignoring unknown option ‘/Ztmp’) for
each and every single user-mode component that I build with PREfast.

Therefore I’ve come to a point that I’d like to understand better the
intent
behind these settings and what to do to get rid of the warning without
introducing problems down the road (yep, I cannot bear with any dust in
the
code, and am living in a glass house :sunglasses:

Thanks in advance for any insight. Apologize if this is a wrong forum
for
the question, or if it was answered before (I did look left and right
before
the post).

Regards,
-Brian


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Brian - look into the use of PREfast filters, (search the PREfast User
Guide for detailed information).

Here’s a couple of filter commands you can try:
prefast /filterpreset=winpft view
prefast /filterpreset=winpft list

WINPFT Preset
PREfast includes the WINPFT preset, which filters messages that may not
be relevant. The WINPFT filter preset is identical to the WSPMIN filter
preset.

This applies the WINPFT preset at the time of your PREfast run. The
result is a log file containing all defects found during the run and a
message list showing only those defects not filtered out by the WINPFT
preset.

Note that the /filterpreset option limits your view to the target issues
in the following section. You can omit this switch to view more errors.

Thanks,
Richard Moore
WDK Team

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian
Sent: Tuesday, March 15, 2005 6:10 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] CL settings in DDK’s setenv.bat

Richard, thanks much for the response.

While we’re at this, is there any way to work around the PREfast
warnings,
with the plain, old WS03 DDK?? I don’t get to change our build
environments, not that easily.

I tried a few approaches, and none prevails.

While I understand those warnings are harmless, I do like to get rid of
them
if there is a way. Thanks in advance, again.
-Brian

----- Original Message -----
From: “Richard Moore (DDK)”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 15, 2005 12:50
Subject: RE: CL settings in DDK’s setenv.bat

These have been removed from Windows Server 2003 Service Pack 1 DDK and
the Windows Longhorn kit.

They were originally added to support building VC6 style debug
information that windbg required at that time. This is no longer
necessary.

Thanks,
Richard Moore
WDK Team

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian
Sent: Monday, March 14, 2005 10:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] CL settings in DDK’s setenv.bat

Wondering if anyone can shed some lights about these explicit settings
in
the DDK’s setenv.bat (3790):

set ML=/Zvc6
set CL=/Ztmp
set LINK=/Tmp

There seems to be no documentation of any of them anywhere, and the only
reference appears to be in “i386mk.inc” in the entire DDK. I believe
they
have stayed like that for a while.

It gives a warning (warning D4002 : ignoring unknown option ‘/Ztmp’) for
each and every single user-mode component that I build with PREfast.

Therefore I’ve come to a point that I’d like to understand better the
intent
behind these settings and what to do to get rid of the warning without
introducing problems down the road (yep, I cannot bear with any dust in
the
code, and am living in a glass house :sunglasses:

Thanks in advance for any insight. Apologize if this is a wrong forum
for
the question, or if it was answered before (I did look left and right
before
the post).

Regards,
-Brian


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

“Richard Moore (DDK)” wrote in message
news:xxxxx@ntdev…
>
> Here’s a couple of filter commands you can try:
> prefast /filterpreset=winpft view
> prefast /filterpreset=winpft list

Hi Richard,

The “/filterpreset” switch only applies in filtering the messages for
viewing or listing; it does not seem to get rid of any of the build warnings
(D4002) from the build*.wrn. Any other idea? Or am I missing something
obvious?

Thanks,
-Brian

Hi Brian - there is currently no other option available to suppress
build warnings from PREfast.

Thanks,
Richard

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian
Sent: Thursday, March 17, 2005 7:18 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] CL settings in DDK’s setenv.bat

“Richard Moore (DDK)” wrote in message
news:xxxxx@ntdev…
>
> Here’s a couple of filter commands you can try:
> prefast /filterpreset=winpft view
> prefast /filterpreset=winpft list

Hi Richard,

The “/filterpreset” switch only applies in filtering the messages for
viewing or listing; it does not seem to get rid of any of the build
warnings
(D4002) from the build*.wrn. Any other idea? Or am I missing something
obvious?

Thanks,
-Brian


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com