Hi,
I have a script that scans the nightly build's output and filters
warnings according to some rules. The script got tripped last night
due to a change in a project's settings. After that, warnings didn't
have a
C:\Project\Module\src\File.cpp
path anymore, but only
..\..\src\File.cpp
(which seems to be the relative path from
C:\Project\Module\Project\VC8
where the module's project file "Module.vcproj" is located.) This has
the problem that it isn't enough for my script to find out the module's
name.
After analyzing yesterday's changes we found the culprit: With /Zi, we
get relative paths in warnings, with /ZI, we get absolute paths.
Is there a reason for this behaviour? Is there anything I can do about
it (besides setting /ZI which we would like to avoid as we suspect it
to make some linker bugs more likely)?
TIA,
Schobi
--
Sp******@gmx.de is never read
I'm HSchober at gmx dot de
"A patched buffer overflow doesn't mean that there's one less way attackers
can get into your system; it means that your design process was so lousy
that it permitted buffer overflows, and there are probably thousands more
lurking in your code."
Bruce Schneier
