QuantLibXL_d.xll compiling errors

Posted by Zhuang, Deming on
URL: http://quantlib.414.s1.nabble.com/QuantLibXL-d-xll-compiling-errors-tp2207.html

Hi:

I just downloaded QuantLib version 0.3.0 and QuantLibXL. Using VC++ 6.0 Standard version, and the workspace file coming with the installation, without changing any code or setting, I attempted to build QuantLib_d.xll myself. The following compiling errors appear:

Deleting intermediate files and output files for project 'QuantLibXL - Win32 OnTheEdgeDebug'.
--------------------Configuration: QuantLibXL - Win32 OnTheEdgeDebug--------------------
Compiling...
datef.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
engines.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
mathf.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
montecarlo.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
pricers.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
qlxlfoper.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
termstructures.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
utilities.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
vols.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
xlAutoOpen.cpp
d:\excelexamples\quantlibxl\qlxl\qlxl.hpp(45) : fatal error C1189: #error :  using an old version of QuantLib, please update
Error executing cl.exe.

QuantLibXL_d.xll - 10 error(s), 0 warning(s)

Has anyone seen these errors before? Any help would be greatly appreciated.