versionnumber has the following fields:
yyyyis four decimal digits denoting a year,
mmis two decimal digits denoting a month, and
ddis two decimal digits denoting a day. For example
version = 20160101corresponds to January 1, 2016.
ddequal to zero. These version numbers are combined with release numbers denoted by
rel. Higher release numbers correspond to more bug fixes. For example
version.rel = 20160000.0corresponds to the first release of the version for 2016,
20160000.1corresponds to the first bug fix for 2016.
licto denote the licence corresponding to an archived version of CppAD. The GNU General Public License is denoted by
lic = gpland the Eclipse Public License is denoted by
lic = epl.
In Unix, you can extract these compressed archives using
tar. For example,
No matter what the format of the name, the corresponding distribution directory is
tar -xzf cppad-version.rel.lic.tgz
cppad-version. To see that the extraction has been done correctly, check for the following file:
These archives correspond to the Eclipse Public License.
gitYou can a git clone of the current version using the command
This procedure requires that the git is installed on your system.
git clone https://github.com/coin-or/CppAD.git cppad.git
This procedure requires that the subversion program is installed on your system.
svn checkout https://projects.coin-or.org/svn/CppAD/trunk cppad.svn/trunk
nmake.exeare you your execution path, you will not need to specify their paths below.)
For example, on one machine these paths had the following values:
call "%VCDIR%\vcvarsall.bat" x86
path_to_cmake=C:\Program Files (x86)\CMake\bin
path_to_vcdir=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC
7z x cppad-version.lic.tgz
7z x cppad-version.lic.tar
cmake -G "NMake Makefiles" ..
docsubdirectory of the distribution directory. If there is no such documentation, you can build it; see building documentation .
omhelpcommand so that
shows it is in your path. Once you have done this, in the distribution directory execute the following command:which omhelp
You will then be able to follow the install instructions in the
docsubdirectory of the distribution directory.