You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Scott Cantor (JIRA)" <ji...@apache.org> on 2012/11/05 16:50:13 UTC
[jira] [Resolved] (SANTUARIO-348) Project for visual studio 2003
(v7.0) is missed source file
[ https://issues.apache.org/jira/browse/SANTUARIO-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor resolved SANTUARIO-348.
------------------------------------
Resolution: Won't Fix
Assignee: Scott Cantor (was: Colm O hEigeartaigh)
It's missing much more than just that one file. All of the older project files are stale, and I will not be maintaining them because I do not build, test, or support the code on the older compiler platforms. If there are contributors that wish to maintain those files and builds, they would need to commit to doing so on an ongoing basis.
The only reason I didn't pull the old project files was to let people using them keep doing what they might want to do with less hassle.
> Project for visual studio 2003 (v7.0) is missed source file
> -----------------------------------------------------------
>
> Key: SANTUARIO-348
> URL: https://issues.apache.org/jira/browse/SANTUARIO-348
> Project: Santuario
> Issue Type: Bug
> Affects Versions: C++ 1.6.0, C++ 1.7.0
> Reporter: Nguyen Tran Nhan
> Assignee: Scott Cantor
> Labels: compile-error
>
> Symptom:
> Compile Santuario with visual studio 2003 occurred bellow error:
> Linking...
> Creating library ../../../../Build/Win32/VC7/Release/xsec_1.lib and object ../../../../Build/Win32/VC7/Release/xsec_1.exp
> DSIGKeyInfoList.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall DSIGKeyInfoDEREncoded::load(void)" (?load@DSIGKeyInfoDEREncoded@@UAEXXZ)
> XSECKeyInfoResolverDefault.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall DSIGKeyInfoDEREncoded::load(void)" (?load@DSIGKeyInfoDEREncoded@@UAEXXZ)
> DSIGKeyInfoList.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall DSIGKeyInfoDEREncoded::~DSIGKeyInfoDEREncoded(void)" (??1DSIGKeyInfoDEREncoded@@UAE@XZ) referenced in function "public: virtual void * __thiscall DSIGKeyInfoDEREncoded::`scalar deleting destructor'(unsigned int)" (??_GDSIGKeyInfoDEREncoded@@UAEPAXI@Z)
> XSECKeyInfoResolverDefault.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall DSIGKeyInfoDEREncoded::~DSIGKeyInfoDEREncoded(void)" (??1DSIGKeyInfoDEREncoded@@UAE@XZ)
> DSIGKeyInfoList.obj : error LNK2019: unresolved external symbol "public: __thiscall DSIGKeyInfoDEREncoded::DSIGKeyInfoDEREncoded(class XSECEnv const *,class xercesc_2_7::DOMNode *)" (??0DSIGKeyInfoDEREncoded@@QAE@PBVXSECEnv@@PAVDOMNode@xercesc_2_7@@@Z) referenced in function $L53993
> DSIGKeyInfoList.obj : error LNK2019: unresolved external symbol "public: class xercesc_2_7::DOMElement * __thiscall DSIGKeyInfoDEREncoded::createBlankDEREncoded(unsigned short const *)" (?createBlankDEREncoded@DSIGKeyInfoDEREncoded@@QAEPAVDOMElement@xercesc_2_7@@PBG@Z) referenced in function "public: class DSIGKeyInfoDEREncoded * __thiscall DSIGKeyInfoList::appendDEREncoded(unsigned short const *)" (?appendDEREncoded@DSIGKeyInfoList@@QAEPAVDSIGKeyInfoDEREncoded@@PBG@Z)
> DSIGKeyInfoList.obj : error LNK2019: unresolved external symbol "public: __thiscall DSIGKeyInfoDEREncoded::DSIGKeyInfoDEREncoded(class XSECEnv const *)" (??0DSIGKeyInfoDEREncoded@@QAE@PBVXSECEnv@@@Z) referenced in function "public: class DSIGKeyInfoDEREncoded * __thiscall DSIGKeyInfoList::appendDEREncoded(unsigned short const *)" (?appendDEREncoded@DSIGKeyInfoList@@QAEPAVDSIGKeyInfoDEREncoded@@PBG@Z)
> ../../../../Build/Win32/VC7/Release/xsec_1_6.dll : fatal error LNK1120: 5 unresolved externals
> Root Cause:
> In section xsec->dsig is missed include file DSIGKeyInfoDEREncoded.cpp
> How to fix:
> add file DSIGKeyInfoDEREncoded.cpp into project dsig.
> <File
> RelativePath="..\..\..\..\xsec\dsig\DSIGKeyInfoDEREncoded.cpp">
> </File>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira