AddInExcel Problem

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

AddInExcel Problem

John Howard-11
I am having problems building the AddinExcel project.  The following items
describe my development environment and the libraries into which I have
installed the pertinent software:

Operating System:  Windows XP Service Pack 2
Development Environment:  Visual C++.NET 2003 from February (or around that
time) 2003

Quantlib Version:  QuantLib-0.3.10
QuantlibAddin Version:  QuantLibAddin-0.3.10

QuantLib Directory:  C:\QuantLib (This is also the value of system variable
QL_DIR)

QuantLibAddin Directory: C:\Program Files\QuantLibAddin

My attempting to build the cited project with the project settings as
installed resulted in my getting the three external reference errors -- the
references to the calendars as cited in problems previously submitted.

I was able to resolve these references by changing '$(QL_DIR)\lib' in the
Additional Include Libraries under the Linkage tab under the Project
Properties tab to '$(QL_DIR)'.  However, my changing that reference resulted
in a library not found error -- 'QuantLib-vc71-mt-sgd-0_3_10.lib' couldn't
be found even though it is in C:\QuantLib\lib where it is supposed to be.

The problem I am finding is that the link step is expecting to find the
calendar references in (in my case) C:\Quantlib\ql and the Quantlib .lib
reference in C:\Quantlib\lib -- simple enough.  But referring to the \lib
directory is a reference that is one level below where the calendar
references are located and thus they can't be found.

Anyway, that is the problem I am having in getting the AddinExcel project
built.  I would appreciate any help I can get on this.

Thanks in advance,

John

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/



Reply | Threaded
Open this post in threaded view
|

Re: AddInExcel Problem

eric ehlers
Hi John,

I believe the QuantLib-0.3.10 VC7 workspace shipped with those 3
calendars omitted - you should be able to either add the three
calendars to the workspace and recompile QuantLib, or just comment out
the references to the three calendars in QuantLibAddin file
enumregistry.cpp.

Regards,
Eric

On 10/16/05, John Howard <[hidden email]> wrote:

> I am having problems building the AddinExcel project.  The following items
> describe my development environment and the libraries into which I have
> installed the pertinent software:
>
> Operating System:  Windows XP Service Pack 2
> Development Environment:  Visual C++.NET 2003 from February (or around that
> time) 2003
>
> Quantlib Version:  QuantLib-0.3.10
> QuantlibAddin Version:  QuantLibAddin-0.3.10
>
> QuantLib Directory:  C:\QuantLib (This is also the value of system variable
> QL_DIR)
>
> QuantLibAddin Directory: C:\Program Files\QuantLibAddin
>
> My attempting to build the cited project with the project settings as
> installed resulted in my getting the three external reference errors -- the
> references to the calendars as cited in problems previously submitted.
>
> I was able to resolve these references by changing '$(QL_DIR)\lib' in the
> Additional Include Libraries under the Linkage tab under the Project
> Properties tab to '$(QL_DIR)'.  However, my changing that reference resulted
> in a library not found error -- 'QuantLib-vc71-mt-sgd-0_3_10.lib' couldn't
> be found even though it is in C:\QuantLib\lib where it is supposed to be.
>
> The problem I am finding is that the link step is expecting to find the
> calendar references in (in my case) C:\Quantlib\ql and the Quantlib .lib
> reference in C:\Quantlib\lib -- simple enough.  But referring to the \lib
> directory is a reference that is one level below where the calendar
> references are located and thus they can't be found.
>
> Anyway, that is the problem I am having in getting the AddinExcel project
> built.  I would appreciate any help I can get on this.
>
> Thanks in advance,
>
> John