Could you please try to get xmlsec from svn and run ./autogen.sh
instead of ./configure? It sounds like the autoconf/automake packages
are not configuring xmlsec on your system correctly. ./autogen.sh
should force the update.
Aleksey
Nolan Hurlburt wrote:
Hi list,
I ran into a bit of a problem
Hi list,
I ran into a bit of a problem recently using the xmlsec library today on
a Linux x86_64 box. Here’s the situation:
1) The xmlsec library was compiled using the standard configure, make. (
--enable-debugging, --with-libxlst=no )
2) A piece of code that signs an xml doc was compiled an
I made this defines!
-Original Message-
From: Aleksey Sanin [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 20. März 2007 15:42
To: Jürgen Heiss
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] Static compile
https://www.aleksey.com/xmlsec/api/xmlsec-notes-compiling-windows.html
#define LIBXML
https://www.aleksey.com/xmlsec/api/xmlsec-notes-compiling-windows.html
#define LIBXML_STATIC
#define LIBXSLT_STATIC
#define XMLSEC_STATIC
Aleksey
Jürgen Heiss wrote:
Hi Aleksey,
Hi,
I compiled libxml2, libxslt, xmlsec, and the openssl crypto Libary as
Multithread Dll and static.
This w
Hi Aleksey,
Hi,
I compiled libxml2, libxslt, xmlsec, and the openssl crypto Libary as
Multithread Dll and static.
This works fine, but when I try to load the library into my application I got
the following link errors.
xmlsec.obj : error LNK2001: unresolved external symbol __imp__xmlFree
xm
