I burned some cycles, building QuantLibXL in various forms using Visual Studio 2012 on a Win 7, 64 bit box.
Here are my results.
I built the “full” QuantLibXL add-in in 32 bit without a problem. It even works with the cell menu from the earlier version of the framework, once I updated cells C17 and C25 in the “Loader.xls” file in the “..\framework\config\” folder.
I also built the “full” QuantLibXL add-in in 64 bit as Static. To use it in Excel 2010 and later, however, the “Declare” statements in the VBA for Utilities.xla, FixedIncome.xla and FixedIncome2.xla in the “..\framework\addin\” folder need to be followed with “PtrSafe” in order to work. Actually, any “Declare” statement should get the same treatment. There could be other cases lurking out there in other macros I just did not find.
The "full" Static build in 64 bit does not try to build the framework, i.e. QuantLib.xla in “..\QuantLibXL\framework\". The “full” Static build also does not create the ObjectHandler-xll-vc110-x64-mt-1_5_0.xll folder or file, which makes it impossible to completely set up the Loader.xls file mentioned above. I have been unable to get the previous version of the framework working in 64-bit Excel, running into issues with the testVbaTrusted subroutine in the FixedIncome.xla file as noted in the following message when trying to load FixedIncome from the add-in tab:
“Fatal error-In order to run QuantLibXL, you must enable ‘Trust access to Visual Basic’:
Under Tools/Macros/Security/, tab ‘Trusted Sources’, enable ‘Trust access to Visual Basic Project’”.
I have adjusted the Trust settings to include all the files resulting from the building process, so I am not sure what that is about.
When I try to load FixedIncome2 from the add-in tab, I get the following message:
“Error initializing fixed income 2:
Unable to convert parameter ‘Set Evaluation Date’ to Boolean”.
I was unsure what to expect from the “QuantLibAllDynamic_vc11.sln”. I built it as Release–x64. It built QuantLib, and tested it (which the “full” build does not do). It built the ObjectHandler-xll-vc110-x64-mt-1_5_0.xll folder and file, and of course the QuantLibXLDynamic_vc110-x64-mt-1_6_0.xll. It failed to build the document files for QuantLibXL and QuantLibAddin. These look like NMAKE problems, but trying the Python path mod did not fix it. The error messages are included below.
I was also unsure about how I might best use the outputs from building QuantLibAllDynamic_vc11.sln in practice. The examples in the “..\ObjectHandler\Examples\xl\” folder and the instructions on the O-H web page do not seem to reflect the current results of the build process. If I try to attach the xll as an add-in, Excel tries to load it as a spreadsheet, creating problems of its own. How do you recommend using the outputs from building the sln file with Excel?
Great work on what you have done, but I could use some directions to files to update to get the framework for the “full” Static state working for x64, should you want the assistance.
-Nick
------------------------------------------------
QuantLibAllDynamic_vc11.sln Build Errors:
Error 32 error U1077: '..\..\ObjectHandler\Docs\preprocess_doxyfile.py' : return code '0x1' C:\build_ql_1_6_0\QuantLibXL\Docs\NMAKE docs-QuantLibXL
Error 33 error MSB3073: The command "NMAKE /f Makefile.vc" exited with code 2. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.MakeFile.Targets 38 5 docs-QuantLibXL
Error 34 error U1077: '..\..\ObjectHandler\Docs\preprocess_doxyfile.py' : return code '0x1' C:\build_ql_1_6_0\QuantLibAddin\Docs\NMAKE docs-QuantLibAddin
Error 35 error MSB3073: The command "NMAKE /f Makefile.vc" exited with code 2. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.MakeFile.Targets 38 5 docs-QuantLibAddin
Any advice for me?
-Nick
------------------------------------------------------------------------------
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users
Locked
