PDB File for VC 9 Static 64-bit library (Debug variant) has the name 
xerceslib_vc80.pdb
---------------------------------------------------------------------------------------

                 Key: XERCESC-1869
                 URL: https://issues.apache.org/jira/browse/XERCESC-1869
             Project: Xerces-C++
          Issue Type: Bug
          Components: Build
    Affects Versions: 3.0.1
         Environment: Windows, Visual Studio 2008
            Reporter: Robert Krajewski
            Priority: Minor


The Statuc Debug confguration of the XercesLib project for the Win64 platform 
creates a PDB file named xerceslib_vc80.pdb, when it should be called 
xerceslib_vc90.pdb.

It's not blocking because the linker doesn't really care what the name of the 
associated PDB file of static library is called (the .lib file will have a 
reference to the name), but it would be good idea to make sure then name make 
sense to people.

The Win32 VC 9 PDB file has the correct name.

When I've built the Static Debug and Release versions under VC 7, VC 8, and VC 
9, here are the PDB files:

[...@qa71 sbdepbuild]$ find /var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1 -name 
'*.pdb'
/var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1/Build/Win32/VC7.1/Static 
Debug/xerceslib_vc71d.pdb
/var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1/Build/Win32/VC7.1/Static 
Release/xerceslib_vc71.pdb
/var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1/Build/Win32/VC8/Static 
Debug/obj/XercesLib/xerceslib_vc80.pdb
/var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1/Build/Win32/VC9/Static 
Debug/obj/XercesLib/xerceslib_vc90.pdb
/var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1/Build/Win64/VC8/Static 
Debug/obj/XercesLib/xerceslib_vc80.pdb
/var/tmp/sbbuild-rpk/xercesc/xerces-c-3.0.1/Build/Win64/VC9/Static 
Debug/obj/XercesLib/xerceslib_vc80.pdb

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to