build question

I want to be able to build 2 libraries from a single directory. The
only difference between the 2 would be a single C preprocessor
identifier, defined in one version, undefined in the other.

I’ve been using 2 separate sources. files, one with an extra C_DEFINES=
line in it which defines the identifier in question.

Is there a way to do this from the build command line, and have a single
sources. file? Or some other way?

Thanks,
ScottR

If you do not need files from the directory above, consider creating two
subdirectories, and move a copy of sources and makefile into each. Replace
the existing sources/makefile with a dirs file for the two subdirs and have
the subdirs sources files do have the two conditions.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Robins, Scott” wrote in message
news:xxxxx@ntdev…
I want to be able to build 2 libraries from a single directory. The
only difference between the 2 would be a single C preprocessor
identifier, defined in one version, undefined in the other.

I’ve been using 2 separate sources. files, one with an extra C_DEFINES=
line in it which defines the identifier in question.

Is there a way to do this from the build command line, and have a single
sources. file? Or some other way?

Thanks,
ScottR

Hi,

Is there a way to do this from the build command line, and have a single
sources. file? Or some other way?
why not a simple CMD script that does the change in the file or inside an include to the sources file? I think the SOURCES files can have IFDEF blocks which refer to *environment* variables.

Alternatively consider ddkbuild.cmd and deposit a ddkprebld.cmd in the same folder, so as to have some pre-build step done. Or ddkbldenv.cmd to customize the environment before the DDK build tool gets called.

// Oliver


DDKWizard and DDKBUILD: http:</http:>