C++ C Makefile M4 Shell CMake
Latest commit 518f454 Mar 29, 2017 @lballabio Merge pull request #228.
Failed to load latest commit information.
Docs Update changelog and news. Feb 24, 2017
Examples Remove unused variables. Mar 27, 2017
config Removed obsolete .cvsignore files Mar 30, 2007
m4 Support for new libtool features Feb 11, 2009
man Add new files to distribution. Apr 27, 2016
ql Remove ambiguity in operator precedence. Mar 29, 2017
test-suite Use available test data. Mar 29, 2017
tools Drop support for Visual C++ 8. Aug 5, 2016
.gitignore Merge pull request #216. Mar 24, 2017
Announce.txt Increase version number to 1.10. Nov 8, 2016
Authors.txt Update changes and contributors. Jun 4, 2015
Bugs.txt merged changeset up to Rev16952 from branches/R01000x-branch to trunk Dec 30, 2009
CMakeLists.txt Add Boost directory to CMake include path. Mar 16, 2016
ChangeLog.txt Update changelog and news. Feb 24, 2017
Contributors.txt Update ChangeLog, news and contributors. Oct 21, 2016
LICENSE.TXT Update list of copyrights. Oct 13, 2016
Makefile.am Use single VC++ solution file. Nov 24, 2016
News.txt Update changelog and news. Feb 24, 2017
QuantLib.dev Update projects. Mar 16, 2017
QuantLib.props Enable VC++ 2017 compiler. Mar 8, 2017
QuantLib.sln Merge pull request #113. Feb 23, 2017
QuantLib.spec.in Require Boost 1.43 as minimum version. Apr 6, 2016
QuantLib.vcxproj fixed VS project files Feb 27, 2017
QuantLib.vcxproj.filters fixed VS project files Feb 27, 2017
QuantLib_vc9.sln Merge pull request #113. Feb 23, 2017
QuantLib_vc9.vcproj Update projects. Mar 16, 2017
README.md Revamp Readme. Jan 7, 2016
Readme.txt Revamp Readme. Jan 7, 2016
acinclude.m4 boost 1.64 changes (based on version 1.64.0 beta 1) Mar 24, 2017
autogen.sh Merged 0.3.8 branch Dec 8, 2004
configure.ac Merge pull request #113. Feb 23, 2017
quantlib-config.in added a clean implementation of the thread-safe observer Oct 7, 2015
quantlib.el fix warning during build Aug 31, 2013
quantlib.m4 Fixed m4 macro for QuantLib detection. Apr 21, 2010
quantlib.pc.in Add missing compilation and linking flags. Feb 23, 2016


QuantLib: the free/open-source library for quantitative finance

The QuantLib project (http://quantlib.org) is aimed at providing a comprehensive software framework for quantitative finance. QuantLib is a free/open-source library for modeling, trading, and risk management in real-life.

QuantLib is Non-Copylefted Free Software and OSI Certified Open Source Software.

Download and usage

QuantLib can be downloaded from http://quantlib.org/download.shtml; installation instructions are available at http://quantlib.org/install.shtml for most platforms.

Documentation for the usage and the design of the QuantLib library is available from http://quantlib.org/docs.shtml.

A list of changes for each past versions of the library can be browsed at http://quantlib.org/reference/history.html.

Questions and feedback

Bugs can be reported as a GitHub issue at https://github.com/lballabio/QuantLib/issues; if you have a patch available, you can open a pull request instead (see "Contributing" below).

You can also use the quantlib-users and quantlib-dev mailing lists for feedback, questions, etc. More information and instructions for subscribing are at http://quantlib.org/mailinglists.shtml.


The easiest way to contribute is through pull requests on GitHub. Get a GitHub account if you don't have it already and clone the repository at https://github.com/lballabio/QuantLib with the "Fork" button in the top right corner of the page. Check out your clone to your machine, code away, push your changes to your clone and submit a pull request; instructions are available at https://help.github.com/articles/fork-a-repo. (In case you need them, more detailed instructions for creating pull requests are at https://help.github.com/articles/using-pull-requests, and a basic guide to GitHub is at https://guides.github.com/activities/hello-world/.

It's likely that we won't merge your code right away, and we'll ask for some changes instead. Don't be discouraged! That's normal; the library is complex, and thus it might take some time to become familiar with it and to use it in an idiomatic way.

We're looking forward to your contributions.