At 15.14 02/09/2005 +0530, [EMAIL PROTECTED] wrote:
Thanks for the reply.
It appears to me that Win32 type will be a bigger sized messageloader?
Which one is faster?
I don't know: I guess the faster and smaller is the INMEM, but you
should test it if you care about this difference.
Alberto
warm regards
Saurabh
Alberto Massari <[EMAIL PROTECTED]>
09/02/2005 02:49 PM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: WIN64 build on x64 platform using MSVS 2005 Beta
Hi Saurabh,
the WIN32 message loader stores the error messages as strings in the
resource section of the DLL; the INMEM stores them as C arrays in the
data section of the code.
Alberto
At 14.17 02/09/2005 +0530, [EMAIL PROTECTED] wrote:
>Hi
>Can anyone expalin the difference b/w the WIN32 native messageloader and
>INMEM messageloader?
>
>warm regards
>
>Saurabh
>
>
>
>Saurabh Bhatnagar/BLR/HTL
>08/23/2005 07:38 PM
>
>To
>[email protected]
>cc
>[EMAIL PROTECTED], [email protected],
>[EMAIL PROTECTED]
>Subject
>Re: WIN64 build on x64 platform using MSVS 2005 Beta
>
>
>
>
>
>Hi
>
>I found the cause for this error is that there is no implementation for
>the constructor "InMemMsgLoader(unsigned short const * const)".
>
>It will link fine if we provide a do nothing constructir but as I see for
>other Message Loaders there will be initialisations required.
>
>For now, I am using the WIN32 message loader.
>
>I need to justify it's use instead of the INMEM, can anyone expain the
>difference?
>
>Thanks!
>
>warm regards
>
>Saurabh
>
>
>
>[EMAIL PROTECTED]
>08/23/2005 07:12 PM
>Please respond to
>[email protected]
>
>
>To
>[EMAIL PROTECTED]
>cc
>[EMAIL PROTECTED], [email protected],
>[EMAIL PROTECTED]
>Subject
>Re: WIN64 build on x64 platform using MSVS 2005 Beta
>
>
>
>
>
>
>Hi All
>
>I have been able to build Xerces 64bit with 136 warnings.
>
>I removed the /MACHINE:I386 in the additional preprocessor options. I
>guess one MACHINE is enough.
>
>I used WIN32_MESSAGELOADER above.
>
>As per our requirements we need to use INMEM_MESSAGELOADER. When I
specify
>
>that, I get this error:
>1>Linking...
>1> Creating library
>..\..\..\..\..\Build\Win64\VC8\Release/xerces-c_2.lib and object
>..\..\..\..\..\Build\Win64\VC8\Release/xerces-c_2.exp
>1>Win32PlatformUtils.obj : error LNK2019: unresolved external symbol
>"public: __cdecl xercesc_2_6::InMemMsgLoader::InMemMsgLoader(unsigned
>short const * const)" ([EMAIL PROTECTED]@@[EMAIL PROTECTED]@Z)
>referenced in function "private: static class xercesc_2_6::XMLMsgLoader *
>__cdecl xercesc_2_6::XMLPlatformUtils::loadAMsgSet(unsigned short const *
>const)"
>([EMAIL PROTECTED]@xercesc_2_6@@[EMAIL PROTECTED]@[EMAIL PROTECTED])
>1>..\..\..\..\..\Build\Win64\VC8\Release\xerces-c_2_6.dll : fatal error
>LNK1120: 1 unresolved externals
>
>Any clues? Where does that symbol exist? I can't find it in the source.
>
>warm regards
>
>Saurabh
>
>
>
>Saurabh Bhatnagar/BLR/HTL
>08/23/2005 02:14 PM
>
>To
>[email protected]
>cc
>Akshya Pradhan/BLR/[EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject
>Re: WIN64 build on x64 platform using MSVS 2005 Beta
>
>
>
>
>
>Just to add to the information, here is the Linker command line:
>
>/OUT:"..\..\..\..\..\Build\Win64\VC8\Release\xerces-c_2_6.dll"
>/INCREMENTAL:NO /NOLOGO /LIBPATH:"..\..\..\..\..\Build\Win64\VC8\Release"
>/DLL /MANIFEST
>/MANIFESTFILE:"x64\Release\xerces-c_2_6.dll.intermediate.manifest"
>/PDB:".\..\..\..\..\..\Build\Win64\VC8\Release/xerces-c_2_6.pdb"
>/MAP:".\..\..\..\..\..\Build\Win64\VC8\Release\obj/xerces-c_2_6.map"
>/SUBSYSTEM:WINDOWS /BASE:"0x12000000"
>/IMPLIB:"..\..\..\..\..\Build\Win64\VC8\Release/xerces-c_2.lib"
>/MACHINE:AMD64 /ERRORREPORT:PROMPT ws2_32.lib kernel32.lib user32.lib
>gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib
>oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
>
>I am using the AMD64 target machine, not x86 as it's found by MSVS!!!
>
>warm regards
>
>Saurabh
>
>
>
>Saurabh Bhatnagar/BLR/HTL
>08/23/2005 12:51 PM
>
>To
>[email protected]
>cc
>Akshya Pradhan/BLR/[EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject
>WIN64 build on x64 platform using MSVS 2005 Beta
>
>
>
>
>
>I am getting this fatal error LNK1112
>
>1>..\..\..\..\..\build\win64\vc8\release\obj\Base64.obj : fatal error
>LNK1112: module machine type 'x64' conflicts with target machine type
>'X86'
>
>
>My command line in VC++ 8 looks like
>
>/O1 /Ob2 /I "..\..\..\..\..\src" /D "NDEBUG" /D "PLATFORM_WIN64" /D
>"_CRTDBG_MAP_ALLOC" /D "PROJ_XMLPARSER" /D "PROJ_XMLUTIL" /D
>"PROJ_PARSERS" /D "PROJ_SAX4C" /D "PROJ_SAX2" /D "PROJ_DOM" /D
>"PROJ_VALIDATORS" /D "XML_SINGLEDLL" /D "_WINDOWS" /D
>"XML_USE_WIN32_TRANSCODER" /D "XML_USE_INMEM_MESSAGELOADER" /D
>"XML_USE_NETACCESSOR_WINSOCK" /D "WIN64" /D "_VC80_UPGRADE=0x0700" /D
>"_WINDLL" /GF /FD /EHsc /MD /Zc:wchar_t-
>/Fp".\..\..\..\..\..\Build\Win64\VC8\Release\obj/XercesLib.pch"
>/Fo".\..\..\..\..\..\Build\Win64\VC8\Release\obj/"
>/Fd".\..\..\..\..\..\Build\Win64\VC8\Release\obj/" /W3 /nologo /c /TP
>/errorReport:prompt
>
>The WIN32, what I got from the SLN file has beenn updated with
>""XML_USE_WIN32_TRANSCODER" - is there ""XML_USE_WIN64_TRANSCODER"??
>and I have replaced "PLATFORM_WIN32" with "PLATFORM_WIN64" and added
>"WIN64".
>
>Please give me the proper steps to build.
>
>
>warm regards
>
>Saurabh
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
