[EMAIL PROTECTED] wrote:
Hi Dave,
Thank you once again for your helpful reply.
>>
>> I have, as suggested, created a trivial program that illustrates the
>> problem.
>> It is based on the XalanTransfrom example with minimal changes.
>> It is attached.
>>
>> Hopefully it shows where I am
Antonio Scotti wrote:
Here is what I do:
void doXpath(xercesc_2_7::DOMElement* theElem, xercesc_2_7::DOMDocument*
theDoc)
{
XALAN_CPP_NAMESPACE::XercesDocumentWrapper* theWrapper;
XALAN_CPP_NAMESPACE::XercesDOMSupport* theDOMSupport;
XALAN_CPP_NAMESPACE::XercesParserLiaison* theParserLiaison
Hi Dave,
Thank you once again for your helpful
reply.
>>
>> I have, as suggested, created a trivial program
that illustrates the
>> problem.
>> It is based on the XalanTransfrom example
with minimal changes.
>> It is attached.
>>
>> Hopefully it shows where I am going wrong.
>> Maybe the prob
Here is what I do:
void doXpath(xercesc_2_7::DOMElement* theElem, xercesc_2_7::DOMDocument*
theDoc)
{
XALAN_CPP_NAMESPACE::XercesDocumentWrapper* theWrapper;
XALAN_CPP_NAMESPACE::XercesDOMSupport* theDOMSupport;
XALAN_CPP_NAMESPACE::XercesParserLiaison* theParserLiaison;
const XALAN_CPP_NAMES
Thank you David.
Yes I just added these to my PATH environment variable (in XP), to find
the Xerces DLL's, and both release and debug builds from trunk svn were
successful in VS2005.
F:\projects\xerces-c\trunk\Build\Win32\VC8\Release;F:\projects\xerces-c\trunk\Build\Win32\VC8\Debug
Che