Search Within Space:

Build Environment - Linux

Linux - NOTE: In all cases you MUST install a 32-bit OS (Either CentOS, Fedora, or Ubuntu)

The Linux build environment documented on this page is based on a basic Fedora Core 15 installation CD. There are CentOS 6- and Ubuntu-specific notes below. It should also be possible to use a previously existing Linux installation, assuming that you have all of the required packages described below. The following section describes how to set up a machine from scratch.

Preparing a System for Build

Install Fedora Core 15 i386 CD or CentOS 6.x or Ubuntu 12.04 LTS (64 bit not supported. Note specific platform notes below, and at bottom.)

  1. !* Choose and make note of the root password
    • Create your user (remember the password)
  2. Update the software on the system
    • System->Administration->Update System
      • If you get the following error "Transaction error could not add package update for <distro info>". The work around is typing the following on the command line:
        $su -
        $yum update
  3. Convert your user to a "sudoer"
    • Get a terminal window (Applications->System Tools->Terminal)
    • Type 'su -'  (no quotes)
    • Enter root password
    • Fedora, CentOS
      • visudo
      • add the following line toward the end of the file (assuming your user name was steve)
      • %steve ALL=(ALL) ALL
    • Ubuntu
      • Add user to "sudo" group in /etc/group in 12.04 LTS, or "admin" group in earlier versions, e.g.
        sudo:x:27:steve
        admin:x:25:steve
  4. Install all the required Linux packages  (CentOS, Fedora. See bottom for Ubuntu).
  5. Check the RI Code out to populate your machine
    • Start in your home directory ('cd ')
    • mkdir CableLabsRI
    • cd CableLabsRI
    • svn co https://community.cablelabs.com/svn/OCAPRI/trunk
    • Enter your credentials when prompted, then wait as it checks out the trunk. You now have the majority of the tree for Linux on your machine under /home/<user>/CableLabsRI/trunk
  6. Ensure SELinux is disabled  (CentOS, Fedora. Ubuntu does not install and enable SELinux by default.)
    • Activate menu by selecting System->Administration->SELinux Management
    • Enter root password
    • In Status Tab, set System Default Enforcing Mode to Disable
    • For Fedora 15 and CentOS:
      • sudo vi /etc/sysconfig/selinux
        change SELINUX=enforcing to SELINUX=disabled
         :wq (save and quit).
          You have to reboot the system for this to take effect.
  7. Install the Sun 1.6 Java Development Kit (Java SE JDK 6 Update XX)
    • Note: Installation of Sun's JDK is not necessary - the Open JDK has already been installed (and works).
      However, the Open JDK developer tools must be installed (i.e. the full JDK, not just the JRE):
      For CentOS: 
      yum install java-1.6.0-openjdk java-1.6.0-openjdk-devel

      For Ubuntu:
      See full apt-get command at bottom.

    • For Sun JDK:

    • Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html
    • Select latest JDK 6 Download
    • Select Platform: Linux Language: Multi-language, select checkbox accepting the License agreement
    • Select jdk_6uxx-linux-rpm.bin, and "Save File" when prompted
    • in ~/Download, do 'chmod +x jdk-6uxx-linux-i586-rpm.bin' (no quotes)
    • sudo ./jdk-6uxx-linux-i586-rpm.bin
    • Accept the license, and watch the jdk get installed
    • Ignore the registration
  8. Get ant 1.8 or later
  9. Edit your environment to get ready to build
    • Edit .bashrc in your home directory
    • Add the following lines to the end, replacing "steve" with your user name

Building Everything for the First Time

  1. Build the platform (the support code for the OCAP stack)
    • Start a new terminal session to pick up the environment changes you just made
    • cd $PLATFORMROOT
    • make clean purge build
  2. Build the OCAP stack (the Java VM and support libraries)
    • cd $OCAPROOT
    • ant clean
    • ant purge (this may fail due to a bug in the build script for now - ignore)
    • ant build
    • This should build the stack - Yahoo! Wait for complete with no errors
    • From this point forward, 'ant purge' should work, so you can do a super-clean build using 'ant clean purge build'

Subsequent Builds

  1. Building the platform (assuming you did not change the support libraries)
    • From $PLATFORMROOT do 'build source'

Required Linux Packages

You should first install all of the recommended additional packages that the Fedora system manager directs you to.

The following packages must be installed on your Linux system prior to building the RI Platform and Stack. You can download and install packages directly from Fedora. Click on System > Administration > Add/Remove Software. Sometimes you will need to look for older packages (e.g. Subversion 1.4). For those packages the Fedora Package Database can prove to be a valuable resource.

Package Name

Description

Known Working Version

Comments

gcc

GNU Compiler Collection

4.3.2-7

Installing this package will also install a lot of other packages such as binutils, glibc, etc

gcc-c++

C++ support for GCC

4.3.2-7

Installing this package will also install libstdc++-devel

 

make

GNU Build Tool

1.3.81-14

 

gettext

Mulit-lingual message library

0.17-8

 

patch

Utility for modifying/upgrading files

2.5.4-35

 

bison

Parser generator

2.3-5

 

flex

Tool for creating scanners

2.5.35-2

 

liboil

Library of Optimized Inner Loops

0.3.14-1

May already be installed

liboil-devel

Development files for liboil

0.3.14-1

 

zlib

ZLib compression/decompression library

1.2.3-18

May already be installed

zlib-devel

Headers and libs for zlib development

1.2.3-18

 

libxml2

Library providing XML and HTML support

2.7.3-1

May already be installed

libxml2-devel

Libraries for developing XML/HTML apps

2.7.3-1

 

doxygen

Documentation generator for C/C++

1.5.7.1-1

 

libX11-devel

X11 development package

1.1.4-6

Installing this package will install several other X11 development packages (including Mesa libGL)

libXext

X11 libXext runtime library

1.0.4-1

May already be installed

libXext-devel

X11 libXext development package

1.0.4-1

 

mesa-libGLU-devel

Mesa libGLU development package

7.2-0.15

 

atk

Accessibility support

1.24.0-1

May already be installed

atk-devel

ATK development libs

1.24.0-1

Installing this package will install several other packages

pango

Layout for internationalized text

1.22.3-1

 

pango-devel

Development libs for pango

1.22.3-1

 

cairo

Graphics library

1.8.0-1

 

cairo-devel

Development libs for cairo

1.8.0-1

 

libjpeg

JPEG libs

6b-43

 

libjpeg-devel

JPEG development libs

6b-43

 

libtiff

TIFF libs

3.8.2-11

 

libtiff-devel

TIFF development libs

3.8.2-11

 

man-pages

Lots of good man pages for Linux

3.09-2

Obviously, this is optional, but it installs man pages for glibc functions which are always helpful

perl-Net-Telnet

Telnet libraries for perl

3.03-7

Required for ATE Emulator

perl-Digest-SHA1

SHA1 libraries for perl

2.11.7

Required for ATE Emulator

pkg-config

Linux package configuration utility

 

ant

Ant make tool

1.8.0

Required to build the OCAP stack

ant-jdepend

Ant support libraries for dependency checking

1.7.1

Required to build the OCAP stack

vlc

Media Streamer/Player

0.9.9-2

Used by the RI Platform to play MPEG-2 transport streams from file

Add your user group to sudoers file

*(Fedora/CentOS-only) In order to run ATE tests, the RI Platform must be able to connect to certain network ports that are only available to processes running as root. To facilitate this, we have modified the runPlatform_linux.sh startup script to always execute the RI process as root. On Linux systems, non-root users must add their user group to a list of groups that are allowed to gain root privileges. The list of these groups is found in the /etc/sudoers file. Edit this file and add your user group to one of the two sections


Selecting a User Interface Target

On the Linux platform, there are currently two user interface targets:

  • Native libX11 Windows
  • wxWidgets Windows (default)

To build the native X11 Windows UI target, uncomment the line

UI_TARGET = Linux

in the target/Linux/debug/defs.mk file. To build for the cross-platform wxWidgets UI target, uncomment the line

UI_TARGET = wxWidgets

in the target/Linux/debug/defs.mk/ file. Make sure that the target you are NOT interested in is also commented out.

Ubuntu Specific Notes

Ubuntu 10.04.01 LTS, 10.10, the following command will install all prerequisite packages.

 


Ubuntu 11.04, 11.10 the following command will install all prerequisite packages.



Ubuntu 12.04 LTS prerequisite packages

fix SHA1.pm renaming issue

If you do a fresh install of 12.04 (as opposed to an upgrade from 11.x) and need build CTP test streams run:

 

All Ubuntu

Add these lines to ~/.bashrc:

export JAVA_HOME=/usr/lib/jvm/java-6-openjdk
export PATH=$PATH:~/atelite/bin

export ANT_HOME=/usr/share/ant

OR

export ANT_HOME=~/apache-ant-1.8.4

If you have scripts or other that use /bin/sh, configure to use bash instead of dash:

...and answer No

 

Labels
  • None
  1. Nov 30, 2011

    After setting up environments for both Win32-Cygwin and Ubuntu Linux, I am listing a few observations as well as the exact steps I finally ended up taking.  Thanks a lot to Mark, Chris and Nishant for helping me through all of my environment issues!

    1. RI platform build ($PLATFORMROOT) does not work on Ubuntu 11.10 due to some missing OpenGL libraries.  I changed to 11.4 and had no further issues.
    2. Instead of checking out the entire OCAPRI/trunk repository, use the following commands.  These operations will make the SVN checkouts much quicker and environment variable setup much easier.  Should any builds fail, the svn checkout may have missed copying over some files so you may need to do an "svn update".
            • RI build
            • svn co -N https://community.cablelabs.com/svn/OCAPRI
            • cd OCAPRI
            • ./checkout_dev_env.sh trunk (checks out necessary svn directories and creates the "setEnv" script
            • cd trunk
            • . ./setEnv (creates necessary shell environment variables)
            • cd $PLATFORMROOT
            • make clean purge build
            • OCAP Stack Build
            • ensure JAVA_HOME and ANT_HOME are set.  This may be potentially avoided if the executables "javac" and "ant" are located within your shell's path.
            • cd $OCAPROOT
            • ant clean purge build
    3. Test to ensure your RI has been installed correctly by running a tuner test which should stream a video of a baby.
      • cd $PLATFORMROOT
      • ./runRI.sh -tunetest -setup
    4. After building from source, you should be able to start the RI for use against a locally running ATE daemon via the command "./runRI.sh -ate -setup" (note: the binary distribution of the RI will not work properly with the ATE).

    Regarding OS setup, do not forget to retrieve all the necessary libraries for the platform of your choice.  Should one be omitted, you could have a build failure that may not overtly spelled out by the build logs.