=== Contents ===

1: Introduction
   1.1: Citation Details

2: Installation
   2.0: Preliminaries
   2.1: Installation on Linux and Mac OS X
   2.2: Manual Installation / Installation on Windows

3: Compiling Programs and Linking
   3.0: Examples
   3.1: Compiling & Linking on Linux and Mac OS X
   3.2: Compiling & Linking on Windows

4: Support for high-speed BLAS & LAPACK replacements
   4.0: Support for Intel MKL and AMD ACML
   4.1: Support for ATLAS

5: Documentation / Reference Manual

6: FAQs and Bug Reports

7: Credits

8: License

=== 1.0: Introduction ===

Armadillo is a C++ linear algebra library (matrix maths)
aiming towards a good balance between speed and ease of use.
Integer, floating point and complex numbers are supported,
as well as a subset of trigonometric and statistics functions.
Various matrix decompositions are provided through optional
integration with LAPACK or high-performance LAPACK-compatible
libraries (such as Intel's MKL or AMD's ACML).

A delayed evaluation approach is employed (during compile time)
to combine several operations into one and reduce (or eliminate)
the need for temporaries. This is accomplished through recursive
templates and template meta-programming.

This library is useful if C++ has been decided as the language
of choice (due to speed and/or integration capabilities),
rather than another language like Matlab or Octave.
It is distributed under a license that is useful in both
open-source and proprietary contexts.

Armadillo is primarily developed at NICTA (Australia),
with contributions from around the world.
More information about NICTA can be obtained from:

=== 1.1: Citation Details ===

If you use Armadillo in your research and/or software,
please cite the following tech report. Citations are useful
for the continued development and maintenance of the library.

  Conrad Sanderson.
  Armadillo: An Open Source C++ Linear Algebra Library for
  Fast Prototyping and Computationally Intensive Experiments.
  Technical Report, NICTA, 2010.

=== 2.0: Installation: Preliminaries ===

Armadillo makes extensive use of template meta-programming,
recursive templates and template based function overloading.
As such, C++ compilers which do not fully implement the C++
standard may not work correctly.

The functionality of Armadillo is partly dependent on other
libraries: mainly LAPACK and BLAS. Armadillo can work without
LAPACK or BLAS, but its functionality will be reduced.
In particular, basic functionality will be available
(eg. matrix addition and multiplication), but things like
eigen decomposition or matrix inversion will not be.
Matrix multiplication (mainly for big matrices) may not be as fast.

* For automatic installation on Linux and Mac OS X systems,
  see section 2.1. This installation is also likely to work on
  other Unix-like systems, such as FreeBSD, NetBSD, OpenBSD,
  Solaris, CygWin, etc.
* For manual installation and/or installation on Windows,
  see section 2.2.

* If you have a previous version of Armadillo already installed,
  we recommend removing it before installing a newer version.

=== 2.1: Installation on Linux and Mac OS X ===

You can use the manual installation process as described in
section 2.2, or the following CMake based automatic installation.

* Step 1:
  If CMake is not already be present on your system, download
  it from

  On major Linux systems (such as Fedora, Ubuntu, Debian, etc),
  cmake is available as a pre-built package, though it may need
  to be explicitly installed (using a tool such as PackageKit,
  yum, rpm, apt, aptitude).
* Step 2:
  If you have BLAS and/or LAPACK, install them before installing
  Armadillo. Under Mac OS X this is not necessary.
  On Linux systems it is recommended that the following libraries
  are present: LAPACK, BLAS, ATLAS and Boost. LAPACK and BLAS are
  the most important. If you have ATLAS and Boost, it's also necessary
  to have the corresponding header files installed.
* Step 3:
  Open a shell (command line), change into the directory that was
  created by unpacking the armadillo archive, and type the following
  cmake .
  The full stop separated from "cmake" by a space is important.
  CMake will figure out what other libraries are currently installed
  and will modify Armadillo's configuration correspondingly.
  CMake will also generate a run-time armadillo library, which is a 
  combined alias for all the relevant libraries present on your system
  (eg. BLAS, LAPACK and ATLAS).
  If you need to re-run cmake, it's a good idea to first delete the
  "CMakeCache.txt" file (not "CMakeLists.txt").
* Step 4:
  If you have access to root/administrator/superuser privileges,
  first enable the privileges (eg. through "su" or "sudo")
  and then type the following command:
  make install
  If you don't have root/administrator/superuser privileges, 
  type the following command:
  make install DESTDIR=my_usr_dir
  where "my_usr_dir" is for storing C++ headers and library files.
  Make sure your C++ compiler is configured to use the sub-directories
  present within this directory.

=== 2.2: Manual Installation / Installation on Windows ===

The manual installation is comprised of 3 steps:

* Step 1:
  Copy the entire "include" folder to a convenient location
  and tell your compiler to use that location for header files
  (in addition to the locations it uses already).
  Alternatively, you can use the "include" folder directly.

* Step 2:
  Modify "include/armadillo_bits/config.hpp" to indicate 
  which libraries are currently available on your system.
  For example, if you have LAPACK and BLAS present, 
  uncomment the following lines:
  #define ARMA_USE_BLAS

* Step 3:
  If you have LAPACK and/or BLAS present, configure your 
  compiler to link with these libraries. 
  If using Windows, see Section 3.2.
  If using Mac OS X, link using -framework Accelerate
  You can also link with high-speed replacements for LAPACK and BLAS,
  eg. Intel's MKL or AMD's ACML.  See Section 4.0 for more info.

=== 3.0: Compiling Programs and Linking: Examples ===

The "examples" directory contains several quick example programs
that use the Armadillo library. If Armadillo was installed manually
(ie. according to section 2.2), you will also need to explicitly
link your programs with the libraries that were specified in

"example1.cpp" may require the BLAS library or its equivalent.
"example2.cpp" requires the LAPACK library or its equivalent
(eg. the Accelerate framework on Mac OS X).

You may get errors at compile or run time if BLAS and/or LAPACK
functions are not available.

NOTE: As Armadillo is a template library, we recommended that
      optimisation is enabled during compilation. For example,
      for the GCC compiler use -O1 or -O2

=== 3.1: Compiling & Linking on Linux and Mac OS X ===

Please see "examples/Makefile", which may may need to be configured
for your system. If Armadillo header files were installed in a
non-standard location, you will need to modify "examples/Makefile"
to tell the compiler where they are.

In general, programs which use Armadillo are compiled along these lines:
  g++ example1.cpp -o example1 -O1 -larmadillo

(you may also need to specify the include directory via the -I switch)

If you get linking errors, or if Armadillo was installed manually
and you specified that LAPACK and BLAS are available, you will
need to explicitly link with LAPACK and BLAS (or their equivalents),
for example:
  g++ example1.cpp -o example1 -O1 -llapack -lblas

(you may also need to specify the library directory via the -L switch)


  * under most Linux systems, using "-llapack -lblas" should be enough;
    however, on Ubuntu and Debian you may need to add "-lgfortran"
  * under Mac OS X, try "-framework Accelerate" or "-llapack -lblas"
    (the Accelerate option is usually the fastest)
  * under the Sun Studio compiler, try "-library=sunperf"

=== 3.2: Compiling & Linking on Windows ===

As a courtesy, we've provided pre-compiled 32 bit versions of
standard LAPACK and BLAS for Windows, as well as MSVC project
files to compile example1.cpp and example2.cpp.
The project files are stored in the following folders:

The standard 32 bit versions of the LAPACK and BLAS libraries
are stored in:

If you're getting messages such as "use of LAPACK needs to be enabled",
you will need to manually modify "include/armadillo_bits/config.hpp"
to enable the use of LAPACK. See section 2.2 for more information.

Note that on 64 bit systems (such as Windows 7), dedicated
64 bit versions of BLAS and LAPACK are considerably faster.
If you don't have a 64 bit BLAS library, it's better to
explicitly disable the use of BLAS by defining ARMA_DONT_USE_BLAS
before including the armadillo header:

#include <armadillo>

The MSCV project files were tested on 32 bit Windows XP with
Visual C++ 2008 (Express Edition). You may need to make adaptations
for 64 bit systems, later versions of Windows and/or the compiler.
For example, you may have to enable or disable the ARMA_BLAS_LONG
and ARMA_BLAS_UNDERSCORE macros in "armadillo_bits/config.hpp".

The pre-compiled versions of LAPACK and BLAS were downloaded from:

If the provided libraries don't work for you, or you want more speed,
try these versions:

The MKL and ACML libraries are generally the fastest.
See Section 4.0 for more info on making Armadillo use MKL or ACML.

You can find the original sources for standard BLAS and LAPACK at:

We recommend the following high-quality compilers:

  * GCC (part MinGW)

  * GCC (part of CygWin)

  * Intel's C++ compiler

For the GCC compiler, use version 4.0 or later.
For Intel's C++ compiler, use version 10.0 or later.

For best results we recommend using an operating system that's
more reliable and more suitable for heavy duty work,
such as Mac OS X or the various flavours of Linux,
eg. Scientific Linux:

=== 4.0: Support for Intel MKL and AMD ACML ===

Armadillo can use Intel's Math Kernel Library (MKL) and the
AMD Core Math Library (ACML) as high-speed replacements for BLAS and LAPACK.

You may need to make minor modifications to "include/armadillo_bits/config.hpp"
in order to make sure Armadillo uses the same style of function names
as used by MKL or ACML. For example, the function names might be in capitals.

On Linux systems, ACML and MKL are typically installed in a
non-standard location, which can cause problems during linking.
Before installing Armadillo, the system should know where the ACML or MKL
libraries are located (eg. "/opt/intel/mkl/").
This can be achieved by setting the LD_LIBRARY_PATH environment variable,
or for a more permanent solution, adding the location of the libraries
to "/etc/". It may also be possible to store a text file 
with the location in the "/etc/" directory.
In the latter two cases you will need to run "ldconfig" afterwards.

The default installations of ACML 4.4.0 and MKL are known 
to have issues with SELinux, which is turned on by default in Fedora
(and possibly RHEL). The problem may manifest itself during run-time,
where the run-time linker reports permission problems.
It is possible to work around the problem by applying an appropriate
SELinux type to all ACML and MKL libraries.

If you have ACML or MKL installed and they are persistently giving
you problems during linking, you can disable the support for them
by editing the "CMakeLists.txt" file, deleting "CMakeCache.txt" and
re-running the CMake based installation. Specifically, comment out
the lines containing:

=== 4.1: Support for ATLAS ===

Armadillo can use the ATLAS library for faster versions of
certain LAPACK and BLAS functions. Not all ATLAS functions are
currently used, and as such LAPACK should still be installed.

The minimum recommended version of ATLAS is 3.8.
Old versions (eg. 3.6) can produce incorrect results
as well as corrupting memory, leading to random crashes.

Users of Ubuntu and Debian based systems should explicitly
check that version 3.6 is not installed. It's better to
remove the old version and use the standard LAPACK library.

=== 5: Documentation / Reference Manual ===

A reference manual (user documentation) is available at or in the "docs" folder of
this archive.  Use a web browser to open docs/index.html

The user documentation explains how to use Armadillo's
classes and functions, with snippets of example code.

=== 6: FAQs and Bug Reports ===

Answers to Frequently Asked Questions (FAQs) can be found at:

This library has gone through extensive testing and
has been successfully used in production environments.
However, as with almost all software, it's impossible
to guarantee 100% correct functionality.

If you find a bug in the library (or the documentation),
we are interested in hearing about it. Please make a small
self-contained program which exposes the bug and send the
program source (as well as the bug description) to the 
developers. The developers' contact details are available at:

=== 7: Credits ===

Main sponsoring organisation:

Main developers:
- Conrad Sanderson -
- Ian Cullinan
- Dimitrios Bouzas
- Stanislav Funiak

- Eric R. Anderson
- Benoît Bayol
- Salim Bcoin
- Justin Bedo
- Darius Braziunas
- Ted Campbell
- Chris Cooper
- Clement Creusot
- Ryan Curtin
- Chris Davey
- Dirk Eddelbuettel
- Romain Francois
- Piotr Gawron
- Charles Gretton
- Benjamin Herzog
- Edmund Highcock
- Kshitij Kulshreshtha
- Oka Kurniawan
- Simen Kvaal
- David Lawrence
- Jussi Lehtola
- Jeremy Mason
- Carlos Mendes
- Artem Novikov
- Martin Orlob
- Ken Panici
- Adam Piątyszek
- Jayden Platell
- Vikas Reddy
- Ola Rinta-Koski
- Boris Sabanin
- James Sanders
- Alexander Scherbatey
- Gerhard Schreiber
- Shane Stainsby
- Petter Strandmark
- Eric Jon Sundstrom
- Paul Torfs
- Simon Urbanek
- Arnold Wiliem
- Yong Kang Wong
- Buote Xu

=== 8: License ===

Please see the "LICENSE.txt" file.