Among the many possible build systems on Linux we suggest using ArrayFire with either CMake or Makefiles with CMake being the preferred build system.

Pre-requisites

Before you get started, make sure you have the necessary pre-requisites.

If you are using CUDA, please make sure you have CUDA 7 installed on your system.
- Contact us for custom builds (eg. different toolkits)
If you are using OpenCL, please make sure you have one of the following SDKs.

You will also need the following dependencies to use ArrayFire.

Fedora, Centos and Redhat

Install EPEL repo (not required for Fedora)

1 yum install epel-release

2 yum update

Install the common dependencies

1 yum install gcc gcc-c++ cmake make

2 yum install freeimage

Install glfw (not required for no-gl installers)

Fedora:

1 yum install glfw

For Centos and Redhat, please follow these instructions

Debian and Ubuntu

Install common dependencies

1 apt-get install build-essential cmake cmake-curses-gui

2 apt-get libfreeimage3

Install glfw (not required for no-gl installers)

1 apt-get install libglfw3

For Debian 7 and Ubuntu 14.04, please follow these instructions

Special instructions for Tegra-K1

1 sudo apt-get install libatlas3gf-base libatlas-dev libfftw3-dev liblapacke-dev

CMake

This is the suggested method of using ArrayFire on Linux. ArrayFire ships with support for CMake by default, including a series of Find scripts installed in the /usr/local/share/ArrayFire/cmake (or similar) directory. These scripts will automatically find the CUDA, OpenCL, and CPU versions of ArrayFire and automatically choose the most powerful installed backend (typically CUDA).

To use ArrayFire, simply insert the FIND_PACKAGE command inside of your CMakeLists.txt file as follows:

FIND_PACKAGE(ArrayFire)
INCLUDE_DIRECTORIES(${ArrayFire_INCLUDE_DIRS})
...

ADD_EXECUTABLE(some_executable ...)
TARGET_LINK_LIBRARIES(some_executable ${ArrayFire_LIBRARIES} )

The find script will automatically define several variables including:

ArrayFire_INCLUDE_DIRS    - Location of ArrayFire's include directory.
ArrayFire_LIBRARIES       - Location of ArrayFire's libraries. This will default
                            to a GPU backend if one
ArrayFire_FOUND           - True if ArrayFire has been located

If you wish to use a specific backend, the find script also defines these variables:

ArrayFire_CPU_FOUND        - True of the ArrayFire CPU library has been found.
ArrayFire_CPU_LIBRARIES    - Location of ArrayFire's CPU library, if found
ArrayFire_CUDA_FOUND       - True of the ArrayFire CUDA library has been found.
ArrayFire_CUDA_LIBRARIES   - Location of ArrayFire's CUDA library, if found
ArrayFire_OpenCL_FOUND     - True of the ArrayFire OpenCL library has been found.
ArrayFire_OpenCL_LIBRARIES - Location of ArrayFire's OpenCL library, if found

Therefore, if you wish to target a specific specific backend, switch ${ArrayFire_LIBRARIES} to ${ArrayFire_CPU} ${ArrayFire_OPENCL} or ${ArrayFire_CUDA} in the TARGET_LINK_LIBRARIES command above.

Finally, if you have installed ArrayFire to a non-standard location, CMake can still help you out. When you execute CMake specify the path to the ArrayFireConfig* files that are found in the share/ArrayFire/cmake subdirectory of the installation folder. For example, if ArrayFire were installed locally to /opt/ArrayFire then you would modify the cmake command above to contain the following definition:

``` cmake -DArrayFire_DIR=/opt/ArrayFire/share/ArrayFire/cmake ... ```

MakeFiles

Using ArrayFire with Makefiles is almost as easy as CMake, but you will need to specify paths manually. In your makefile specify the include path to the directory containing arrayfire.h. Typically this will be -I /usr/include or -I /usr/local/include if you installed ArrayFire using our installation instructions. Then, in your linker line specify the path to ArrayFire using the -L option (typically -L/usr/lib or -L/usr/local/lib and the specific ArrayFire backend you wish to use with the -l option (i.e. -lafcpu, -lafopencl or -lafcuda for the CPU, OpenCL and CUDA backends repsectively).

Here is a minimial example MakeFile which uses ArrayFire's CPU backend:

LIBS=-lafcpu
LIB_PATHS=/usr/lib
INCLUDES=-I/usr/include
CC=g++ $(COMPILER_OPTIONS)
COMPILER_OPTIONS=-std=c++11 -g

all: main.cpp Makefile
    $(CC) main.cpp -o test $(INCLUDES) $(LIBS) $(LIB_PATHS)