These instructions are designed so that you can quickly copy and paste the commands into a terminal window and get a development environment configured for Ubuntu 8.04.
Some commands require sudo privileges so that system wide packages can be installed. Therefore, these steps should be run by a user that has administrative privileges on the computer. On Ubuntu, these users are members of the "admin" group. By default the first user on the system is added to the admin group.
Use these commands to install the packages necessary for elisa development.
# Packages needed by pigment
sudo aptitude install subversion autoconf automake libglib2.0-dev \
libgtk2.0-dev gtk-doc-tools libgstreamer0.10-dev \
libgstreamer-plugins-base0.10-dev libx11-dev libgl1-mesa-dev \
libpango1.0-dev libcairo2-dev
# Packages needed by pigment-python
sudo aptitude install python2.5-dev python-gobject-dev python-gst0.10
# Packages needed by elisa
sudo aptitude install bzr python-setuptools python-twisted-bin \
python-twisted-core python-twisted-web python-twisted-web2 \
python-openssl python-gtk2 python-cairo python-pymetar \
python-simplejson python-avahi python-twill
Install cssutils and coherence using the easy install tool that comes bundled with python-setuptools.
sudo easy_install cssutils coherence
Create a directory for your branches. We will use Projects/elisa-branches in our home directory.
mkdir -p ~/Projects/elisa-branches
Checkout the development branch.
cd ~/Projects/elisa-branches
bzr branch lp:elisa
Setup pigment. These commands will check out a development version of pigment, compile it, run the interactive pigment shell, and compile the python bindings for pigment. The pigment shell allows us to use pigment without performing a system-wide installation.
cd ~/Projects
svn co https://code.fluendo.com/pigment/svn/trunk pigment
cd pigment/pigment
./autogen.sh
make
./misc/pgm-uninstalled
cd ../pigment-python
./autogen.sh
make
Important Note: You will need to run the pgm-uninstalled script in the terminal window where you will be launching elisa once before running elisa. The commands above have already started the interactive shell so we don't need to run the command again. However, it is important that you remember to run the shell for each new terminal that you use.
If you fail to run this before trying to run elisa in a terminal then you will only see a black screen when elisa runs. You only need to run it once in the terminal. It will update your prompt to show [pigment] at the beginning when it is configured.
Here is the command to setup the pigment shell:
~/Projects/pigment/pigment/misc/pgm-uninstalled
Setup your path.
cd ~/Projects/elisa-branches/elisa
export PYTHONPATH=$PWD/elisa-core:$PWD/elisa-plugins:$PYTHONPATH
Verify that elisa is configured correctly:
python -c "import elisa"
You should not see any output if everything is setup correctly. If you get an error like "ImportError: No module named elisa", then something is not correctly setup. Go back and verify that you have completed the steps correctly.
Try running the branch. We run elisa with a configuration file that doesn't exist so that elisa will create a new configuration file.
python elisa-core/bin/elisa my_conf.conf
If you don't get any output when running the command, then you can try running elisa with more debugging comments turned on by using this command.
ELISA_DEBUG=5 python elisa-core/bin/elisa my_conf.conf
You should now be configured for development. Head over to http://elisa.fluendo.com/documentation/ and give the tutorials a try.
If you run into problems configuring your environment, then let us know. You can get help by using the mailing list, forums, wiki or irc. Check out the links to our help options at the bottom of the page http://elisa.fluendo.com/participate/.