Compiling Second Life First Look 1.13.3.58018 on Ubuntu, again

This build failed, but the next one succeeded. This article includes some of the steps I had to make in the next build.

Reference:

• Source code
• Compiling the viewer (Linux)
• My system specs

tar xzf slviewer-src-FL-1.13.3.58185.tar.gz
tar xzf slviewer-linux-libs-FL-1.13.3.58185.tar.gz
unzip slviewer-artwork-FL-1.13.3.58185.zip
tar xzf fmodapi375linux.tar.gz

as kindly suggested in a comment to previous article, i’m going to edit the first line of any build scripts from ‘#!/bin/sh’ to ‘#!/bin/bash’:

vim linden/indra/newview/linux_tools/launch_url.sh
vim linden/indra/newview/linux_tools/wrapper.sh
(UPDATE: this one doesn’t exist in beta-1.13.4.3) vim linden/indra/newview/linux_tools/package-client.sh
vim linden/libraries/include/boost/pool/detail/pool_construct_simple.sh
vim linden/libraries/include/boost/pool/detail/pool_construct.sh
vim linden/libraries/i686-linux/include/apr-1/arch/unix/apr_arch_threadproc.h

i hope i edited all appropriate files.

cd fmodapi375linux/
cp api/inc/* ../linden/libraries/i686-linux/include/
cp api/libfmod-3.75.so ../linden/libraries/i686-linux/lib_release_client/

export SLSRC=/my/path/to/linden/

cp -a /usr/include/atk-1.0 ${SLSRC}/libraries/i686-linux/include/
cp -a /usr/include/gtk-2.0 ${SLSRC}/libraries/i686-linux/include/
cp -a /usr/lib/gtk-2.0/include/* ${SLSRC}/libraries/i686-linux/include/gtk-2.0/
cp -a /usr/include/glib-2.0 ${SLSRC}/libraries/i686-linux/include/
cp -a /usr/lib/glib-2.0/include/* ${SLSRC}/libraries/i686-linux/include/glib-2.0/
cp -a /usr/include/pango-1.0 ${SLSRC}/libraries/i686-linux/include/
cp -a /usr/include/cairo/* ${SLSRC}/libraries/i686-linux/include/

cd ../linden/indra/

vim newview/linux_tools/client-manifest-i686
(i uncomment the two lines corresponding to libllkdu and libkdu – then they should be automatically copied into the right place in the runtime directory as i’m following the ‘Packaging the client’ instructions)

scons DISTCC=no BTARGET=client BUILD=releasefordownload
(i’m using the BUILD=releasefordownload scon option because i need to build a complete tarball for the end-user)

(…now waiting…)