Re: resource files
- From: "Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx>
- Date: Tue, 22 May 2007 17:04:59 +0400
might be silly
Why? For me, patching the production binaries _of your own_ is silly, if you
can rebuild.
Patching the binaries _of another parties_ is not silly, but possibly not legal
either :-)
Is there any rebuild command.I normally use build -cwZ.
For me, "build -c" is enough.
By the way one way of doing it(actually I am doing it in this way)
1.set a compilation flag in source file as you said.Depending upon that my
variables are set in the resource file.For this I need to have 2 source files
if I am right?
....or uncomment the entry in the single SOURCES file before full rebuild, or
set the environment variable.
Is there any other way of doing it.like after I build my driver if I run
some script or something the company name ,product name etc should be
changed.ie,when I right click my driver properties I should see 2 different
entries.
In SOURCES:
!IFDEF VERSION_B
C_DEFINES=$(C_DEFINES) -DVERSION_B
!ENDIF
In .RC file:
#ifdef VERSION_B
#else
#endif
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com
.
- Follow-Ups:
- Re: resource files
- From: qwert
- Re: resource files
- References:
- Re: resource files
- From: Maxim S. Shatskih
- Re: resource files
- Prev by Date: Re: usbser.sys -> "Device cannot start"
- Next by Date: Re: usbser.sys -> "Device cannot start"
- Previous by thread: Re: resource files
- Next by thread: Re: resource files
- Index(es):
Relevant Pages
|
