It may not be listed in the help, but /pdbcompress is a valid switch, at
least with the 7.10.4035 linker in the 3790.1830 DDK (Win 2003 SP1).
The real question is why anybody should care whether the PDB is
compressed or not. The OP never said what kind of problem they were
having.
You can’t remove standard switches from LINKER_FLAGS in sources, but you
can do it from makefile.inc. For example:
LINKER_FLAGS=$(LINKER_FLAGS:/pdbcompress=)
This should be considered build system hackery, and there is no
guarantee that it will work in future DDK’s. I’d recommend to the OP
that they identify and solve their underlying problem, because
compressed PDB files shouldn’t be an issue.
-----Original Message-----
From: Gary G. Little
Sent: Wednesday, May 25, 2005 10:20 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] “build” compresses pdb files
I went exploring on my own system, and do not find /PDBCOMPRESSED. In
the
linker for Visual Studios .NET 2003 I find :
/PDB:{filename|NONE}
/PDBTYPE:{CON[SOLIDATE]|SEPT[YPES]}
, but no /PDBCOMPRESSED. In Whidbey and in the DDK linker I find:
/PDB:filename
/PDBSTRIPPED:filename
Again no /PDBCOMPRESSED.
So the question becomes what linker are you using to build your driver?
–
The personal opinion of
Gary G. Little
“Shahar Talmi” wrote in message news:xxxxx@ntdev…
> Hi,
> I noticed that one of the options “build” passes to the linker by
default
> is
> “/pdbcompress”.
> This linker option is not documented anywhere as far as I can tell,
but it
> seems that it causes the pdb file to be compressed if created on a
NTFS
> volume.
> I tried adding “LINKER_FLAGS=/pdbcompress:no” to my sources file to
revert
> this (it was just a guess, I figured it might be like /incremental and
> /incremental:no), but it didn’t help…
> How can I prevent the linker from compressing this file?
>
> Thanks,
> Shahar