1>LINK : fatal error LNK1104: cannot open file 'QuantLib-vc110-mt-sgd.lib'
After doing some research on the net, I encountered as a possible source of that error, that QuantLib could be built in release mode and the xll is instead built in debug mode. Then the mismatch of these modes causes the linker error.
So I tried a few combinations:
The lib version of my QuantLib on hard drive is 'QuantLib-vc110-mt-gd.lib'
Compilation of my xll project in debug mode => linker is looking for 'QuantLib-vc110-mt-sgd.lib'
Compilation of my xll project in release mode => linker is looking for 'QuantLib-vc110-mt-s.lib'
As you can see in any case there is no match at all.
Honestly I am bit surprised by the problem and compared all my project properties to a running quantlib example, which compiles as an .exe, but I don't have a clue yet.
In addition I alignedthe properties between QuantLib
( cf C/C++/Code Generation/Runtime Library = /MDd)
and my little xll project. In doing so LNK1104 does not pop up again, but just another bunch of linker errors (e.g.
xll.lib(dllmain.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MTd_StaticDebug' doesn't match value 'MDd_DynamicDebug' in function.obj
Is there a simple solution to the problem(, which does not involve rebuilding the whole QuantLib in order to get the right lib name)?
Many thanks,
Jens
Free forum by Nabble | Disable Popup Ads | Edit this page |