You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by Berin Lautenbach <be...@ozemail.com.au> on 2003/07/31 09:07:47 UTC

[Fwd: Re: Build problems]

Vincent,

One other thing - you might want to try

V1.0 RC1 at:

http://xml.apache.org/security/rc/

That supports Xerces 2.2 and 2.3.

It's not what will be released - I am waiting on Xalan 1.6 before I put 
out a final, but it might help you a bit.

Cheers,
	Berin


-------- Original Message --------
Subject: Re: Build problems
Date: Thu, 31 Jul 2003 17:03:52 +1000
From: Berin Lautenbach <be...@ozemail.com.au>
To: 'security-dev@xml.apache.org' <se...@xml.apache.org>
References: <98...@SOL>

Vincent,

Xerces 2.2 should be fine.

Could you try running xtest?  That uses HMAC with "secret" as a key to
run a few tests of the system.  You don't need to pass it anything.

What compiler are you using?  It almost looks like the C14n sample can't
find the xerces install?

You might also want to link in OpenSSL once you have everything
compiling - it's far more tested than the Windows Crypto API.

Cheers,
	Berin

Vincent Finn wrote:
> Hi,
> 
> I just downloaded the library and can't get all the projects (in particular
> the samples) with it to build
> 
> I have xerces 2.2 on the machine, 
> I assume this is the correct version since there were far more errors with
> 2.1 or 2.3 
> 
> I am building without Xalan or OpenSSL
> 
> I have put a few of the linker errors below and the compile error from the
> samples
> 
> only 3 projects build, xsec_lib, templatesign and xtest
> 
> I haven't tried actually running them yet since I haven't got a key to use
> yet
> 
> possibly these projects are irrelevant to me but I want to make sure
> 
> All I need to do is take a DOMDocument, sign it (the whole thing) and write
> it out
> and then take that file, verify it, decrypt it and get a DOMDocument
> 
> Anyone know what is wrong?
> and do I need to worry about it?
> 
> 	Thanks, Vin
> 
> c14n.obj : error LNK2001: unresolved external symbol "public: virtual void
> __thiscall xercesc_2_2::AbstractDOMParser::TextDecl(unsigned short const *
> const,unsigned short const * const)"
> (?TextDecl@AbstractDOMParser@xercesc_2_2@@UAEXQBG0@Z)
> c14n.obj : error LNK2001: unresolved external symbol "public: virtual void
> __thiscall xercesc_2_2::AbstractDOMParser::startExtSubset(void)"
> (?startExtSubset@AbstractDOMParser@xercesc_2_2@@UAEXXZ)
> c14n.obj : error LNK2001: unresolved external symbol "public: virtual void
> __thiscall xercesc_2_2::AbstractDOMParser::startIntSubset(void)"
> (?startIntSubset@AbstractDOMParser@xercesc_2_2@@UAEXXZ)
> c14n.obj : error LNK2001: unresolved external symbol "public: virtual void
> __thiscall xercesc_2_2::AbstractDOMParser::startAttList(class
> xercesc_2_2::DTDElementDecl const &)"
> (?startAttList@AbstractDOMParser@xercesc_2_2@@UAEXABVDTDElementDecl@2@@Z)
> 
> compile errors
> xml-security-0.2.0\src\samples\IOStreamOutputter.hpp(88): error C2061:
> syntax error : identifier 'XERCES_CPP_NAMESPACE_QUALIFIER'
> xml-security-0.2.0\src\samples\IOStreamOutputter.hpp(88): error C2805:
> binary 'operator <<' has too few parameters
>