Hi Dirk,
> > In QuantLib 0.3.5, which will be released by the end of this month, the > > boost library is optional. In 0.3.6 the boost library will be mandatory. > >Grrr, had I known that I would have build 0.3.5 with boost support for Debian. sorry Dirk, we probably write too little about development on our mailing lists... anyway no features are missing from the non-boost version. The boost issue is the first item in NEWS.TXT, and the announcement will point that out. Since 0.3.5 will be released on March 31st, can we just rebuild for Debian? To enforce boost dependency in the QuantLib code it's as easy as uncommenting a line of code. BTW what about not releasing binaries for QuantLib? I've decided not to provide binaries for Win32, since that would have been 30Mb (80MB if you consider Debug libraries too). The strong point should be that Quantlib users are C++ developers: they should be able to compile QuantLib on their own. Of course I'm not talking about QL_Python, etc. ciao -- Nando |
Hi Nando
On Thu, Mar 25, 2004 at 04:56:27PM +0100, Ferdinando Ametrano wrote: > Hi Dirk, > > >> In QuantLib 0.3.5, which will be released by the end of this month, the > >> boost library is optional. In 0.3.6 the boost library will be mandatory. > > > >Grrr, had I known that I would have build 0.3.5 with boost support for > >Debian. > > > sorry Dirk, we probably write too little about development on our mailing > lists... anyway no features are missing from the non-boost version. > > The boost issue is the first item in NEWS.TXT, and the announcement will > point that out. Yeah, my bad. Too many balls in the air ... I guess I missed the News.txt file. > Since 0.3.5 will be released on March 31st, can we just rebuild for Debian? > To enforce boost dependency in the QuantLib code it's as easy as > uncommenting a line of code. Yes, that is probably a good idea. Are you guys still hacking on Debian machines. Is what I need among these? Libboost itself, do I need any add-ons? edd@homebud:~/debian/QuantLib/QuantLib-0.3.5> apt-cache search libboost libboost-date-time-dev - Set of date-time libraries based on generic programming concepts libboost-date-time1.30.2 - Set of date-time libraries based on generic programming concepts libboost-dev - Boost.org libraries development files libboost-doc - Boost.org libraries documentation libboost-graph-dev - Generic graph components and algorithms in C++ libboost-graph1.30.2 - Generic graph components and algorithms in C++ libboost-python-dev - The Boost Python Library development files libboost-python1.30.2 - Boost Python Library libboost-regex-dev - Regular expression library for C++ libboost-regex1.30.2 - Regular expression library for C++ libboost-signals-dev - Managed signals and slots library for C++ libboost-signals1.30.2 - Managed signals and slots library for C++ libboost-test-dev - Components for writing and executing test suites libboost-test1.30.2 - Components for writing and executing test suites libboost-thread-dev - Portable C++ multi-threading libboost-thread1.30.2 - Portable C++ multi-threading edd@homebud:~/debian/QuantLib/QuantLib-0.3.5> > BTW what about not releasing binaries for QuantLib? I've decided not to > provide binaries for Win32, since that would have been 30Mb (80MB if you > consider Debug libraries too). The strong point should be that Quantlib > users are C++ developers: they should be able to compile QuantLib on their > own. Of course I'm not talking about QL_Python, etc. The quantlib-examples package has become semi-famous in mail exchanges I am having with the openMosix folks as I use BermudanSwaption as a migration test for openMosix :) The package is only 2mb under Debian, and fully optional. That strikes me as the right thing to do. Dirk -- The relationship between the computed price and reality is as yet unknown. -- From the pac(8) manual page |
Free forum by Nabble | Edit this page |