The current viewer codebase includes AlexIvy components from Linden Lab. This code does not compile in Linux. Developers are working on the code to make it compile correctly. New procedures will be published
There is no official support for compiling or operating self-compiled viewers. There may be unofficial support as listed at the bottom of this page.

This procedure is used for building a non-standalone viewer on 32-bit Ubuntu systems and was verified on LinuxMint 17.1. (variant of Ubuntu 14.04LTS). This procedure assumes that your Ubuntu system has been properly updated, and also assumes any derivative system (eg.: Mint) includes all the standard Ubuntu libraries.

Establish your programming environment

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

Install Required Tools

The required tools are:

bison bzip2 cmake curl flex g++ 4.8 or newer m4 (for make) mercurial (for hg) python newer than 2.4.3 but not 3.0 python development pip
sudo apt-get update # to make sure the repository list is current
sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends bison bzip2 cmake curl flex g++ m4 mercurial python python-dev python-pip

(the –install-recommends flag tells apt-get to install all packages recommended by each named package.)

Install Required Libraries

These libraries may be included with your distribution, and some may be automatically installed as dependencies for the tools you just installed: (libc6-dev) (libgl1-mesa-dev) (libglu1-mesa-dev) (libstdc++6) (libX11-dev) (libxinerama-dev ) (libxml2-dev) (libxrender-dev)
sudo apt-get install --install-recommends libc6-dev libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \
  libX11-dev libxinerama-dev libxml2-dev libxrender-dev 

Install Autobuild

Autobuild is a Linden Lab resource that does all the hard work. For Firestorm, you will need a modified version of autobuild.

sudo pip install hg+

Set up your source code tree

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. This document will refer to src in your hole directory, ~/src.

cd ~/src

There are several repositories but the one we are after is the development repository. You can grab all the sources if you wish, but but keep in mind that each FS source requires around 110MB initially and around 4.3GB after the binaries have been built, plus possible compiling overhead.

hg clone

It will create a folder called phoenix-firestorm-lgpl. You can choose a different destination folder by adding that folder's name to the end of the command, such as:

hg clone firestorm-source

The rest of this document will assume the default directory, phoenix-firestorm-lgpl

Cloning the Firestorm repository can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help:
cd ~/src
hg clone -r 10000
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
	echo "Grabbing to change $i"
	hg pull -u -r $i
echo "Grabbing to tip"
hg pull -u
cd ~/src

Configuring the Viewer

cd ~/src/phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open

This will set up to compile with all defaults and without third party libraries. It will fetch any additional necessary libraries.

Configuration Switches

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

  • LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
    more of them.
  • clean will cause autobuild to remove any previously compiled objects and fetched packages. It can be useful if you need to force a reload of all packages
  • package will result in a bzip2 archive of the completed viewer. Enabled by default, you would have to use -DPACKAGE:BOOL=Off to disable it

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE


autobuild configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -c ReleaseFS_open -- --clean

The first time you configure, several additional files will be downloaded from Firestorm and Second Life sources. These are mostly binary packages maintained outside the viewer development itself. And if you use the –clean switch, you will re-download them all.

Compiling the Viewer

autobuild build -c ReleaseFS_open

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Running your newly built viewer

Running from a menu item

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged/etc

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

Running from command line or file browser

cd ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged

"Installing" the viewer

You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged to another location if you choose, and then launch firestorm from there. Example:

mkdir ~/Firestorm
cp -a ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/ to create a desktop launcher


Handling problems

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

  • IRC: The #phoenixviewer-dev channel is the best place to look for solutions.
    A lot of self-compilers and project developers hang out there and are ready to help you.
  • Jira: JIRA may contain resolved tickets.
    Search using the error you encountered.
  • Included documentation: In the Firestorm root folder are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date.

If you found a procedural error in this document, please let us know in as much detail as you can, either contact the author (preferred) or discuss on IRC.

Common Issues/Bugs/Glitches And Solutions

  • Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Ubuntu repositories, so make sure you did not disable those. If you find that a library or application is in a different package for your system, contact the team with the name of the library or application, the name of its package and your Linux OS so that information can be checked and added here.
  • Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet
  • Voice Won't Connect It was observed in testing that voice would not connect and no devices could be selected in Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings. This was resolved by replacing Firestorm/lib/ with a copy from release.
  • fs_compiling_firestorm_32bit_ubuntu.txt
  • Last modified: 2018/05/11 15:52
  • by miro.collas