This window displays the Environment assets that you have in your inventory. These include those you have acquired (shown in your Inventory → Settings folder) and those provided by Linden Lab (shown in your Library → Environments folder).

The three Environment asset types are Days, Skies, and Water.

• Days, Skies, Water: These three checkboxes are filters that determine which of the three are displayed in this window.
• Double-click on an Environment asset to open its edit window.
• Right click on an Environment asset for its menu.
• Show All Folders: This displays all Inventory folders, whether or not they contain Environment assets.
• Gear menu: Gives various options for the currently selected Environment asset, most of which are also in the item's right-click menu.
• “+” Symbol: Click to create a new Day, Sky, or Water asset.

This page describes all necessary steps to build the Firestorm viewer for Windows, using the updated build infrastructure introduced with Linden Lab's project Alex Ivy and the latest tools update.

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

All installations are done with default settings (unless told explicitly) - if you change that, you're on your own!

• Install Windows 10 64bit using your own product key
• Alternatively: Install 8.1 Pro 64bit

• Install Visual Studio 2017
• Note: If you don't own a copy of a commercial edition of Visual Studio 2017 (e.g. Professional), you might consider installing the Community version (requires creating a Microsoft account if you do not already have one)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • Check “Desktop development with C++” on the “Workloads” tab.
  • All other workload options can be unchecked

• Download and install TortoiseGit 2.9.0 or newer (64bit)
  • Note: No option available to install as Administrator
  • Use default options (path, components etc.) for Tortoise Git itself
  • At some point, it will ask you to download and install Git for Windows
    • You can install with default options EXCEPT when it asks for “Configuring the line endings conversion”: You MUST select “Checkout as-is, commit as-is” here!

• Download and install at least CMake 3.8.0
  • Run the installer as Administrator (right click, “Run as administrator”)
  • At the “Install options” screen, select “Add CMake to the system PATH for all users”
  • For everything else, use the default options (path, etc.)
  • Make sure that the following directory was added to your path:

    C:\Program Files (x86)\CMake\bin

• Download and install Cygwin 64 (64bit)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • Use default options (path, components etc.) *until* you get to the “Select Packages” screen
  • Add additional packages:
    • Devel/patch
  • Use default options for everything else
  • Make sure that the following directory was added to your path.:

    C:\Cygwin64\bin

• Download and install the most recent version of Python 2.7 (32bit)
  • Linden Lab advises to use the 32bit version as the VMP requires it. However, Firestorm currently doesn't use VMP, so the 64bit version might work (use at own risk!)
  • Note: No option available to install as Administrator
  • Use default options (path, components etc.) until you get to the “Customize Python” screen
  • Change “Add python.exe to Path” to “Will be installed on local hard drive”
  • Add the Python installation dir to the system path:

    C:\Python27

Confirm things are installed properly so far by opening a Cygwin terminal and enter:

cmake --version
git --version
python --version

If they all report sensible values and not “Command not found” errors, then you are in good shape.

• Install Boostrip pip
  • Download (Save As) get-pip.py and copy to a temp folder
  • Open Windows Command Prompt
  • Switch to that temp folder and execute it:

    python get-pip.py

  • Pip will be installed
  • Add the following directory to your path:

    C:\Python27\Scripts

• Install Autobuild
  • Open Windows Command Prompt and enter:

    pip install git+https://vcs.firestormviewer.org/autobuild-1.1#egg=autobuild

  • Autobuild will be installed. Earlier versions of Autobuild could be made to work by just putting the source files into your path correctly; this is no longer true - Autobuild must be installed as described here.

• Set environment variable AUTOBUILD_VSVER to 150

• Check Autobuild version to be 1.1.8 or higher:

  autobuild --version

• If you plan to package the viewer and create an installer file, you must install the NSIS from the official website.
• Not required unless you need to build an actual viewer installer for distribution, or change the NSIS installer package logic itself

In order to make it easier to build collections of related packages (such as the viewer and all the library packages that it imports) with the same compilation options, Autobuild expects a file of variable definitions. This can be set using the environmenat variable AUTOBUILD_VARIABLES_FILE.

• Clone the build variables repository:

  git clone https://vcs.firestormviewer.org/fs-build-variables <path-to-your-variables-file>

• Set the environment variable AUTOBUILD_VARIABLES_FILE to

  <path-to-your-variables-file>\variables

• Start the IDE
• Navigate to Tools> Options> Projects and Solutions> Build and Run and set maximum number of parallel projects builds to 1.

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. For this document, it is assumed that you created a folder c:\firestorm.

c:
cd \firestorm
git clone https://vcs.firestormviewer.org/phoenix-firestorm

This can take a bit, it's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

If you want to use FMOD Studio to play sounds within the viewer, you will have to download your own copy. FMOD Studio can be downloaded here (requires creating an account to access the download section).

c:
cd \firestorm
git clone https://vcs.firestormviewer.org/3p-libraries/3p-fmodstudio

• After you have cloned the repository, copy the downloaded FMOD Studio installer file to C:\Firestorm\3p-fmodstudio
• If you downloaded a different version of FMOD Studio that is currently used in the viewer, you will have to modify the file build-cmd.sh in the root of the repository. Right at the top, you find the version number of FMOD Studio you want to package (one short version without separator and one long version). Change these values to the version you downloaded:

FMOD_VERSION="20102"
FMOD_VERSION_PRETTY="2.01.02"

Continue on the Windows command line:

c:
cd \firestorm\3p-fmodstudio
autobuild build --all
autobuild package

While running the Autobuild build command, Windows might ask if you want to allow making changes to the computer. This is because of the FMOD Studio installer being executed. Allow these changes to be made.

Near the end of the output you will see the package name written and the md5 hash below it:

wrote C:\firestorm\3p-fmodstudio\fmodstudio-{version#}-windows-{build_id}.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

where {version#} is the version of FMOD Studio (like 2.01.02) and {build_id} is an internal build id of the package.

cd \firestorm\phoenix-firestorm
cp autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Copy the FMOD Studio path and md5 value from the package process into this command:

autobuild installables edit fmodstudio platform=windows hash=<md5 value> url=file:///<fmodstudio path>

For example:

autobuild installables edit fmodstudio platform=windows hash=a0d1821154e7ce5c418e3cdc2f26f3fc url=file:///C:\firestorm\3p-fmodstudio\fmodstudio-2.01.02-windows-192171947.tar.bz2

Open the Windows command prompt.

If you are building with FMOD Studio and have followed the previous FMOD Studio setup instructions AND you are now using a new terminal you will need to reset the environment variable first by entering

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then enter:

 c:
 cd \firestorm\phoenix-firestorm
 autobuild configure -c ReleaseFS_open

This will configure Firestorm to be built with all defaults and without third party libraries.

autobuild configure -v -c ReleaseFS_open

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.

• -A <architecture> sets the target architecture, that is if you want to build a 32bit or 64bit viewer (32bit is default if omitted).
• –fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps in FMOD Studio using Autobuild for this to work.
• –package makes sure all files are copied into viewers output directory. You won't be able to start your compiled viewer if you don't enable package or do 'compile' it in VS.
• –chan <channel name> lets you define a custom channel name for the viewer
• -LL_TESTS:BOOL=<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.

Examples:

• To build a 32bit viewer with FMOD Studio and to create an installer package, run this command in the Windows command window:

  autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

• To build a 64bit viewer without FMOD Studio and without installer package, run this command:

  autobuild configure -A 64 -c ReleaseFS_open -- --chan MyViewer -DLL_TESTS:BOOL=FALSE

There are two ways to build the viewer: Via Windows command line or from within Visual Studio.

If you are building with FMOD Studio and have followed the previous FMOD Studio setup instructions AND you are now using a new terminal you will need to reset the environment variable with

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then run the Autobuild build command. Make sure you include the same architecture parameter you used while configuring the viewer:

autobuild build -A 64 -c ReleaseFS_open --no-configure

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling will take quite a bit of time.

Inside the Firestorm source folder, you will find a folder named build-vc150-<architecture>, with <architecture> either being 32 or 64, depending on what you chose during the configuration step. Inside the folder is the Visual Studio solution file for Firestorm, called Firestorm.sln.

• Double-click Firestorm.sln to open the Firestorm solution in Visual Studio.
• From the menu, choose Build → Build Solution
• Wait until the build is finished

Older versions of the viewer before the merge of Linden Lab's project Alex Ivy use Autobuild 1.0 that is incompatible with the build process as it is now. By default it is not possible to install two different versions of Autobuild on the same computer at the same time. Making use of virtualenv will overcome this problem, allowing simultaneous installations of Autobuild 1.0 and Autobuild 1.1 in two distinct “virtual” Python environments.

Install virtualenv by opening a Windows command prompt and enter:

pip install virtualenv

This requires the Boostrip pip already installed. After virtualenv has been installed, you can create virtual Python environments using the command

virtualenv <virtual-environment-name>

This will create the directory <virtual-environment-name> within the Python installation folder and add some required folders and files. Among these files is a batch file called activate.bat in the folder Scripts. To switch to the newly created virtual environment execute the activate.bat batch file. After switching to the virtual environment, your command prompt will be prepended by the name of the virtual environment.

In this example we will create a virtual environment called “Autobuild11”:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat

Your command prompt should look like this now:

(Autobuild11) C:\

After you switched to a particular virtual environment, you can now install as described in Set up Autobuild and Python.

Complete example:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat
pip install hg+https://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild

Configuring and building the viewer from the Windows command line is basically identical as described in Building from the Windows command line with the difference that you now have to call the activate script first:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE
autobuild build -A 64 -c ReleaseFS_open --no-configure

If you plan to build the viewer from within Visual Studio, you will have to configure the viewer the same way as if you were to build from the Windows command line:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

To be able to build from Visual Studio, you will have to set a Windows environment variable called VIRTUAL_ENV pointing at the virtual Python environment to use, in our example “C:\Python27\Autobuild11”. Now open the Firestorm Visual Studio solution to start Visual Studio and build the viewer.

When trying to execute the Autobuild build command, you might encounter an error similar to

../build.cmd.sh line 200: SystemRootsystem32: unbound variable

This error is caused by the order of the items in the Windows “path” environment variable. Autobuild exports all paths set in the “path” environment variable into Cygpath names and variables. Since these Windows “paths” can also contain variables like %SystemRoot% and they can also depend on each other, it is important to keep the dependency order intact. Example:

%SystemRoot%
%SystemRoot%\system32
%SystemRoot%\System32\Wbem

The following screenshot shows the correctly ordered paths containing variables and depending on each other.

In this tab, you can set specific day cycle, sky, or water settings for your parcel, or create a day cycle ad-hoc.

• Use Default Settings
• Use Inventory: Click this to select a predefined day cycle, sky, or water asset from your inventory.
• Customize: Allows you to create an ad-hoc day cycle for the parcel. Refer to this page for information on creating a day setting.

How many (real) hours the day cycle is to last. “Legacy” SL days are 4 hours long, but you can use any value here from 4 to 168.

If you want a day cycle that matches the Legacy day cycle of 3 hours daylight, and 1 hour night, refer here.

Offset from UTC. The default is -8, which is SL time, or Pacific time.

An indication of the apparent time of day, based on the day asset in use, and the current time of day (sun position).

Shows what sky and water assets are in use for the day cycle assigned to the parcel. The sky heights here cannot be changed; they are indicative only.

• Sky 4 3000m
• Sky 3 2000m
• Sky 2 1000m
• Ground
• Water

This is a powerful set of tools for SL photographers and machinima makers. It combines a large number of settings from many places, into a single, multi-tabbed window.

This is accessed via a button on the button bar. If you do not have the button visible, right click any button on the button bar, and select Toolbar Buttons; the Toolbar Buttons window opens. Locate the Phototools button there, and drag it onto any of the button bars (bottom, left or right). Alternately, you can access via top menu, World → Photo and Video → Phototools.

These settings are separate for each account logging in with Firestorm.

Firestorm 6.4.5 (60799) Prerelease Notes

“n/a” in the table below means “not available”; see the boxed note above.

Firestorm 6.4.5 (60799) Prerelease Notes

“n/a” in the table below means “not available”; see the boxed note above.

• 64-bit Debian 8.x (jessie) - AlexIvy updated 2019/09/11
• 64-bit Debian 9.x (stretch) updated 2019/09/11
• 64-bit Debian 9.x (stretch) - AlexIvy updated 2019/09/11
• 64-bit Ubuntu 14.04 updated 2019/09/11
• 64-bit Ubuntu 16.04 updated 2019/09/11
• 64-bit Ubuntu 16.04 (AlexIvy) updated 2019/09/11
• Gentoo

This procedure is used for building a 64-bit viewer on 64-bit Debian systems and was tested and verified on Debian 8.11. This procedure assumes that your system has been properly updated.

This procedure may not work on older versions of Debian, nor has it been tested on any other version of Debian or any other distribution/variant/derivative.

The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommded 8GB or more RAM, quad-core CPU and 32GB available HDD space.

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

The required tools, some of which may already be installed, are:

make | g++ | gdb | mercurial (for hg) | python2.7 | python-pip

sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends make g++ gdb mercurial python2.7 python-pip

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

Do not install cmake from the repositories, Debian 8 comes with too old of a version, we will be downloading and installing a newer version from cmake's website.

These libraries may be included with your distribution, and some may already be installed:

sudo apt-get install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild from Linden Lab, version 1.1 or above.

sudo pip install --upgrade pip
sudo pip install autobuild

This will install autobuild and add a link in the exec path.

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. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one wea re 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 https://hg.firestormviewer.org/phoenix-firestorm-lgpl

It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

hg clone https://hg.firestormviewer.org/phoenix-firestorm-lgpl firestorm-source

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 https://hg.firestormviewer.org/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.

cd ~src
hg clone https://hg.firestormviewer.org/fs-build-variables/

Because Debian 8 comes with cmake version 3.0 and cmake 3.8 is the minimum needed to build the viewer, we will download the prebuilt version of cmake 3.15.3.

cd ~src
wget https://github.com/Kitware/CMake/releases/download/v3.15.3/cmake-3.15.3-Linux-x86_64.tar.gz
tar xf cmake-3.15.3-Linux-x86_64.tar.gz
PATH=$PATH:~/src/cmake-3.15.3-Linux-x86_64/bin/
export PATH

Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.

cd ~/src/phoenix-firestorm-lgpl
export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

Unlike previous versions of autobuild, version 1.1 requires the address size switch (-A) after the command, not before it. If you want a 32-bit build, you must specify that; there is no longer a default.

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

This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.

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

Examples:

autobuild configure -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -c ReleaseFS_open -- --clean
autobuild configure -A 64 -c ReleaseFS_open -- --chan="MyBuild"

In the last example, the channel and resulting viewer name would be “Firestorm-MyBuild”.

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

autobuild build -A 64 -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 -A 64 -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

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

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

You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/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-x86_64/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

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.

• 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 Debian 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

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

This procedure is used for building a 64-bit viewer on 64-bit Debian systems and was tested and verified on Debian 9.3. This procedure assumes that your system has been properly updated.

This procedure may not work on older versions of Debian, nor has it been tested on any other version of Debian or any other distribution/variant/derivative.

The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommded 8GB or more RAM, quad-core CPU and 32GB available HDD space.

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

Firestorm requires version 4.9 or 4.8 of the gcc/g++ compiler. This is not available in Debian 9's default repositories, so we need to add a Jessie repo.

sudo echo "deb http://ftp.us.debian.org/debian/ jessie main" >> /etc/apt/sources.list
sudo apt update

The required tools, some of which may already be installed, are:

sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends moreutils bison bzip2 cmake curl doxygen flex g++-4.9 gdb m4 mercurial python python-pip

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

The build environment need to know to use gcc 4.9:

sudo update-alternatives --remove-all gcc
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 49 \
--slave /usr/bin/g++ g++ /usr/bin/g++-4.9 \
--slave /usr/bin/gcov gcov /usr/bin/gcov-4.9
sudo update-alternatives --config gcc

Note that this will “hide” the current gcc from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.

These libraries may be included with your distribution, and some may already be installed:

sudo apt-get install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that does all the hard work. The 64-bit version requires a modified autobuild package, which our Nicky Djasmin has provided.

pip install --upgrade pip
pip install llbase
pip install hg+https://bitbucket.org/NickyD/autobuild-1.0#egg=autobuild

This will install autobuild and add a link in the exec path

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. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one wea re 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 https://hg.firestormviewer.org/phoenix-firestorm-lgpl

It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

hg clone https://hg.firestormviewer.org/phoenix-firestorm-lgpl firestorm-source

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 https://hg.firestormviewer.org/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

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

This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.

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

Examples:

autobuild -m64 configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild -m64 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 outisde the viewer development itself. And if you use the –clean switch, you will re-download them all.

autobuild -m64 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 -m64 build -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

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

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

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-x86_64/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

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.

• 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

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

This procedure is used for building a 64-bit viewer on 64-bit Debian systems and was tested and verified on Debian 9.3. This procedure assumes that your system has been properly updated.

This procedure may not work on older versions of Debian, nor has it been tested on any other version of Debian or any other distribution/variant/derivative.

The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommded 8GB or more RAM, quad-core CPU and 32GB available HDD space.

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

The required tools, some of which may already be installed, are:

make | cmake | g++ | gdb | mercurial (for hg) | python2.7 | python-pip

sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends make cmake g++ gdb mercurial python2.7 python-pip

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

These libraries may be included with your distribution, and some may already be installed:

sudo apt-get install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild from Linden Lab, version 1.1 or above.

sudo pip install --upgrade pip
sudo pip install autobuild

This will install autobuild and add a link in the exec path.

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. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one wea re 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 https://hg.firestormviewer.org/phoenix-firestorm-lgpl

It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

hg clone https://hg.firestormviewer.org/phoenix-firestorm-lgpl firestorm-source

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 https://hg.firestormviewer.org/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.

cd ~src
hg clone https://hg.firestormviewer.org/fs-build-variables/

Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.

cd ~/src/phoenix-firestorm-lgpl
export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

Unlike previous versions of autobuild, version 1.1 requires the address size switch (-A) after the command, not before it. If you want a 32-bit build, you must specify that; there is no longer a default.

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

This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.

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

Examples:

autobuild configure -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -c ReleaseFS_open -- --clean
autobuild configure -A 64 -c ReleaseFS_open -- --chan="MyBuild"

In the last example, the channel and resulting viewer name would be “Firestorm-MyBuild”.

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

autobuild build -A 64 -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 -A 64 -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

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

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

You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/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-x86_64/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

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.

• 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 Debian 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

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

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

This procedure may not work on older LTS versions of Ubuntu and has not been tested on any other versions or distributions. It is advised that you have/use a dedicated system for compiling, or a virtual guest running Ubuntu 14.04.

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

The required tools, some of which may already be installed, are:

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 python2.7 python2.7-dev python-pip

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

The recommended version of gcc/g++ for compiling Firestorm is 4.8. If you have multiple versions of g++ installed, you may have to set version 4.8 as the default. These steps will set version 4.8 as the only option, you can duplicate the second line for 4.4, 4.6 and so forth, then choose when prompted.

sudo update-alternatives --remove-all gcc
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 48 \
--slave /usr/bin/g++ g++ /usr/bin/g++-4.8 \
--slave /usr/bin/gcov gcov /usr/bin/gcov-4.8
sudo update-alternatives --config gcc

These libraries may be included with your distribution, and some may already be installed:

sudo apt-get install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \
libX11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that does all the hard work. The 64-bit version requires a modified autobuild package, which our Nicky Djasmin has provided.

sudo pip install hg+https://bitbucket.org/NickyD/autobuild-1.0#egg=autobuild

This will install autobuild and add a link in the exec path

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. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one wea re 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 https://hg.firestormviewer.org/phoenix-firestorm-lgpl

It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

hg clone https://hg.firestormviewer.org/phoenix-firestorm-lgpl firestorm-source

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 https://hg.firestormviewer.org/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

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

This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.

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

Examples:

autobuild -m64 configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild -m64 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 outisde the viewer development itself. And if you use the –clean switch, you will re-download them all.

autobuild -m64 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 -m64 build -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

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

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

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-x86_64/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

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.

• 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

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

This procedure is used for building a non-standalone viewer on 64-bit Ubuntu 16.04 LTS systems and was tested on a fresh installation within a virtual guest. 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.

The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommded 8GB or more RAM, quad-core CPU and 32GB available HDD space.

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

The required tools are:

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++-4.7 m4 mercurial python python-dev python-pip
sudo pip install --upgrade pip # The version in the repository is not the latest version
sudo pip install llbase

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

In case you have multiple versions of g++ installed, which is possible, we need to identify 4.7.x as the default version.

update-alternatives --remove-all gcc 
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.7 47 --slave /usr/bin/g++ g++ /usr/bin/g++-4.7 --slave /usr/bin/gcov gcov /usr/bin/gcov-4.7
update-alternatives --config gcc

It doesn't hurt to run those commands if you only have one g++ version installed.

These libraries may be included with your distribution, and some may be automatically installed as dependencies for the tools you just installed:

sudo apt-get install --install-recommends libc6-dev libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \
  libx11-dev libxinerama-dev libxml2-dev libxrender-dev 

You can optionally install doxygen to eliminate related errors, but it is not needed to build Firestorm

sudo apt-get install --install-recommends doxygen

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

sudo hg clone https://bitbucket.org/NickyD/autobuild-1.0 /opt/autobuild
sudo ln -s /opt/autobuild/bin/autobuild /usr/bin/autobuild 

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 home 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 https://hg.firestormviewer.org/phoenix-firestorm-lgpl

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 https://hg.firestormviewer.org/phoenix-firestorm-lgpl 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:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 https://hg.firestormviewer.org/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

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.

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

Examples:

autobuild -m64 configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild -m64 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.

autobuild -m64 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 -m64 build -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

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

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

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

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

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.

• 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/libvivoxal.so.1 with a copy from release.

This procedure is used for building a 64-bit version of Firestorm 5.1 on 64-bit Ubuntu systems. It was tested and verified on Ubuntu 16.04. This procedure assumes that your system has been properly updated.

This procedure will not work on other versions of Ubuntu, and has not been tested on any other version of Ubuntu or any other distribution/variant/derivative.

The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommended 8GB or more RAM, quad-core CPU and 32GB available HDD space.

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

This repository is needed so that gcc version 6 can be installed.

sudo add-apt-repository "deb http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial main"
sudo apt update

The required tools, some of which may already be installed, are:

sudo apt upgrade # to make sure all installed packages are current
sudo apt install --install-recommends bison bzip2 cmake curl doxygen flex g++-6 gdb m4 mercurial moreutils pkg-config \
                                      python python-dev python-pip

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

The build environment needs to know to use gcc 6

update-alternatives --remove-all gcc 
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-6 6 \ 
--slave /usr/bin/g++ g++ /usr/bin/g++-6 \
--slave /usr/bin/gcov gcov /usr/bin/gcov-6
update-alternatives --config gcc

Note that this will “hide” the current gcc (v7) from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.

If you build in a virtual machine (guest), you probably don't want to run the viewer from there, but rather from the host, or a different machine altogether. To simplify the process of sending the viewer oustide the guest, you will need rsync. Rsync will copy only the changed files, dramatically speeding up subsequent processes, and it will properly handle symbolic links.

Note that this procedure assumes you have correctly configured your guest and host, and that the destination path is accessible and writable from the guest.

sudo apt install --install-recommends rsync

Firestorm 5.1, like Linden Lab's AlexIvy release, is built with the USESYSTEMLIBS flag set so that the libraries are installed on the user's system as needed and not shipped with - or maintained by - the viewer. This means that a large number of development libraries must be installed on the build system.

These libraries should all be available in the standard Debian repositories, and some may already be installed:

sudo apt install --install-recommends libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev libboost-all-dev libcairo2-dev \
libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev libgl1-mesa-dev \
libglu1-mesa-dev libgtk2.0-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev libogg-dev libopenal-dev \
libpangox-1.0-dev libpng-dev libsdl1.2-dev libssl-dev libstdc++6 liburiparser-dev libvorbis-dev libx11-dev \
libxinerama-dev libxml2-dev libxmlrpc-epi-dev libxrender-dev zlib1g-dev

Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild from Linden Lab, version 1.1 or above.

sudo pip install --upgrade pip
sudo pip install autobuild

This will install autobuild and add a link in the exec path.

Plan your directory structure ahead of time. If you are going to be producing changes or patches you may 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 on its own hard drive, or on a hard drive with lots of free space. Currently, the source code tree takes up over 1GB initially, 3GB after configuring and several times that after building the viewer. If you are a casual compiler and won't be producing any changes, you can use one directory. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one we are after is the lgpl (release) repository. You can grab all the sources if you wish, but keep in mind that each requires over 1GB initially.

hg clone https://hg.firestormviewer.org/phoenix-firestorm-lgpl

This will create a folder called phoenix-firestorm-lgpl and add all the source files. If you desire, you can choose a different folder name by adding the name to the end of the command:

hg clone https://hg.firestormviewer.org/phoenix-firestorm-lgpl firestorm-source

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 https://hg.firestormviewer.org/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..50000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.

cd ~src
hg clone https://hg.firestormviewer.org/fs-build-variables

Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.

cd ~/src/phoenix-firestorm-lgpl
source ../fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

Unlike previous versions of autobuild, version 1.1 requires the address size switch (-A) after the command, not before it. If you want a 32-bit build, you must specify that; there is no longer a default.

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

This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.

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
• chan will set a unique channel (and the name) for the viewer, appending whatever is defined to “Firestorm-”. By default, the channel is “private” followed by your computer's name.

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

Examples:

autobuild configure -A 64 -c ReleaseFS_open -- -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -c ReleaseFS_open -- --clean
autobuild configure -A 64 -c ReleaseFS_open -- --chan="MyBuild"

In the last example, the channel and resulting viewer name would be “Firestorm-MyBuild”.

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

autobuild build -A 64 -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 -A 64 -c ReleaseFS_open – –clean [more switches]). For clarity, they are mentioned separately.

If you build the viewer using a virtual machine (guest), you may want to copy the viewer files over to your host or to a different machine in order to use the viewer. Your guest may not have sufficient resources to run the viewer. The rsync program can make copying easy and accurate. And if you build the viewer again, the options included in the command example will cause rsync to only copy the new files, cutting down on the time needed to copy.

rsync -rptgoDLK --update --progress $HOME/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/* /path/to/host/machine

Again, we will assume that you have already made that destination accessible and writable by the guest.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

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

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

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-x86_64/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

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 team (preferred) or discuss on IRC.

• 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

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

• Voice Won't Connect pt 2 The current version of the voice files may not function correctly in the Linux viewer, in which case you will see the red indicator on the Nearby Chat tab, and you may or may not get an error message. This is a known issue and is being addressed. Hopefully we can soon remove this as an issue. The workaround is to copy the win32 folder from our Release viewer's bin folder and paste it into your build's bin folder.

You can refer to this site for instructions.

These classes are based on our current Firestorm release and are conducted in text and/or voice as noted. There's no need to talk in a voice class, but you may want to be able to hear the instructor. We also usually have help available to answer questions in text.

Note that it is not mandatory that you use Firestorm to attend our classes, but it is best if you do.

Classes are held at the Firestorm Classroom unless otherwise noted.

Classes normally held daily between 8 am to 7 pm SLT. The schedule may change without notice. if the class times are inconvenient some classes have been recorded and are available on YouTube.

Unscheduled classes may also be held on an impromptu basis. If this happens, a notice will be sent in Firestorm Support English. secondlife:///app/group/3a1be8d4-01f3-bc1a-2703-442f0cc8f2dd/about

*All times SLT*

This section covers issues related to audio, video and some aspects of search.

• For situations where you cannot hear audio, be it streaming music, or the audio from a movie/video, the first thing to do is check the following:
  • Windows users: see this page.
  • Make sure streaming music and/or media are enabled in Preferences→ Sound & Media -> Sounds.
  • In the same place, check that volumes for music and media are not at minimum.
  • Make sure audio is configured correctly in your operating system (i.e., Windows, Linux, OSX), that sound is going to the correct device (i.e., speakers or headset), and so on. This may require you to adjust settings in your sound mixer, volume mixer, and/or other similar software.
  • Confirm that you have not blocked the stream/video: open Preferences → Sound & Media → Media → Manage Media Sites and see if the problem URL is listed there; if so, remove it.
  • For streaming music, test the music URL in your external web browser, to make sure that the URL actually works.

• If you have plugged in a USB sound device, you may need to relog so that the viewer can use it.
• HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

• The Dullahan Plugin (for those who have questions): Dullahan is a headless browserSDK that uses the Chromium Embedded Framework (CEF). In addition to playing media, Dullahan is also used for:
  • Websearch
  • Web profiles
  • Built-in browser
  • Splash Screen when the viewer is launched
  • Media-based HUDs
  • Avatar Menu - Choose an Avatar
  • Destination Guide
  • Wiki Help pages (when clicking the ? in a floater)

• Relog Firestorm and open the Search window
• Go to your computer processes and look for “slplugin.exe”
  • For Windows users, go to Task Manager → Processes Tab
  • For Mac users, go to Activity Monitor → My Processes (usually by default, but you can check top right drop down)
  • For Linux users, go to Command Terminal, and type “ps aux”
  • You may see four instances of the slplugin running (that is normal behavior)
  • If you do not see any instances of slplugin running, that is the cause of media failing
• If slplugin is not running, disable all firewall and virus protection (including anti-virus software and windows or other operating system firewalls). Do this check also for dullahan_host.exe.
• Relog and attempt video playback again
• If it works, you will need to stop your firewall/virus protection from blocking the slplugin and/or dullahan_host.exe files by granting appropriate permissions in your firewall/virus protection software
• NOTE: If you have several viewers installed, you will have to allow to each one access through your firewall, as well as to SLPlugin and dullahan_host.exe for each one.
• If all of the above does not resolve the issue, you can try downloading the latest SL Viewer and replacing your Firestorm slplugin file with the one from SL Viewer.

• In Preferences → Sound & Media → Sounds, make sure the “Enabled” checkbox to the right of the “Media” slider is checked
  (For audio, check “Streaming Music”)
• In Preferences → Sound & Media → Media, check “Allow inworld scripts to play media”
• In Preferences → Network & Files -> Connection, make sure the Maximum Number of Web Browser Windows dropdown is set to Five, Ten or Unlimited
• Make sure the issue is not with the specific television you are using, by attempting to view videos on a television that plays video normally for other Firestorm users.
• Make sure that “Enable plugins” is ticked in Preferences → Network & Files -> Connection, else the external media plugin can not be executed, and you may see a message saying: Adobe Flash Player or an HTML5 supported browser is required for video playback.

In-world videos (on TVs and Prim Media, a.k.a. Media-on-a-Prim) are independent streams from the source to each person watching. The only way to synchronize them is for each person to click Play at the exact same time, and even then the streams can get out of sync depending on lag, connection, buffering, and other network & computer issues.

If you have Parcel Media rights, Parcel Media is an alternative. Like a music stream, it will generally be sync'd for everyone watching (World menu > Parcel Details > Media tab). Click the ? at the top of the Media tab page or see here for more information on how to configure Parcel Media.

Embedded MP4s no longer are supported by Second Life. Consult your TV maker to determine if they use this format. Refer to BUG-224979, as well as this blog post.

Please read https://support.microsoft.com/en-au/help/4520411/adobe-flash-end-of-support before considering installing flash. Flash has a LONG history of very serious security issues. If someone is providing content that only works with flash, please contact them and let them know that flash will be end of life in the near future, this means there will be NO security updates from the vendor beyond that point. Nobody should be forcing flash on anyone in this day and age, it is 2020, not 2001 anymore. If you want to take the risk, read ahead….

The Flash plugin is not installed with Firestorm; you have to install it yourself. However, you need specific plugin versions:

• Windows users:
  • In order to play Flash format videos (e.g., YouTube videos), you must have the Opera & Chromium version of the Adobe Flash plugin installed. Unless you already have this specific version of Flash installed already, you will need to get the Opera & Chromium Flash plugin from Adobe.

• Linux users
  • You need to have the pepperflash plugin installed, which can be satisfied by installing pepperflashplugin-nonfree for Chromium

• Mac users
  • Mac users currently need the Safari & Firefox version of Adobe Flash plugin installed. Download it from Adobe.

• All users: Test your Flash
  • To make sure you have successfully installed the correct version of Flash and that it is working, use the in-world Flash game to test it.
    • Open the Developer menu: CTRL-Alt-Q. (Close this after testing; it's best not to leave this menu open.)
    • Then type CTRL-SHIFT-Z to open the internal browser.
    • Once the browser loads, click the Home icon in the upper left of the browser window.
    • Click the Media tab, at top.
    • Click “Flash game.”
    • A bubble-shooter game should load.

• NOTE: If you experience graphics driver crashes on nVidia cards when viewing Flash media (for example Youtube) both in-world and on a website and/or severe drops in your GPU clock mhz on any card then you will need to disable hardware acceleration on Flash Player. To do this, go to Youtube and Pick any video. Right click the video play area to bring up the options and follow the instructions here.

• “You have requested a file download which is not supported within Firestorm”: This message indicates you do not have Flash installed. To avoid seeing this error if you do not intend to install Flash, go to Preferences → Notifications → Alerts. Scroll down to “Warn about unsupported file downloads.” Select to highlight, and click the down arrow to move it from “Always Show” section to “Never Show” section.

QuickTime is no longer needed for Windows users (and never was for Linux users). Mac users, however, still need to have it.

• If YouTube videos suddenly will not play, and you just get a white screen, go to Preferences→ Privacy -> General, and click on Clear History, then try again.
• See also the Flash section, above.

Go to Preferences→ Sound & Media -> Sounds and make sure the volume sliders for streaming music and media are not all to the left and that there is no mute symbol (red no entry sign) on the speaker icon next to those. Make sure the Master Volume is not all to the left.

Check that Sound Source rolloff distance (Media tab) is correct; set back to default, if you changed it (5m and 30 respectively for min and max).

1) Check viewer settings

• Go to Preferences→ Sound & Media -> Sounds and check that you have the Sounds and UI sliders up high enough and that there is no mute symbol (red no entry sign) on the speaker icon next to those.

2) Check your audio drivers

• Look in Help menu → About Firestorm for the line that begins with “Audio Driver Version.” If that line says “Undefined,” reboot your computer and see if the Audio Driver Version appears.
• If this doesn't help:
  • Go into Windows device manager (https://support.microsoft.com/en-us/instantanswers/005a1acb-776e-4320-b9f2-3a2302a320da/open-device-manager) & see if there is a yellow triangle warning symbol against your Sound devices (or your display adapters).
  • Also make sure your sound card driver is up to date.
  • Reinstall your graphics driver; the drivers also include audio components.

Go to the top menu bar→ Advanced → Use Plugin Read Thread, and disable it, if it is enabled - or vice versa. (If you cannot see Advanced on the top menu, press Ctrl-Alt-D.)

If that doesn't help, first ensure that you have your bandwidth set correctly. Also, test the audio stream in your regular media player, and/or try a different audio stream in-world.

If the music volume fades as you cam around or edit objects, check the sound equalization settings in your operating system. For example, this may be caused by “Loudness equalization” being enabled in your speaker properties on Windows 7. (Refer to https://jira.firestormviewer.org/browse/FIRE-19885.)

Preferences - Sound & Media - Music - Enable Parcel Audio Fading - uncheck if checked. (reference for Support only https://jira.firestormviewer.org/browse/SUP-20376|SUP-20376).

This error is due to Flash not being installed, or not installed correctly. See above.

There are two possible causes:

• Flash is not installed, or is not installed correctly. See Flash, above.
• Your antivirus has deleted or mangled the plugin. See Antivirus Whitelisting for instructions on how to fix this.