Menu
▾
▴
Re: [Quantlib-dev] Addin Question
|
From: <dr....@gm...> - 2018-06-27 12:31:25
|
Hi Eric, A few more thoughts... Issue one: Using the "no-number" solution gets rid of this one. Issue two: If... users renamed their boost library "C:\local\boost_current". Then maybe a permeant link to this directory could be used in the VS solution. I'm really, really not a much of a user of Boost though, so I don’t know if this causes other issues. Issue three: I've sent you an email already. Issue four: The instances of hardcoded target names I found were in the build "Release Static" & "x64" (sorry only from memory...) and were for the sub projects... apr, aprutil, log4cxx, ohxllib & xlsdk. Kind Regards Richard Dr....@Gm... 07966 347 202 -----Original Message----- From: Eric Ehlers <eri...@re...> Sent: 26 June 2018 18:14 To: dr....@gm... Cc: qua...@li...; ig...@gm...; js...@ma... Subject: Re: [Quantlib-dev] Addin Question Hi Richard, Apologies for the delay in getting back to you, I am on the road. Congratulations on getting QuantLibXL to build. Regarding the incorrect path for ObjectHandler, I just went to this page... https://sourceforge.net/projects/quantlib/files/ObjectHandler/1.12.0/ ...and I downloaded ObjectHandler-1.12.0.zip and uncompressed it, the paths appear to be correct. What do I need to do to recreate this error? When I package the upcoming release of QuantLibXL 1.13 I will check for any instances of vc140 hard coded and fix them as necessary. Regards, Eric On 2018-06-22 18:00, dr....@gm... wrote: > > Hi, > > Ok I’ve made some progress in getting QuantLibXL to build… > > First, I have got QuantLib to build! > > Also, I have got QuantLibXL_basic to build. Although, this was a > little painful… > > 1. I’m using VS2017 – so everything needs / gets upgraded when you > open the solution files (or it refuses to build…). > 2. Could you mention on the web page that the Boost headers & > libraries need to be linked, via the project settings , in this > way... > "Include directories" : C:\local\boost_1_**_* > "Library directories" : C:\local\boost_1_**_*\lib64-msvc-14.0 > 3. The required directory structure on the web page, > https://www.quantlib.org/quantlibaddin/build_qlxl.html is not one > that I could get working. According to the project solution the > hierarchy should be… > C:\build_ql_1_12_0\QuantLibXL\gensrc (required only for the Full > build) > C:\build_ql_1_12_0\QuantLibXL\log4cxx > C:\build_ql_1_12_0\QuantLibXL\ObjectHandler > C:\build_ql_1_12_0\QuantLibXL\QuantLib > C:\build_ql_1_12_0\QuantLibXL\QuantLibAddin > C:\build_ql_1_12_0\QuantLibXL\QuantLibXL > It would be nice if the website could be updated to mention this & > that the default extraction path of the associated projects of > C:\build_ql_1_12_0\QuantLibXL\ObjectHandler\ObjectHandler > is *one level too long* and needs to be changed to > C:\build_ql_1_12_0\QuantLibXL\ObjectHandler > 4. Some of the subprojects build’s target files have “vc140” > hardcoded into them. But not all, some use $(qlCompilerTag) to > build their target name! > For my set up (VS2017) $(qlCompilerTag) => “vc141”, so my linker > couldn’t find the files it was looking for (the ones with > hardcoded names). > The Fix, is to either edit the target files’ properties and > re-hardcode to vc141. Not a long term good idea… > OR add the *.props file to the subprojects that need them & then > update the target name in the project settings to use the > $(qlCompilerTag). This solution is long term better, but I don’t > know how to do it. > > Kind Regards > Richard > > Dr....@Gm... <mailto:Dr....@Gm...> > > 07966 347 202 > > *From:*Richard Marshall <dr....@gm...> > *Sent:* 20 June 2018 10:27 > *To:* John Samler <js...@ma...> > *Cc:* Eric Ehlers <eri...@re...>; > qua...@li...; ig...@gm... > *Subject:* Re: [Quantlib-dev] Addin Question > > Hi John, Eric & Francois, > > That would be great. It would certainly push the project forwards a > step or 2 for very little effort. > > I don’t actually know how to feed back improvements into the project? > Is there someone that could tell us the best way? > > Also, (maybe of more interest to Francois) I had a look at the > instructions on how to build Quantlib and saw that I had to download > stuff, install stuff, etc etc. I have decided that I like my computer > the way it is! So, I’ve set up a google cloud account (MS and AWS have > similar offerings with free credits) where I can run a virtual machine > with windows os that will build the project. > > I have realised that this way of working has a secondary advantage of > being able to do my work, on my machine (in its original state) after > kicking off the necessary build processes which will would probably > max out my laptop’s capabilities and render it unusable for a while. > > I’ve only just started this on Monday. So I haven’t got very far yet. > I’m following a couple of YouTube videos (search YouTube for > “introduction to quantlib”) and just going to see where the adventure > leads me... > > > Kind regards > > Richard > > Sent from my iPad > > > On 19 Jun 2018, at 17:10, John Samler <js...@ma... > <mailto:js...@ma...>> wrote: > > I've been exposing manually a couple of functions in QuantLibAddin > in my local version for a bit. It's admittedly a bit painful to > have to copy the code every time instead of just use the > pre-compiled versions. > > I haven't tried to add to GitHub because I was expecting the > Reposit project to launch, which seems absolutely amazing! But I > assume that has been put on hold. > > I guess will make sense to just try to add to GitHub the changes I > make which will benefit other users. > > *Sent:* Tuesday, June 12, 2018 at 6:02 PM > *From:* "Eric Ehlers" <eri...@re... > <mailto:eri...@re...>> > *To:* "Richard Marshall" <dr....@gm... > <mailto:dr....@gm...>>, > qua...@li... > <mailto:qua...@li...> > *Subject:* Re: [Quantlib-dev] Addin Question > > Hi Richard, > > Unfortunately these days I don't have time for more than just keeping > the project alive. Perhaps another kind soul here on the list would > volunteer to help out. > > Kind Regards, > Eric > > On 2018-06-08 15:24, Richard Marshall wrote: > > Hi, > > Is there any chance that the inflation swap-curve construction > could be exposed in the next release of the XL addin? > > > > I would find it really helpful! > > > > kind regards > > Richard > > > > Sent from my iPad > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org <http://Slashdot.org>! > http://sdm.link/slashdot > > _______________________________________________ > > QuantLib-dev mailing list > > Qua...@li... > <mailto:Qua...@li...> > > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://Slashdot.org>! > http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > <mailto:Qua...@li...> > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |