|
|
| (16 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {{tabLang|EN|Ryzom Client On Debian DE|Building Ryzom Client On Debian|Ryzom Client On Debian ES|Ryzom Client On Debian FR|Ryzom Client On Debian RU}} | + | {{migrated to|:en:Building Ryzom Client On Debian}} |
| − | {{ToTrad|DE}}
| |
| − | {{ToTrad|ES}}
| |
| − | {{ToTrad|FR}}
| |
| − | {{ToTrad|RU}}
| |
| − | | |
| − | | |
| − | | |
| − | | |
| | == General == | | == General == |
| | | | |
| | | | |
| − | This page applies for Debian-based GNU/Linux distributions. It should work on other linux distribution too, but some package name might change. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client under Mac OS X]] | + | This page applies for Debian-based GNU/Linux distributions. It should work on other linux distribution too, but some package name might change. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client On Mac OS X]]. For Archlinux, check [[Building Ryzom Client On Archlinux]] |
| − | | |
| − | Here i use a chroot because i want to have a clean build environment, but you can perfectly do it in your own system, just skip the [[#Setting up the chroot]] part, and command run as user inside the chroot as simple user [in your system], command run as root inside the root as root [in your system] :)
| |
| − | | |
| − | If you need less control over the building process, you might check a stripped version of this same guide, which only purpose is to build the client for your own system: [[Building_Ryzom_Client_On_Debian_(Stripped_Version)]]
| |
| | | | |
| − | === Why should i build my own client ? ===
| + | If you are building the client for your own computer, build a dynamically linked version. If you are building it for other people, it's probably safer to build a statically linked version (note : you should use a distribution with a not too recent libc6, if you want it to work on as many platforms as possible. I recommend a debian Jessie, and doing that in a chroot or a VM). |
| | | | |
| − | There is a couple of valables reasons :
| + | Lines starting with a $ are meant to be run as a regular user, while lines starting with a # are meant to be run as root. |
| − | * You are having problems with sound (usually this happens when you don't use pulseaudio on your system)
| |
| − | * You want better performance
| |
| − | * You want to say "i did it !"
| |
| − | * You love to build your own executable (gentoo users, i'm looking at you)
| |
| − | * You want better graphics : the official client beeing pretty old, and some big update (including anti-aliasing if possible and anisotropic filter things like that) are available if you take the last code from RyzomCore.
| |
| | | | |
| − | == Setting up the chroot == | + | == Common steps == |
| | + | === Downloading ryzom dependencies === |
| | | | |
| − | The host system should be a debian or any derivate. Didn't tested but if you chroot a squeeze, your debian version should be at least a squeeze too.
| + | Tools needed to build the client : |
| − | I choosed squeeze because the libc version is pretty old, so the static binary compiled should work on (almost) every linux system.
| + | # apt install mercurial autoconf automake cmake libtool build-essential bison |
| − | $ command means run as simple user | + | Libraries needed : |
| − | # command means run as root | + | # apt install libluabind-dev libfreetype6-dev libcurl4-openssl-dev libx11-dev \ |
| − | #$ command means run as simple user inside chroot | + | libgl1-mesa-dev libxxf86vm-dev libxrandr-dev libxrender-dev libopenal-dev \ |
| − | ## command means run as root inside chroot | + | libogg-dev libvorbis-dev libxml2-dev libpng-dev libjpeg-dev libxmu-dev libssl-dev liblzma-dev |
| | | | |
| − | Don't forget to change USER by your username or it won't work :p
| + | If you are using debian jessie (or older), the CMake version in the repo is too old. You need to take it from jessie-backports (or, for earlier version than jessie, compile it yourself), for that, add to your /etc/apt/sources.list : |
| − | # apt-get install debootstrap dchroot
| + | deb http://ftp.debian.org/debian/ jessie-backports main |
| − | $ mkdir -p /home/USER/chroot/ryzom_squeeze64
| + | Then, update & install : |
| − | $ mkdir -p /home/USER/chroot/ryzom_squeeze32 | + | # apt update |
| − | # debootstrap --arch amd64 squeeze /home/USER/chroot/ryzom_squeeze64 http://ftp.fr.debian.org/debian
| + | # apt install -t jessie-backports cmake |
| − | # debootstrap --arch i386 squeeze /home/USER/chroot/ryzom_squeeze32 http://ftp.fr.debian.org/debian | |
| | | | |
| − | !!The instruction are only for the 64 bits chroot, just change the path for the 32 bits one :)
| + | === Getting ryzom code === |
| − | # chroot /home/USER/chroot/ryzom_squeeze64
| |
| − | ## apt-get install wget nano locales dialog apt-utils
| |
| − | ## dpkg-reconfigure locales
| |
| − | ## nano /etc/apt/sources.list
| |
| − | It should look like this :
| |
| − | deb http://ftp.fr.debian.org/debian squeeze main contrib non-free
| |
| − | deb-src http://ftp.fr.debian.org/debian squeeze main contrib non-free
| |
| − |
| |
| − | ## apt-get update
| |
| − | ## exit
| |
| − | # cp /etc/passwd/ /home/USER/chroot/ryzom_squeeze64/etc/
| |
| − | # sed 's/\([^:]*\):[^:]*:/\1:*:/' /etc/shadow | tee /home/USER/chroot/ryzom_squeeze64/etc/shadow
| |
| − | # cp /etc/group /home/USER/chroot/ryzom_squeeze64/etc/
| |
| − | # cp /etc/hosts /home/USER/chroot/ryzom_squeeze64/etc/
| |
| − | # chroot /home/USER/chroot/ryzom_squeeze64
| |
| − | ## passwd
| |
| − | I recommend using the same password as the root on your system (i think the root's password is supposed to be copied, not sure why it don't work)
| |
| − | ## exit
| |
| − | Now we have to mount some directory for our chroot :
| |
| − | # nano /etc/fstab
| |
| | | | |
| − | Add the following lines :
| + | $ cd ~ |
| − | /proc /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
| + | $ hg clone https://bitbucket.org/ryzom/ryzomcore |
| − | /dev /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
| + | We just need to switch branch (very important) |
| − | /sys /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
| + | $ cd ryzomcore |
| − | /tmp /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
| + | $ hg update -c compatibility-develop |
| − | | |
| − | # mount -a
| |
| − | # chroot /home/USER/chroot/ryzom_squeeze64
| |
| − | ## echo ryzomm_squeeze64 >> /etc/debian_chroot
| |
| − | ## exit
| |
| − | # nano /etc/schroot/schroot.conf
| |
| − | Add the following lines (make sure to change the "users=" line & directory line)
| |
| − | [ryzom_squeeze64]
| |
| − | description=Squeeze 64bits for ryzom
| |
| − | directory=/home/USER/chroot/ryzom_squeeze64
| |
| − | users=USER
| |
| − | groups=sbuild
| |
| − | root-groups=root
| |
| − |
| |
| − | [ryzom_squeeze32]
| |
| − | description=Squeeze 32 bits for ryzom
| |
| − | directory=/home/USER/chroot/ryzom_squeeze32
| |
| − | users=USER
| |
| − | groups=sbuild
| |
| − | root-groups=root
| |
| − | personality=linux32
| |
| − | | |
| − | You can now use your chroot as a normal user, just type :
| |
| − | $ dchroot -c ryzom_squeeze64 | |
| − | You won't have a ~ the first time you log in, just create it
| |
| − | #$ su -
| |
| − | ## mkdir /home/USER
| |
| − | ## chown USER:USER /home/USER
| |
| − | ## exit
| |
| − | | |
| − | Congratulations ! Your chroot are now working perfectly !
| |
| − | | |
| − | == Downloading ryzom dependencies ==
| |
| − | | |
| − | | |
| − | ## apt-get install mercurial libluabind-dev libfreetype6-dev libcurl4-openssl-dev libx11-dev libgl1-mesa-dev libxxf86vm-dev \
| |
| − | libxrandr-dev libxrender-dev libopenal-dev libogg-dev libvorbis-dev libxml2-dev cmake build-essential \
| |
| − | libpng12-dev libjpeg62-dev rrdtool libmysqlclient15-dev bison libxmu-dev autoconf automake libtool
| |
| − | | |
| − | == Compiling ryzom dependencies ==
| |
| − | | |
| − | You can probably download some of this libs but since there is often problems with them, i prefer to compile them myself :)
| |
| − | First, download all the code you need :
| |
| − | #$ cd ~
| |
| − | #$ mkdir dep_ryzomcore && cd dep_ryzomcore | |
| − | #$ hg clone http://hg.kervala.net/packaging
| |
| − | #$ hg clone http://hg.kervala.net/cmake
| |
| − | #$ export CMAKE_MODULE_PATH=$(pwd)/cmake/modules
| |
| − | | |
| − | | |
| − | libwww-dev :
| |
| − | | |
| − | #$ cd ~/dep_ryzomcore/packaging/libwww
| |
| − | #$ ./autogen.sh
| |
| − | #$ ./configure --with-ssl=no --with-zlib --with-expat --with-gnu-ld --enable-shared
| |
| − | #$ make
| |
| − | ## make install
| |
| − | | |
| − | The following two libs are only required if you want to build specific tools, not for the client itself.
| |
| − | libsquish :
| |
| − | | |
| − | #$ cd ~/dep_ryzomcore/
| |
| − | #$ export CMAKE_MODULE_PATH=$(pwd)/cmake/modules
| |
| − | #$ cd packaging/squish
| |
| − | #$ mkdir build && cd build
| |
| − | #$ cmake ..
| |
| − | #$ make
| |
| − | ## make install
| |
| − | | |
| − | cpptest :
| |
| − | | |
| − | #$ cd ~/dep_ryzomcore/packaging/cpptest/
| |
| − | #$ sh ./autogen.sh
| |
| − | #$ ./configure
| |
| − | #$ make
| |
| − | ## make install
| |
| − | | |
| − | Note : If you have trouble during the autogen.sh / configure part due to glibtoolize, find the following line (should be line 31) :
| |
| − | if glibtoolize --version &>/dev/null ; then
| |
| − | and replace it by :
| |
| − | if hash glibtoolize 2>/dev/null ; then
| |
| − | | |
| − | == Compiling ryzom dependencies, static version specific ==
| |
| − | | |
| − | We need to build libopenal static :
| |
| − | #$ cd ~
| |
| − | #$ mkdir libopenal && cd libopenal
| |
| − | #$ apt-get source libopenal1
| |
| − | #$ nano openal-soft-1.12.854-2/debian/rules
| |
| − | add this line "-DLIBTYPE=STATIC", after line 15, so you'll something like this :
| |
| − | -DALSOFT_CONFIG=ON \
| |
| − | -DLIBTYPE=STATIC \
| |
| − | | |
| − | | |
| − | ## apt-get build-dep libopenal1
| |
| − | #$ cd openal-soft-1.12.854-2
| |
| − | #$ dpkg-buildpackage -rfakeroot -uc -b
| |
| − | Unfortunately the install isn't going well so we need to copy the static lib by hand :
| |
| − | ##cp ~/libopenal/openal-soft-1.12.854-2/build-tree/libopenal.a /usr/lib
| |
| − | | |
| − | And now we need a static curl :
| |
| − | #$ cd ~
| |
| − | #$ mkdir libcurl && cd libcurl
| |
| − | I prefer to have the same curl version as my system (check apt-cache policy libcurl3 to have the info) but it shouldn't change much
| |
| − | #$ wget -c http://curl.haxx.se/download/curl-7.21.0.tar.bz2
| |
| − | #$ tar xjf curl-7.21.0.tar.bz2
| |
| − | #$ cd curl-7.21.0
| |
| − | #$ ./configure --disable-ldap --disable-ldaps --disable-rtsp --disable-dict --disable-ipv6 \
| |
| − | --disable-crypto-auth --disable-sspi --disable-tls-srp --without-gnutls --without-librtmp \
| |
| − | --without-libidn --disable-versioned-symbols --disable-pop3 --without-libssh2
| |
| − | #$ make
| |
| − | ## make install
| |
| − | | |
| − | == Getting ryzom code ==
| |
| − | | |
| − | #$ cd ~
| |
| − | #$ hg clone https://bitbucket.org/ryzom/ryzomcore
| |
| − | We just need to switch branch (default to compatibility) | |
| − | #$ cd ryzomcore | |
| − | #$ hg update -c compatibility | |
| | | | |
| | If you need to update the code later, just type : | | If you need to update the code later, just type : |
| − | #$ hg pull && hg update | + | $ hg pull && hg update |
| − | | |
| − | == Building Ryzom (static version) ==
| |
| − | | |
| − | #$ cd ~
| |
| − | #$ mkdir build_static && cd build_static
| |
| − | use the following cmake options :
| |
| − | | |
| − | | |
| − | #$ cmake -DWITH_NEL_TESTS=OFF -DWITH_NEL_SAMPLES=OFF -DWITH_NEL_TOOLS=OFF -DWITH_RYZOM_CLIENT=ON \
| |
| − | -DWITH_RYZOM_SERVER=OFF -DWITH_RYZOM_TOOLS=OFF -DWITH_NEL=ON -DWITH_SOUND=ON -DWITH_DRIVER_OPENGL=ON \
| |
| − | -DWITH_DRIVER_OPENAL=ON -DWITH_STATIC=ON -DWITH_STATIC_DRIVERS=ON -DWITH_NEL_TESTS=OFF \
| |
| − | -DWITH_LIBWWW_STATIC=ON -DOPENAL_LIBRARY=/usr/lib/libopenal.a -DOPENGL_gl_LIBRARY=/usr/lib/libGL.so \
| |
| − | -DWITH_STATIC_EXTERNAL=ON -DWITH_STLPORT=OFF -DCURL_LIBRARY=/usr/local/lib/libcurl.a ../ryzomcore/code
| |
| − | | |
| − | The directory of libGL.so might change, depending on the strange things happenin in /usr/lib with the i386/ amd64 directory, check it before building.
| |
| − | | |
| − | Here, n is the number of core in your CPU :
| |
| − | #$ make -jn
| |
| − | | |
| − | == Building Ryzom (dynamically linked) ==
| |
| − | | |
| − | #$ cd ~
| |
| − | #$ mkdir build && cd build
| |
| | | | |
| − | For differents cmake options, see [[#CMake options]]. Here's the one i'm using :
| + | == Dynamically linked version == |
| | | | |
| − | #$ cmake -DWITH_NEL_TESTS=OFF -DWITH_NEL_SAMPLES=OFF -DWITH_NEL_TOOLS=OFF -DWITH_RYZOM_SERVER=OFF \
| + | === Building ryzom === |
| − | -DWITH_RYZOM_TOOLS=OFF -DWITH_QT=OFF -DWITH_RYZOM_CLIENT=ON ../ryzomcore/code
| + | (Assuming you are in the ryzomcore folder you got in [[#Getting ryzom code]]) |
| | | | |
| − | If you are having trouble with cmake who can't find LIBWWW_INCLUDE_DIR, it's probably because the make install of libwww put everything in a subfolder of /usr/local/include and cmake doesn't seems to find it. Easiest way to solve it is : (the path may change a little on your computer)
| + | $ cmake -DWITH_RYZOM_CLIENT=ON -DWITH_STATIC=ON -DWITH_STATIC_DRIVERS=ON -DWITH_DRIVER_OPENGL=ON -DWITH_QT=OFF -DWITH_NEL_TESTS=OFF -DWITH_RYZOM_SERVER=OFF -DWITH_NEL_SAMPLES=OFF -DWITH_SNOWBALLS=OFF -DWITH_NEL_TOOLS=OFF -DWITH_RYZOM_TOOLS=OFF -DWITH_RYZOM_PATCH=ON ../code |
| − | ## cd /usr/local/include/-package/
| |
| − | ## mv * ..
| |
| − | Then run cmake again
| |
| − | Here, n is the number of core in your CPU :
| |
| − | #$ make -jn
| |
| − | The binary is now in bin/ryzom_client. You can't really use this one like that, because you need all the libs (libnel* + libryzom* that you just compiled, libwwwthat you compiled earlier). If you want to use this one, copy all the file in lib/ and all the file in /usr/local/lib in your system (/usr/local/lib for example). Easy (and clean) way to do that is to run the following command :
| |
| − | ## make install
| |
| − | Will put all the needed file where they belong :) (ryzom_client will go to /usr/local/games)
| |
| | | | |
| − | == How do i use my client ? ==
| + | Let's build ! replace n with the number of your cores |
| | + | $ make -jn ryzom_client |
| | | | |
| − | Very simple ! Just copy your ryzom_client executable (from your bin/ folder if it's static, or /usr/local/games if you built it dynamic way) to your ryzom folder. I recommend keeping the official ryzom_client and renaming yours, so you have a backup client in case of trouble !
| + | === Play ryzom === |
| | | | |
| − | == Creating a package for ryzom ==
| + | Copy the bin/ryzom_client executable in your ryzom folder (if you are using ryzom installer, it's in ~/.local/share/Ryzom/ryzom_live/). I recommend changing the file name to ryzom_client_compiled or something, or it will replace itself with a patched version everytime you run it (assuming you didn't disabled the patch at compilation), and change the executable your profile use (or directly change the value "client_filename_linux" in your server configuration, in ryzom_installer.ini) |
| − | TODO : pbuilder tutorial
| |
| | | | |
| − | == CMake options ==
| + | That's it ! |
| | | | |
| − | === Option specific to RyzomCore === | + | == Static version == |
| | | | |
| − | *BUILD_DASHBOARD
| |
| − | *BOOST_DIR
| |
| − | *CMAKE_BUILD_TYPE
| |
| − | *CMAKE_CONFIGURATION_TYPES
| |
| − | *CMAKE_INSTALL_PREFIX
| |
| − | *CPPTEST_INCLUDE_DIR
| |
| − | *FINAL_VERSION - '''TRUE'''
| |
| − | *FREETYPE_ADDITIONAL_INCLUDE_DIR
| |
| − | *FREETYPE_INCLUDE_DIRS
| |
| − | *FREETYPE_LIBRARY
| |
| − | *JPEG_INCLUDE_DIR
| |
| − | *JPEG_LIBRARY
| |
| − | *LIBWWW_ADDITIONAL_INCLUDE_DIR
| |
| − | *LIBWWW_INCLUDE_DIR
| |
| − | *LUABIND_INCLUDE_DIR
| |
| − | *NL_BIN_PREFIX
| |
| − | *NL_DRIVER_PREFIX
| |
| − | *NL_ETC_PREFIX
| |
| − | *NL_LIB_PREFIX
| |
| − | *NL_SBIN_PREFIX
| |
| − | *NL_SHARE_PREFIX
| |
| − | *OGG_INCLUDE_DIR
| |
| − | *OGG_LIBRARY
| |
| − | *RYZOM_BIN_PREFIX
| |
| − | *RYZOM_ETC_PREFIX
| |
| − | *RYZOM_ETC_PREFIX
| |
| − | *RYZOM_GAMES_PREFIX
| |
| − | *RYZOM_LIB_PREFIX
| |
| − | *RYZOM_SBIN_PREFIX
| |
| − | *RYZOM_SHARE_PREFIX
| |
| − | *SQUISH_INCLUDE_DIR
| |
| − | *VORBISFILE_LIBRARY
| |
| − | *VORBIS_INCLUDE_DIR
| |
| − | *VORBIS_LIBRARY
| |
| − | *WITH_3D - '''TRUE'''
| |
| − | *WITH_COVERAGE
| |
| − | *WITH_DRIVER_DIRECT3D
| |
| − | *WITH_DRIVER_DSOUND
| |
| − | *WITH_DRIVER_FMOD
| |
| − | *WITH_DRIVER_OPENAL - '''TRUE'''
| |
| − | *WITH_DRIVER_OPENGL - '''TRUE'''
| |
| − | *WITH_DRIVER_OPENGLES
| |
| − | *WITH_DRIVER_XAUDIO2
| |
| − | *WITH_EXTERNAL
| |
| − | *WITH_GEORGES - '''TRUE'''
| |
| − | *WITH_GTK
| |
| − | *WITH_GUI - '''TRUE'''
| |
| − | *WITH_INSTALL_LIBRARIES - '''TRUE'''
| |
| − | *WITH_LIBWWW_STATIC
| |
| − | *WITH_LIGO - '''TRUE'''
| |
| − | *WITH_LOGGING - '''TRUE'''
| |
| − | *WITH_LOGIC - '''TRUE'''
| |
| − | *WITH_LUA51 - '''TRUE'''
| |
| − | *WITH_MFC
| |
| − | *WITH_NEL - '''TRUE'''
| |
| − | *WITH_NELNS
| |
| − | *WITH_NELNS_LOGIN_SYSTEM - '''TRUE'''
| |
| − | *WITH_NELNL_SERVER - '''TRUE'''
| |
| − | *WITH_NEL_CEGUI
| |
| − | *WITH_NEL_MAXPLUGIN
| |
| − | *WITH_NEL_SAMPLES - '''TRUE'''
| |
| − | *WITH_NEL_TESTS - '''TRUE'''
| |
| − | *WITH_NEL_TOOLS - '''TRUE'''
| |
| − | *WITH_NET - '''TRUE'''
| |
| − | *WITH_PACS - '''TRUE'''
| |
| − | *WITH_PCH - '''TRUE'''
| |
| − | *WITH_QT
| |
| − | *WITH_RYZOM - '''TRUE'''
| |
| − | *WITH_RYZOM_CLIENT - '''TRUE'''
| |
| − | *WITH_RYZOM_SERVER
| |
| − | *WITH_RYZOM_SOUND - '''TRUE'''
| |
| − | *WITH_RYZOM_TOOLS - '''TRUE'''
| |
| − | *WITH_SNOWBALLS
| |
| − | *WITH_SNOWBALLS_CLIENT - '''TRUE'''
| |
| − | *WITH_SNOWBALLS_SERVER - '''TRUE'''
| |
| − | *WITH_SOUND - '''TRUE'''
| |
| − | *WITH_STATIC
| |
| − | *WITH_STATIC_DRIVERS
| |
| − | *WITH_STATIC_EXTERNAL
| |
| − | *WITH_STLPORT
| |
| − | *WITH_SYMBOLS
| |
| − | *XF86VidMode_INCLUDE_DIR
| |
| − | *XF86_VidMode_LIBRARY
| |
| | | | |
| − | === Generic option who might be useful === | + | === Compiling ryzom dependencies === |
| | | | |
| − | TODO
| + | Note : this is done on a debian jessie, debian stretch (and possibly sid) will have multiples issues with -fPic, needing you to recompile a shitton of library(openssl, gif, curl, almost anything really), so i recommend sticking with jessie. |
| | | | |
| − | === Common option set to build a client === | + | We just need to build curl ; Grab it from kervala's packaging repository : |
| | + | $ hg clone http://hg.kervala.net/packaging/ |
| | + | $ cd packaging/curl |
| | + | $ mkdir build && cd build |
| | + | $ cmake -DCMAKE_BUILD_TYPE=Release -DCURL_ZLIB=ON -DBUILD_CURL_EXE=OFF -DBUILD_CURL_TESTS=OFF -DCURL_STATICLIB=ON -DHTTP_ONLY=ON -DENABLE_IPV6=ON -DCMAKE_USE_OPENSSL=ON -DOPENSSL_SSL_LIBRARIES=/usr/lib/libssl.a -DOPENSSL_CRYPTO_LIBRARIES=/usr/lib/libcrypto.a -DCMAKE_USE_LIBSSH2=OFF -DZLIB_LIBRARY=/usr/lib/libz.a .. |
| | + | $ make |
| | + | # make install |
| | | | |
| − | Standard client compilation :
| + | === Building Ryzom === |
| − | #$ cmake -DWITH_NEL_TESTS=OFF -DWITH_NEL_SAMPLES=OFF -DWITH_NEL_TOOLS=OFF -DWITH_RYZOM_SERVER=OFF \
| |
| − | -DWITH_RYZOM_TOOLS=OFF -DWITH_QT=OFF -DWITH_RYZOM_CLIENT=ON ..
| |
| − |
| |
| − | Static client compilation :
| |
| − | #$ cmake -DWITH_NEL_TESTS=OFF -DWITH_NEL_SAMPLES=OFF -DWITH_NEL_TOOLS=OFF -DWITH_RYZOM_CLIENT=ON \
| |
| − | -DWITH_RYZOM_SERVER=OFF -DWITH_RYZOM_TOOLS=OFF -DWITH_NEL=ON -DWITH_SOUND=ON -DWITH_DRIVER_OPENGL=ON \
| |
| − | -DWITH_DRIVER_OPENAL=ON -DWITH_STATIC=ON -DWITH_STATIC_DRIVERS=ON -DWITH_STLPORT=OFF -DWITH_NEL_TESTS=OFF \
| |
| − | -DWITH_LIBWWW_STATIC=ON -DOPENAL_LIBRARY=/usr/lib/libopenal.a -DOPENGL_gl_LIBRARY=/usr/lib/libGL.so \
| |
| − | -DWITH_STATIC_EXTERNAL=ON -DCURL_LIBRARY=/usr/local/lib/libcurl.a ..
| |
| − |
| |
| − | Adding debugging symbols (useful if you want to run gdb) :
| |
| − | #$ cmake -DWITH_SYMBOLS=ON ALLOTHEROPTIONS ..
| |
| | | | |
| − | Debug mode (useful only if you are a dev ; it's a bad idea to use it if you aren't cause there is more crash + it's slower) :
| + | (Assuming you are in the ryzomcore folder you got in [[#Getting ryzom code]]) |
| − | #$ cmake -DFINAL_VERSION=OFF -DCMAKE_BUILD_TYPE=Debug ALLOTHEROPTIONS .. | + | $ mkdir build_static && cd build_static |
| − | == Auto-build script ==
| + | (Cmake options are almost the same, we need to use our compiled curl library, and use static_external): |
| | | | |
| − | A simple script to build different (static) version of the client : [http://manda.glorf.fr/client/static_build]
| + | Let's build ! replace n with the number of your cores |
| | + | $ make -jn ryzom_client |
| | | | |
| − | Another script to manage the built ryzom_client : launch a new build (both 64 & 32 bits) using my chroot, then saving everything and uploading it to my server : [http://manda.glorf.fr/client/chroot_static_build]
| + | === Further reading on static building === |
| − | == Sources == | |
| − | For the chroot / static compilation, an excellent tutorial by shevek : [http://sevmek.free.fr/static/howto-ryzom2.0.txt]
| |
| | | | |
| − | For the client building & dependencies, the RyzomCore wiki page : [https://ryzomcore.atlassian.net/wiki/display/RC/Build+Source+on+Linux]
| + | If you actually want to regularely build static ryzom client, you should check [[http://hg.kervala.net/packaging/file/5b4bf439aa91/ryzom/steam|kervala's scripts]], they are very complete and allow you to completely automate your build process. |
| | | | |
| − | For the chroot & client building : [http://sevmek.free.fr/static/howto-ryzom2.0.txt]
| |
| | <references /> | | <references /> |
| | {{In_Category|Linux}} | | {{In_Category|Linux}} |
This page applies for Debian-based GNU/Linux distributions. It should work on other linux distribution too, but some package name might change. To compile Ryzom client under Mac OS X, please check this page : Building Ryzom Client On Mac OS X. For Archlinux, check Building Ryzom Client On Archlinux
If you are building the client for your own computer, build a dynamically linked version. If you are building it for other people, it's probably safer to build a statically linked version (note : you should use a distribution with a not too recent libc6, if you want it to work on as many platforms as possible. I recommend a debian Jessie, and doing that in a chroot or a VM).
Lines starting with a $ are meant to be run as a regular user, while lines starting with a # are meant to be run as root.
If you are using debian jessie (or older), the CMake version in the repo is too old. You need to take it from jessie-backports (or, for earlier version than jessie, compile it yourself), for that, add to your /etc/apt/sources.list :
Copy the bin/ryzom_client executable in your ryzom folder (if you are using ryzom installer, it's in ~/.local/share/Ryzom/ryzom_live/). I recommend changing the file name to ryzom_client_compiled or something, or it will replace itself with a patched version everytime you run it (assuming you didn't disabled the patch at compilation), and change the executable your profile use (or directly change the value "client_filename_linux" in your server configuration, in ryzom_installer.ini)
Note : this is done on a debian jessie, debian stretch (and possibly sid) will have multiples issues with -fPic, needing you to recompile a shitton of library(openssl, gif, curl, almost anything really), so i recommend sticking with jessie.
(Cmake options are almost the same, we need to use our compiled curl library, and use static_external):
