You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Shalmi <sh...@gmail.com> on 2007/11/21 18:59:28 UTC
Linking problem for dll using xerces
Hi,
I have created an dll which internally makes use of xerces and do some work.
I have client which makes use of my dll. When i developed th dll using VC6
and used in a client in VS2003 it gets linked and gets properly called. But
if i try to create dll in VS2003 then it does gets compiled but client
application is not able to link to the function.
Do i need to do some settings for VS2003? I have already made it multi
threaded and tchar settings. Is anything else is needed for VC7 onwards?
Any help is highly appreciated.
Regards
Shalmi
--
View this message in context: http://www.nabble.com/Linking-problem-for-dll-using-xerces-tf4851876.html#a13882607
Sent from the Xerces - C - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Linking problem for dll using xerces
Posted by Alberto Massari <am...@datadirect.com>.
Shalmi wrote:
>
> David Bertoni wrote:
>
>> Shalmi wrote:
>>
>>> Hi,
>>> Here is the error log file generated by VC
>>> ======================================
>>> Build Log ------- Build started: Project: TestinForDll,
>>> Configuration:
>>> Debug|Win32 -------
>>>
>>> Command Lines Creating temporary file
>>> "d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp" with contents
>>> [
>>> /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /Gm /EHsc /RTC1 /MTd
>>> /Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /c /Wp64 /ZI /TP
>>> .\TestinForDll.cpp
>>> ]
>>> Creating command line "cl.exe
>>> @d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp /nologo"
>>> Creating temporary file
>>> "d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002B.rsp" with contents
>>> [
>>> /OUT:"Debug/TestinForDll.exe" /INCREMENTAL /NOLOGO /DEBUG
>>> /PDB:"Debug/TestinForDll.pdb" /SUBSYSTEM:CONSOLE /MACHINE:X86
>>> /VERBOSE:LIB
>>> INPUTXML.lib xerces-c_2D.lib Xalan-C_1D.lib xsec_1.lib SimpleTestDll.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
>>> ".\xerces-c_2D.lib" ".\Xalan-C_1D.lib"
>>>
>> ...
>>
>>> Finished searching libraries
>>> TestinForDll.obj : error LNK2019: unresolved external symbol
>>> _CreateFinalDOM
>>> referenced in function _main
>>> Debug/TestinForDll.exe : fatal error LNK1120: 1 unresolved externals
>>> Results Build log was saved at
>>> "file://d:\Shalmi\TestinForDll\TestinForDll\Debug\BuildLog.htm"
>>> TestinForDll - 2 error(s), 1 warning(s)
>>> ==========================================================================
>>> Any guesses?
>>>
>> That's not a Xerces-C symbol, so you'll need to look at the source code
>> for
>> that object file, and determine where it might be coming from .
>>
>> Dave
>>
>>
>>
> Hi,
>
> The function CreateFinalDOM is a function which will call xerces API. That
> (CreateFinalDOM)function is residing in my dll. So do my client need
> anything special?
>
>
You are probably not exporting that function from the DLL; have a look
at http://msdn2.microsoft.com/en-us/library/z4zxe9k8(VS.71).aspx to
learn how you can do it.
Alberto
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Linking problem for dll using xerces
Posted by Shalmi <sh...@gmail.com>.
David Bertoni wrote:
>
> Shalmi wrote:
>> Hi,
>> Here is the error log file generated by VC
>> ======================================
>> Build Log ------- Build started: Project: TestinForDll,
>> Configuration:
>> Debug|Win32 -------
>>
>> Command Lines Creating temporary file
>> "d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp" with contents
>> [
>> /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /Gm /EHsc /RTC1 /MTd
>> /Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /c /Wp64 /ZI /TP
>> .\TestinForDll.cpp
>> ]
>> Creating command line "cl.exe
>> @d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp /nologo"
>> Creating temporary file
>> "d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002B.rsp" with contents
>> [
>> /OUT:"Debug/TestinForDll.exe" /INCREMENTAL /NOLOGO /DEBUG
>> /PDB:"Debug/TestinForDll.pdb" /SUBSYSTEM:CONSOLE /MACHINE:X86
>> /VERBOSE:LIB
>> INPUTXML.lib xerces-c_2D.lib Xalan-C_1D.lib xsec_1.lib SimpleTestDll.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
>> ".\xerces-c_2D.lib" ".\Xalan-C_1D.lib"
> ...
>> Finished searching libraries
>> TestinForDll.obj : error LNK2019: unresolved external symbol
>> _CreateFinalDOM
>> referenced in function _main
>> Debug/TestinForDll.exe : fatal error LNK1120: 1 unresolved externals
>> Results Build log was saved at
>> "file://d:\Shalmi\TestinForDll\TestinForDll\Debug\BuildLog.htm"
>> TestinForDll - 2 error(s), 1 warning(s)
>> ==========================================================================
>> Any guesses?
> That's not a Xerces-C symbol, so you'll need to look at the source code
> for
> that object file, and determine where it might be coming from .
>
> Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: c-dev-help@xerces.apache.org
>
>
>
Hi,
The function CreateFinalDOM is a function which will call xerces API. That
(CreateFinalDOM)function is residing in my dll. So do my client need
anything special?
--
View this message in context: http://www.nabble.com/Linking-problem-for-dll-using-xerces-tf4851876.html#a13906848
Sent from the Xerces - C - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Linking problem for dll using xerces
Posted by David Bertoni <db...@apache.org>.
Shalmi wrote:
> Hi,
> Here is the error log file generated by VC
> ======================================
> Build Log ------- Build started: Project: TestinForDll, Configuration:
> Debug|Win32 -------
>
> Command Lines Creating temporary file
> "d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp" with contents
> [
> /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /Gm /EHsc /RTC1 /MTd
> /Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /c /Wp64 /ZI /TP
> .\TestinForDll.cpp
> ]
> Creating command line "cl.exe
> @d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp /nologo"
> Creating temporary file
> "d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002B.rsp" with contents
> [
> /OUT:"Debug/TestinForDll.exe" /INCREMENTAL /NOLOGO /DEBUG
> /PDB:"Debug/TestinForDll.pdb" /SUBSYSTEM:CONSOLE /MACHINE:X86 /VERBOSE:LIB
> INPUTXML.lib xerces-c_2D.lib Xalan-C_1D.lib xsec_1.lib SimpleTestDll.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
> ".\xerces-c_2D.lib" ".\Xalan-C_1D.lib"
...
> Finished searching libraries
> TestinForDll.obj : error LNK2019: unresolved external symbol _CreateFinalDOM
> referenced in function _main
> Debug/TestinForDll.exe : fatal error LNK1120: 1 unresolved externals
> Results Build log was saved at
> "file://d:\Shalmi\TestinForDll\TestinForDll\Debug\BuildLog.htm"
> TestinForDll - 2 error(s), 1 warning(s)
> ==========================================================================
> Any guesses?
That's not a Xerces-C symbol, so you'll need to look at the source code for
that object file, and determine where it might be coming from .
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Linking problem for dll using xerces
Posted by Shalmi <sh...@gmail.com>.
Hi,
Here is the error log file generated by VC
======================================
Build Log ------- Build started: Project: TestinForDll, Configuration:
Debug|Win32 -------
Command Lines Creating temporary file
"d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp" with contents
[
/Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /Gm /EHsc /RTC1 /MTd
/Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /c /Wp64 /ZI /TP
.\TestinForDll.cpp
]
Creating command line "cl.exe
@d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002A.rsp /nologo"
Creating temporary file
"d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002B.rsp" with contents
[
/OUT:"Debug/TestinForDll.exe" /INCREMENTAL /NOLOGO /DEBUG
/PDB:"Debug/TestinForDll.pdb" /SUBSYSTEM:CONSOLE /MACHINE:X86 /VERBOSE:LIB
INPUTXML.lib xerces-c_2D.lib Xalan-C_1D.lib xsec_1.lib SimpleTestDll.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
".\xerces-c_2D.lib" ".\Xalan-C_1D.lib"
.\Debug\stdafx.obj
.\Debug\TestinForDll.obj
]
Creating command line "link.exe
@d:\Shalmi\TestinForDll\TestinForDll\Debug\RSP00002B.rsp"
Output Window Compiling...
TestinForDll.cpp
c:\xerces-c-src_2_7_0\src\xercesc\internal\XSerializeEngine.hpp(818) :
warning C4244: 'return' : conversion from '__w64 int' to 'unsigned long',
possible loss of data
Linking...
Searching libraries
Searching INPUTXML.lib:
Searching xerces-c_2D.lib:
Searching Xalan-C_1D.lib:
Searching xsec_1.lib:
Searching SimpleTestDll.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\kernel32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\user32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\gdi32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\winspool.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\comdlg32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\advapi32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\shell32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\ole32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\oleaut32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\uuid.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\odbc32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\odbccp32.lib:
Searching .\xerces-c_2D.lib:
Searching .\Xalan-C_1D.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\libcpmtd.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\LIBCMTD.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\OLDNAMES.lib:
Searching INPUTXML.lib:
Searching xerces-c_2D.lib:
Searching Xalan-C_1D.lib:
Searching xsec_1.lib:
Searching SimpleTestDll.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\kernel32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\user32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\gdi32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\winspool.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\comdlg32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\advapi32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\shell32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\ole32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\oleaut32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\uuid.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\odbc32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\odbccp32.lib:
Searching .\xerces-c_2D.lib:
Searching .\Xalan-C_1D.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\libcpmtd.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\LIBCMTD.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\OLDNAMES.lib:
Searching INPUTXML.lib:
Searching xerces-c_2D.lib:
Searching Xalan-C_1D.lib:
Searching xsec_1.lib:
Searching SimpleTestDll.lib:
Finished searching libraries
Creating library Debug/TestinForDll.lib and object Debug/TestinForDll.exp
Searching libraries
Searching INPUTXML.lib:
Searching xerces-c_2D.lib:
Searching Xalan-C_1D.lib:
Searching xsec_1.lib:
Searching SimpleTestDll.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\kernel32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\user32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\gdi32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\winspool.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\comdlg32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\advapi32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\shell32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\ole32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\oleaut32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\uuid.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\odbc32.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\lib\odbccp32.lib:
Searching .\xerces-c_2D.lib:
Searching .\Xalan-C_1D.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\libcpmtd.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\LIBCMTD.lib:
Searching C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\lib\OLDNAMES.lib:
Finished searching libraries
TestinForDll.obj : error LNK2019: unresolved external symbol _CreateFinalDOM
referenced in function _main
Debug/TestinForDll.exe : fatal error LNK1120: 1 unresolved externals
Results Build log was saved at
"file://d:\Shalmi\TestinForDll\TestinForDll\Debug\BuildLog.htm"
TestinForDll - 2 error(s), 1 warning(s)
==========================================================================
Any guesses?
Regards
Shalmi
Alberto Massari wrote:
>
> Hi Shalmi,
> could you post the error log? It's hard to guess what is going wrong
> from just a "not able to link" sentence...
>
> Alberto
>
> Shalmi wrote:
>>
>> Shalmi wrote:
>>
>>> Hi,
>>> I have created an dll which internally makes use of xerces and do some
>>> work. I have client which makes use of my dll. When i developed th dll
>>> using VC6 and used in a client in VS2003 it gets linked and gets
>>> properly
>>> called. But if i try to create dll in VS2003 then it does gets compiled
>>> but client application is not able to link to the function.
>>> Do i need to do some settings for VS2003? I have already made it multi
>>> threaded and tchar settings. Is anything else is needed for VC7 onwards?
>>> Any help is highly appreciated.
>>> Regards
>>> Shalmi
>>>
>>>
>> Hi,
>>
>> Now i have built serces dll for VC7.1 and everything(my dll which makes
>> use
>> od xerces dll and client which makes use of my dll) are in VC7.1. But
>> still
>> client is not able to link to function.
>> Any help??
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: c-dev-help@xerces.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Linking-problem-for-dll-using-xerces-tf4851876.html#a13893205
Sent from the Xerces - C - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Linking problem for dll using xerces
Posted by Alberto Massari <am...@datadirect.com>.
Hi Shalmi,
could you post the error log? It's hard to guess what is going wrong
from just a "not able to link" sentence...
Alberto
Shalmi wrote:
>
> Shalmi wrote:
>
>> Hi,
>> I have created an dll which internally makes use of xerces and do some
>> work. I have client which makes use of my dll. When i developed th dll
>> using VC6 and used in a client in VS2003 it gets linked and gets properly
>> called. But if i try to create dll in VS2003 then it does gets compiled
>> but client application is not able to link to the function.
>> Do i need to do some settings for VS2003? I have already made it multi
>> threaded and tchar settings. Is anything else is needed for VC7 onwards?
>> Any help is highly appreciated.
>> Regards
>> Shalmi
>>
>>
> Hi,
>
> Now i have built serces dll for VC7.1 and everything(my dll which makes use
> od xerces dll and client which makes use of my dll) are in VC7.1. But still
> client is not able to link to function.
> Any help??
>
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Linking problem for dll using xerces
Posted by Shalmi <sh...@gmail.com>.
Shalmi wrote:
>
> Hi,
> I have created an dll which internally makes use of xerces and do some
> work. I have client which makes use of my dll. When i developed th dll
> using VC6 and used in a client in VS2003 it gets linked and gets properly
> called. But if i try to create dll in VS2003 then it does gets compiled
> but client application is not able to link to the function.
> Do i need to do some settings for VS2003? I have already made it multi
> threaded and tchar settings. Is anything else is needed for VC7 onwards?
> Any help is highly appreciated.
> Regards
> Shalmi
>
Hi,
Now i have built serces dll for VC7.1 and everything(my dll which makes use
od xerces dll and client which makes use of my dll) are in VC7.1. But still
client is not able to link to function.
Any help??
--
View this message in context: http://www.nabble.com/Linking-problem-for-dll-using-xerces-tf4851876.html#a13891735
Sent from the Xerces - C - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org