Unresolved externals error linking quantlib_python 0.3.10

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Unresolved externals error linking quantlib_python 0.3.10

ago-2
Hi all,

I am trying to build Quantlib_Python 0.3.10 using "setup.py build"
against quantlib 0.3.10 (compiled as release, tests are ok) using
MSVS7.1 but I get unresolved externals errors. The output is attached
below. Any help is appreciated. Thanks



--------------------------------------

  C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\link.exe
/DLL /nologo
  /INCREMENTAL:NO /LIBPATH:Z:\QuantLib\QuantLib-0.3.10\lib
/LIBPATH:C:\Boost\lib
"/LIBPATH:C:\Program Files\Python24\libs" "/LIBPATH:C:\Program
Files\Python24\PC
Build" /EXPORT:init_QuantLib
build\temp.win32-2.4\Release\QuantLib/quantlib_wrap
.obj /OUT:build\lib.win32-2.4\QuantLib\_QuantLib.pyd
/IMPLIB:build\temp.win32-2.
4\Release\QuantLib\_QuantLib.lib /subsystem:windows /machine:I386

    Creating library build\temp.win32-2.4\Release\QuantLib\_QuantLib.lib
and obje
ct build\temp.win32-2.4\Release\QuantLib\_QuantLib.exp

quantlib_wrap.obj : error LNK2019: unresolved external symbol "public:
static cl
ass QuantLib::Period __cdecl QuantLib::PeriodParser::parse(class
std::basic_stri
ng<char,struct std::char_traits<char>,class std::allocator<char> > const
&)" (?p
arse@PeriodParser@QuantLib@@SA?AVPeriod@2@ABV?$basic_string@DU?$char_traits@D@st
d@@V?$allocator@D@2@@std@@@Z) referenced in function "class
QuantLib::Period * _
_cdecl new_Period__SWIG_1(class std::basic_string<char,struct
std::char_traits<c
har>,class std::allocator<char> > const &)"
(?new_Period__SWIG_1@@YAPAVPeriod@Qu
antLib@@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)

quantlib_wrap.obj : error LNK2019: unresolved external symbol "public:
static cl
ass QuantLib::Date __cdecl QuantLib::DateParser::parse(class
std::basic_string<c
har,struct std::char_traits<char>,class std::allocator<char> > const
&,class std
::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > c
onst &)"
(?parse@DateParser@QuantLib@@SA?AVDate@2@ABV?$basic_string@DU?$char_tra
its@D@std@@V?$allocator@D@2@@std@@0@Z) referenced in function "class
QuantLib::D
ate * __cdecl new_Date__SWIG_3(class std::basic_string<char,struct
std::char_tra
its<char>,class std::allocator<char> > const &,class
std::basic_string<char,stru
ct std::char_traits<char>,class std::allocator<char> > const &)"
(?new_Date__SWI
G_3@@YAPAVDate@QuantLib@@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D
@2@@std@@0@Z)

quantlib_wrap.obj : error LNK2019: unresolved external symbol "public:
__thiscal
l QuantLib::Bratislava::Bratislava(void)"
(??0Bratislava@QuantLib@@QAE@XZ) refer
enced in function __wrap_new_Bratislava

quantlib_wrap.obj : error LNK2019: unresolved external symbol "public:
__thiscal
l QuantLib::Istanbul::Istanbul(void)" (??0Istanbul@QuantLib@@QAE@XZ)
referenced
in function __wrap_new_Istanbul

quantlib_wrap.obj : error LNK2019: unresolved external symbol "public:
__thiscal
l QuantLib::Prague::Prague(void)" (??0Prague@QuantLib@@QAE@XZ)
referenced in fun
ction __wrap_new_Prague

build\lib.win32-2.4\QuantLib\_QuantLib.pyd : fatal error LNK1120: 5
unresolved e
xternals

error: command '"C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\bin\link
.exe"' failed with exit status 1120



Reply | Threaded
Open this post in threaded view
|

Re: Unresolved externals error linking quantlib_python 0.3.10

Luigi Ballabio
On 07/20/2005 11:32:55 PM, Agostino Russo wrote:
> I am trying to build Quantlib_Python 0.3.10 using "setup.py build"  
> against quantlib 0.3.10 (compiled as release, tests are ok) using  
> MSVS7.1 but I get unresolved externals errors.

Agostino,
        it seems that there are a few files missing in the VC7.1  
project for the library. You'll have to open it and add the following  
files:
ql/Utilities/dataparsers.cpp
ql/Calendars/bratislava.cpp
ql/Calendars/istanbul.cpp
ql/Calendars/prague.cpp

After that, you should recompile the library (which should only trigger  
the compilation of the above files if you already compiled the rest.)

The Python module should then be happy with the new library.

Later,
        Luigi

----------------------------------------

The box said "Use Windows 95 or better," so I got a Macintosh.