Re: Build device driver using Microsoft Visual C++ 2005
- From: "Gary G. Little" <gary.g.little@xxxxxxxxxxx>
- Date: Mon, 5 Jun 2006 09:51:34 -0500
You say you are building your driver with VS 2005, but precisely how are you
doing that? Are you using VS to edit and maintain you sources and projects,
and then either using DDKBUILD or a DDK command line environment to actually
build your driver? Or are you really invoking an IDE build and using the VS
compilers? If the latter ... DON'T ... it's the wrong compiler to be using
for device drivers.
Now, having said that, to generate PDB files, all you need to do is invoke a
checked build environment and run BLD or BUILD -cze, or your switches of
choice, or use DDKBUILD from a VS makefile project.
--
The personal opinion of
Gary G. Little
"mirage2k2" <mirage2k2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E74AE9F6-9D92-4313-B268-AD3484C8112F@xxxxxxxxxxxxxxxx
I've just started building my driver using Microsoft Visual C++ 2005. I
notice the .pdb generated by the newer compiler/linker is different to the
one v6 generated. For a start I had to upgrade WinDbg to the latest
version
in order for it to correctly get all symbols from the .pdb. Now I have
problems with softice ... it too has trouble with the newer .pdb.
Does anyone know what has changed with respect to .pdb? Does anyone know
how to get the new compiler/linker to output a .pdb like v6 did?
.
- Prev by Date: Re: Installing NDIS intermediate without admin rights
- Next by Date: Vista Beta 2 won't install my printer driver
- Previous by thread: Redirector Question
- Next by thread: Re: Build device driver using Microsoft Visual C++ 2005
- Index(es):
Relevant Pages
|
