To delete all the binary files generated while compiling a driver… We have to use “build -c” at the command window at our directory… But after doing this also still the “.ob,.res,.pdb” files exist still… How to delete all the binaries generated by the Win DDK at the command level…
build -c -0 will do much of what you want. build -clean will build the
“clean” target in your makefile, if only you had a makefile with a clean
target. You could have a makefile.inc with a clean target and that would
probably get built by build -clean. You could then have a custom make
operation for the clean target to delete all things you consider fair game.
I have not tried the build -clean option. What I do instead is have a top
level makefile for projects that builds wdk targets and visual studio
targets and anything else I need to build using whatever tools are
appropriate and has a ‘clean’ target for cleaning everything up. This
approach avoids having to deal with the obfuscation ontop of nmake known as
‘build’ for doing mundane makefile like things.
On Jan 4, 2008 1:55 AM, wrote:
> To delete all the binary files generated while compiling a driver… We
> have to use “build -c” at the command window at our directory… But after
> doing this also still the “.ob,.res,.pdb” files exist still… How to delete
> all the binaries generated by the Win DDK at the command level…
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Mark Roddy