3.1. Automatic installation
Download the software from the developer site: http://developer.axis.com. An Internet connection is required on the computer intended for the installation.
Download and unpack the devboard-R2_01.tar.gz file. The devboard-R2_01.tar.gz file contains basic scripts needed for installing the SDK (e.g. "tar -xvfz devboard-R2_01.tar.gz").
3.1.2. Run install script
Enter the newly created "devboard-R2_01" directory and run the install script. This will download and install tools and source code needed to configure the SDK in the next step.
First you will be confronted with a question if you would like to copy distribution files from an earlier SDK installation. Provided that you have a fairly new SDK release, copying files will reduce the number of packages needed to be downloaded. If unsure, just skip this step.
At the end of the install script you will be asked which product to use. This selection determines which configuration files to be used. Select a product that resembles your hardware.
"./install"
3.1.3. Configuration (Optional, but recommended)
To be able to control which packages to include, run any of the configuration targets (menuconfig, xconfig, config) to generate a custom configuration.
In most cases, it is recommended to run these configuration targets since the default configuration only includes a subset of all available packages. Configure the SDK according to your needs or skip this step to use the default configuration.
"make menuconfig" (or "make config" or "make xconfig")
3.1.4. Download and install packages
Download and install all packages needed for your configuration. This is performed by the configure script that also generates the top-level Makefile, used in the next step.
"./configure"
Now your SDK tree should be complete for your current configuration. To build the images run make.
"make"
3.2. Tarball installation
A tarball installation involves using two tarballs where the user has to extract these tarballs. This method does not require an Internet connection on the computed intended for the installation, but you still need access to the tarballs.
3.2.1. Download the tarballs
Make sure that you have downloaded both devboard-R2_01.tar.gz and devboard-R2_01-distfiles.tar.gz. Unpack the devboard-R2_01.tar.gz file. Then unpack the devboard-distfiles-R2_01.tar.gz. This will create a folder named distfiles which contain all packages needed for the installation. Then make a symbolic link inside the devboard-R2_01 folder pointing to this distfiles directory.
"tar xvfz devboard-R2_01.tar.gz"
"tar xvfz devboard-R2_01-distfiles.tar.gz"
"cd devboard-R2_01"
"ln -s ../distfiles"
3.2.2. Run install script
Enter the newly created "devboard-R2_01" directory and run the install script. This will install tools and source code needed to configure the SDK in the next step.
First you will be confronted with a question if you would like to copy distribution files from an earlier SDK installation. Since you already copied the files when installing the second tarball answer "n" here.
At the end of the install script you will be asked which product to use. This selection determines which configuration files to be used. Select a product that resembles your hardware.
"./install"
3.2.3. Configuration (Optional, but recommended)
To be able to control which packages to include, run any of the configuration targets (menuconfig, xconfig, config) to generate a custom configuration.
In most cases this is recommended to run these configuration targets since the default configuration only includes a subset of all available packages. Configure the SDK according to your needs or skip this step to use the default configuration.
"make menuconfig" (or "make config" or "make xconfig")
Install all packages needed for your configuration. This is performed by the configure script that also generates the top-level Makefile, used in the next step.
"./configure"
Now your SDK tree should be complete for your current configuration. To build the images run make.
"make"
For further guidance on how to work with your SDK, e.g., adding custom applications, consult the documentation page on http://developer.axis.com.
