Got it thanks.  Everything is compiling now and working great.

On Sat, Oct 5, 2013 at 5:04 AM, Alberto Massari
<[email protected]>wrote:

> You need to manually include to the Visual Studio project the files in the
> folder src\xercesc\util\NetAccessors\**Curl
>
> Alberto
>
> Il 05/10/13 00:37, Travis Loyd ha scritto:
>
>  Hello,
>>
>> I've been able to load up the project in Visual Studio 2010 & change the
>> Preprocessor definition from XERCES_USE_NETACCESSOR_WINSOCK
>> to XERCES_USE_NETACCESSOR_CURL.
>>
>> Building has the following result:
>>
>> 1>------ Build started: Project: XercesLib, Configuration: Debug Win32
>> ------
>> 1>     Creating library
>> .\..\..\..\..\..\Build\Win32\**VC10\Debug\xerces-c_3D.lib and object
>> .\..\..\..\..\..\Build\Win32\**VC10\Debug\xerces-c_3D.exp
>> 1>PlatformUtils.obj : error LNK2001: unresolved external symbol "private:
>> static wchar_t const * const xercesc_3_1::CurlNetAccessor::**fgMyName"
>> (?fgMyName@CurlNetAccessor@**xercesc_3_1@@0QB_WB)
>> 1>PlatformUtils.obj : error LNK2019: unresolved external symbol "public:
>> __thiscall xercesc_3_1::CurlNetAccessor::**CurlNetAccessor(void)"
>> (??0CurlNetAccessor@xercesc_3_**1@@QAE@XZ) referenced in function
>> "private:
>> static class xercesc_3_1::XMLNetAccessor * __cdecl
>> xercesc_3_1::XMLPlatformUtils:**:makeNetAccessor(void)"
>> (?makeNetAccessor@**XMLPlatformUtils@xercesc_3_1@@**CAPAVXMLNetAccessor@2
>> @XZ)
>> 1>C:\Users\asdf\Documents\**Visual Studio
>> 2010\Projects\xerces-c-3.1.1\**projects\Win32\VC10\xerces-**
>> all\XercesLib\.\..\..\..\..\..**\Build\Win32\VC10\Debug\**
>> xerces-c_3_1D.dll
>> : fatal error LNK1120: 2 unresolved externals
>> ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
>> ==========
>>
>> Next I:
>> - added the include directory to point at the libcurl include directory
>> - added the lib directory to point at the libcurl lib directory
>> - added the library to link against
>>
>> Still the compiler error is the same.
>>
>> What additional step is needed?
>>
>>
>> Thank you,
>>
>> Travis
>>
>>
>

Reply via email to