DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
b=YviVUDllCmIOofAK/qEW5h1eb+Cl/wceY2c+83dGjiUGxn2faV5gvTayoOo2UzYDcX0pGqXGuTNM1f0+WmVSYASAMrMGb61YBFdEugAmcNjAbcck+pM4g5kXOVsisi0w82gK5T4N8bSpE4Eo4V8EAqyDGoeKL6fNtXxjZ5hnHKM=
Date: Mon, 21 Nov 2005 15:21:02 -0500
From: "Zenko Klapko Jr." <[EMAIL PROTECTED]>
To: Alberto Massari <[EMAIL PROTECTED]>
Subject: Re: xerces-c 2.7.0
X-Mlf-Threat: nothreat
X-Mlf-Threat-Detailed: nothreat;none;none
X-OriginalArrivalTime: 21 Nov 2005 20:21:03.0272 (UTC)
FILETIME=[1849A280:01C5EED9]
Hi Alberto,
My friend figured it out. Besides the custom compiling and adding
the include/lib paths in Visual Studio I had to type in the name of
the library on the additional dependencies line. I've setup several
outside libraries in the past with VS (openGL and SDL) and I don't
remember ever having to specify the library name. Looking over the
documentation for "installing & building" I guess it's inferred to
do that, but for someone who has never used Xerces before it was
confusing to setup. I'm going to get more involved, at least long
enough so that I can update tho documentation to make it more clear
as what needs to be done.
Thanks for the response,
-Zenko
On 11/21/05, Alberto Massari
<<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]> wrote:
Hi Zenko,
At 12.25 20/11/2005 -0500, Zenko Klapko Jr. wrote:
>Hi Alberto,
>
>I saw your posts on the xerces-c users list. It looks like you spent
>a lot of time working with xerces-c and visual studio.
You're better off if you directly use the mailing lists, instead of
sending private e-mails, so that your request reaches a wider audience .
>I'm using MSVC7.1, I've downloaded the latest source and compiled
>the debug & release versions of the libraries and dll. Both are
>moved into directories that Visual Studio can see. When I try and
>build the sample PrintDOM I get a bunch of linking errors:
>Linking...
>DOMPrint.obj : error LNK2001: unresolved external symbol "public:
>virtual void __thiscall
>xercesc_2_7::StdOutFormatTarget::flush(void)"
>([EMAIL PROTECTED]@xercesc_2_7@@UAEXXZ)
That's the first time I hear that a sample program doesn't compile;
have you changed something in the build process? When you say "moved
into directories that Visual Studio can see", do you refer to a step
you performed?
Alberto
>and it continues.
>
>I've read through the documentation, the FAQs, and now the mailing
>lists looking for this. You're plight comes close and hopefully with
>your experience you will provide the insight needed. I am willing to
>update the documentation to reflect the additional steps that a user
>may need to go through if there setup is slightly different from the
>one supplied.
>
>Thanks in advance,
>Zenko
