Required host system:
We use Debian for building the firmware images, so the buildsystem (OpenADK)
has a strong dependency on Debian. These versions are tested with Debian 8.2
AMD64, you really need the 64bit version.

The easiest way to get everything you need to build the firmware images is to do
a standard installation (I like Mate desktop + ssh + standard system tools).
Then install following packages to build x86 based images:
- build-essential (gcc, binutils ...), g++
- autotools (automake, autoconf, configure ...)
- ed
- genisoimage
- gawk
- pkg-config
- bison, flex
- libtool
- squashfs-tools
- zlib1g, zlib1g-dev
- libncurses-dev
- module-init-tools

If you want to build the ARM based version you have to install some more
packages:
- elfutils, libelf-dev
- libiberty-dev
- libasm1, libdw1, libdw-dev
- u-boot-tools

1. Get the version (tarball) you want to build.
2. Get the tarballs from our tarball pool listed in the REQUIRED_TARBALLS list.
   You really need these tarballs, because some of the differ from the original
   versions and some are very hard to find. You have to put the tarballs in a
   directory called "dl" in the OpenADK directory.
3. Copy the CONFIG.bak file to .config.
4. Run "make prereq" to set the prerequirements of OpenADK.
5. Run "make" to start the build processs. You can use the "-j" options here
   to set the buildjobs that can run in parallel.
6. If you build for x86 then the final firmware image is the ISO file
   "bin/viprinux_i686_glibc/iso_image.iso" in the OpenADK directory.
   If you build for ARM then the final firmware image is the YAFFS2 file
   "bin/viprinux_arm_glibc/initial_image.yaffs2".

The build run will not complete, because these archives contain the open source
components only. The affected packages are SierraLinuxQMIdrivers,
viprinux-base-files, viprinux-debugger-base-files, viprinux-initramfs-files,
viprinux-oprofile-base-files, viprinux-proprietary-base-files,
viprinux-wifi-base-files and vipriusb.