Re: [Quantlib-users] QuantLib Calc addin compilation

[Francois B. <ig...@gm...>]

Hi Alan,

I also had a look at https://github.com/lcallenbach/quantlibaddin . It uses
a different approach to configure and generate the C++ code than the
original QuantLibAddin repository (which uses .xml files). I managed to
build the add-in on Windows and got it working in LibreOffice, but it lacks
many of the classes, types and enumerations that I normally work with, so
it would be unsuitable for my use, but I can see how it can be extended
easily.

It also seems that all parameters for the QL* functions are compulsory,
even the object ID for the instantiated object. This is a deal-breaker for
me, but the novel code generation approach does intrigue me. It's a pity
the author doesn't respond and that it looks like the project has stalled.

[image: image.png]

regards
Francois Botha


On Thu, 25 Aug 2022 at 17:58, Eric Ehlers <eri...@re...> wrote:

> Hello,
>
> The last version of QuantLibAddin that supported the Calc addin was 1.0.1,
> released in 2010.  You could try downloading that and following the
> documentation which came with it but I wouldn't hold out much hope because
> LibreOffice has probably moved on since then.
>
> At the link you provided it looks like somebody managed to get it working
> more recently but I don't know anything about that.  Maybe somebody else
> will chime in with more info.  Sorry that I can't be more helpful.
>
> Regards,
> Eric
> On 25/08/2022 13:01, Alan teixeira nicacio de messias Nicacio via
> QuantLib-users wrote:
>
> Hello. I've been studying QuantLib C++ library for some months.  Recently
> I got interested in knowing and using the LibreOffice Calc export, I tried
> to follow the instructions described at
> github.com/lcallenbach/quantlibaddin but I didn't totally understand the *code
> compilation* section (I'm a mathematician, novice to software
> development). I tried to contact the address *lcallenbach@de*, but had no
> success. Since the information on internet is scarce and old, I decided to
> post on this list. In the following I'll just explain what I already did
> and what I wasn't able to do.
>
> My configurations: Windows 10 64-bit, MVSC C++ compiler, latest Anaconda3
> (with Python 3.9), Linux shell for windows (Ubuntu 20.04.4 LTS),
> LibbreOffice 7.4.
>
> *Code generation*: In 'gensrc' folder I executed on Anaconda3 Powershell
> the command '*python main.py -o*', it ran without problems and generated
> some c++ source files and a .idl file in 'Calc' folder.
>
> *Code compilation*:
> In 'Calc' folder I edited the file 'environment.sh'. I inserted the three
> respective address according to my system (I just wrote the address and
> save the changes). In the guide it says " In order to compile the files
> generated you have to include the path variables (e.g. execute '.
> environment.sh' under Gnu/Linux-bash ". Here I have a question: the only
> 'environment.sh' I see in 'Calc' folder is the one I just edited, when I
> execute it in the Ubuntu shell it does nothing (what is normal since there
> are only path descriptions in that file). What am I doing wrong?
>
> In the sequence it says " Include the LibreOffice SDK development setup
> to your path (e.g. execute '. ~/libreoffice/sdk/setsdkenv_unix.sh' under
> Gnu/Linux-bash) ". In my case I executed the 'setsdkenv_windows.bat'
> which just asked some directories and then created a new
> 'setsdkenv_windows.bat' in user's home directory, all as described on the
> LibreOffice installation guide page api.libreoffice.org/docs/install.html
> .
>
> Now it says " If both paths are set call 'make' ". Question: Does "to be
> set" mean '. environment.sh' and 'setsdkenv_windows.bat' executed as
> described in the guide? If yes they are already set, if not what does it
> mean so? Supposing the paths are set, where do I have to call 'make'? On
> which directory?, on which prompt (Anaconda, cmd, bash)? Would 'make' mean
> 'Makefile'?
>
> Finally the guide ends with " If you have used the auto-installation
> feature of the LibreOffice SDK nothing else has to be done. You can open
> the test sheet 'Examples.ods' by executing 'soffice path/Examples.ods' ".
> I think that I used the auto-installation feature of the LibreOffice
> (didn't I?). What does 'soffice path' mean? on which prompt do I execute 'soffice
> path/Examples.ods' (Anaconda, cmd, bash)?
>
> I'll really appreciate if somebody could help me here or indicate where I
> can find help.
>
> Regards.
>
>
>
> _______________________________________________
> QuantLib-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/quantlib-users
>
> _______________________________________________
> QuantLib-users mailing list
> Qua...@li...
> https://lists.sourceforge.net/lists/listinfo/quantlib-users
>