Ryzom Forge Wiki - User contributions [en]

FR Support

2014-10-02T20:12:21Z

Cacatoes: /* Tutoriaux Linux */

{{TabLang|FR|Support DE|EN Support|ES|Support FR|RU}}



Dans le domaine du Support, différenciez bien les CSR (capables de vous apporter une aide allant bien au delà des conseils) des bénévoles joueurs qui ne peuvent que vous aider avec des mots, mais n'ont aucun pouvoir pour vous aider à changer de nom ou enlever un bannissement.

''Note : Améliorer la liste ci-dessous en notant les noms des CSR et leur domaine de prédilection, en précisant qui est CSR, Anim ou autre, et aussi quelle langue peut parler chacun (avec une note estimée par eux de 1/5, 5 étant "parle parfaitement" et 1 "pourra aider avec un traducteur" ?).''

=GNU/LINUX=

== Tutoriaux Linux==
*[[Building Ryzom Client On Debian]]
*[[FR_Building Ryzom Client On Debian (Stripped Version)]]
*[[Linux_FAQ_EN]]

==Équipe Linux==
''Elle est joignable est [[FR_IRC|IRC]].''
*CSR Emiro (Deutsch, English)
*Glorf (French, English)
*Madi (French, English)
*Zatalyz (French, basic English)
*Daulath (French, English?)
*Zorroargh (French, Spanish, English?)
*Shikitiwa (?)
*Kervala (French, English)

= MAC =

==Tutoriels Mac==

* [http://app.ryzom.com/app_forum/index.php?page=post/view/142180 Copier les Paramètres Ryzom 2.1.0]

==Équipe Mac==
''Elle est joignable est [[FR_IRC|IRC]].''
*Lod (Français, ?)
*Jazzy (Français)
*SIELA1915 (English, Français, Deutsch)

=WINDOWS =

==Tutoriels Windows==

==Équipe Windows==
*CSR Emiro (Deutsch, English)
*CSR Aileya (Deutsch, English)

= Pour en savoir plus sur le Support =

==Rôles==

* Créer les tutoriaux sur comment installer Ryzom sous Linux, Mac et Windows et sur comment résoudre les problèmes courants rencontrés sur les diverses plateformes. Cette partie du wiki est l'endroit idéale pour stocker toutes les astuces pour dépanner quand le client rencontre des problèmes !
* Créer une FAQ sur le forum, qui redigiera vers les tutoriaux.

Lorsque vous créez un tutoriel, n'oubliez pas d'ajouter trois types de catégories :
*Linux, Mac, Windows ou Tout OS
*Support
*Tutoriaux

==Todo list==

* Publier sur cette page un tutoriel pour chaque question technique récurrente. Si le tutoriel existe déjà sur Ryzom Core, le copier ici pour permettre sa traduction, mais en précisant le lien vers la source.

* Créer sur le forum une FAQ pointant en cas de besoin vers les tutoriels. (Utiliser la section Support).

{{TPInWikiRyzom}}
[[Category:Support]]
[[Category:Tutorials]]
[[Category:FR]]

FR Building Ryzom Client On Debian (Stripped Version)

2014-10-02T20:08:15Z

Cacatoes: /* Compiler Ryzom (dynamiquement) */

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}

== General ==

Cet article s'applique aux distributions Gnu/Linux Debian et dérivées. Pour compiler Ryzom sous Mac OS X, merci de consulter: [[Building Ryzom Client under Mac OS X]]

Ce guide est une version allégée de [[Building_Ryzom_Client_On_Debian]].

Nous assumerons donc ici que vous souhaitez compiler le client '''pour votre propre besoin''', et non pas pour:
* faire un paquet .deb
* avoir un client compatible avec d'autres distributions linux (utilisant une vieille version de libc6)
* compiler non seulement le client mais aussi les outils ryzom
* compiler de façon statique plutôt que dynamique
Auquel cas, veuillez suivre cet autre guide.

Les instructions précédées par un # sont à exécuter en tant que root. Celles avec un $ sont à lancer depuis votre compte utilisateur normal.

== Installer les dépendances de compilation de Ryzom ==

# aptitude 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

== Compiler les dépendances de Ryzom ==

D'abord, récupérez le code nécessaire:
$ 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

Puis construisez 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

Note: le paquet libwww-dev [https://packages.debian.org/sid/libwww-dev n'est pas disponible pour toutes les architectures] dans les dépots Debian. Il s'agit d'une librairie ancienne et non maintenue, et modifiée pour que Ryzom puisse continuer de l'utiliser. Si vous le pouvez, aidez-nous à la remplacer.

== Récupérer le code de Ryzom ==

$ cd ~
$ hg clone https://bitbucket.org/ryzom/ryzomcore
Nous changeons juste de branche (de ''default'' à ''compatibility'')
$ cd ryzomcore
$ hg update -c compatibility

Si vous avez besoin de mettre à jour le code plus tard, tapez juste:
$ hg pull && hg update

== Compiler Ryzom (dynamiquement) ==

$ cd ~
$ mkdir build && cd build

Nous utilisons les options ci-dessous pour cmake. Consultez le paragraphe [[Building_Ryzom_Client_On_Debian#CMake options]] de l'autre guide si vous souhaitez les modifier.

$ 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 ../ryzomcore/code

Puis lancez cmake à nouveau.
Ici, ''n'' est à remplacer par le nombre de coeurs dont votre processeur dispose:
$ make -jn

La version compilée est désormais dans bin/ryzom_client. Nous pouvons installer ryzom_client sur le système (stocké dans /usr/local) :

# make install
# ldconfig

== Démarrer Ryzom avec le client fraichement compilé ==

Vous devrez démarrer ryzom_client depuis le répertoire où résident les données du jeu.

Si ce n'est déjà fait, procurez-vous le jeu complet via l'archive .zip du site officiel de Ryzom. Décompressez-la où vous désirez que le jeu soit installé (nous assumerons: ~/games/ryzom)

Copiez le client Ryzom dans ce répertoire, de préférence sous un autre nom (autrement il risque d'être remplacé par le script de mise à jour de Ryzom).
$ cp /usr/local/games/ryzom_client ~/games/ryzom/ryzom_client_mybuild

Vous pouvez maintenant lancer Ryzom:
$ cd ~/games/ryzom
$ ./ryzom_client_mybuild

Amusez-vous bien !

== Sources ==

Ce même guide mais avec des instructions plus complètes pour compiler depuis un environnement chroot, compiler les outils ryzom (et pas seulement le client): [[Building_Ryzom_Client_On_Debian]]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:FR]]

FR Building Ryzom Client On Debian (Stripped Version)

2014-10-02T20:07:51Z

Cacatoes: /* Compiler Ryzom (dynamiquement) */

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}

== General ==

Cet article s'applique aux distributions Gnu/Linux Debian et dérivées. Pour compiler Ryzom sous Mac OS X, merci de consulter: [[Building Ryzom Client under Mac OS X]]

Ce guide est une version allégée de [[Building_Ryzom_Client_On_Debian]].

Nous assumerons donc ici que vous souhaitez compiler le client '''pour votre propre besoin''', et non pas pour:
* faire un paquet .deb
* avoir un client compatible avec d'autres distributions linux (utilisant une vieille version de libc6)
* compiler non seulement le client mais aussi les outils ryzom
* compiler de façon statique plutôt que dynamique
Auquel cas, veuillez suivre cet autre guide.

Les instructions précédées par un # sont à exécuter en tant que root. Celles avec un $ sont à lancer depuis votre compte utilisateur normal.

== Installer les dépendances de compilation de Ryzom ==

# aptitude 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

== Compiler les dépendances de Ryzom ==

D'abord, récupérez le code nécessaire:
$ 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

Puis construisez 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

Note: le paquet libwww-dev [https://packages.debian.org/sid/libwww-dev n'est pas disponible pour toutes les architectures] dans les dépots Debian. Il s'agit d'une librairie ancienne et non maintenue, et modifiée pour que Ryzom puisse continuer de l'utiliser. Si vous le pouvez, aidez-nous à la remplacer.

== Récupérer le code de Ryzom ==

$ cd ~
$ hg clone https://bitbucket.org/ryzom/ryzomcore
Nous changeons juste de branche (de ''default'' à ''compatibility'')
$ cd ryzomcore
$ hg update -c compatibility

Si vous avez besoin de mettre à jour le code plus tard, tapez juste:
$ hg pull && hg update

== Compiler Ryzom (dynamiquement) ==

$ cd ~
$ mkdir build && cd build

Nous utilisons les options ci-dessous pour cmake. Consultez le paragraphe [[Building_Ryzom_Client_On_Debian#CMake options]] de l'autre guide si vous souhaitez les modifier.

$ 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 ../ryzomcore/code

Puis lancez cmake à nouveau.
Ici, ''n'' est à remplacer par le nombre de «cores» dont votre processeur dispose:
$ make -jn

La version compilée est désormais dans bin/ryzom_client. Nous pouvons installer ryzom_client sur le système (stocké dans /usr/local) :

# make install
# ldconfig

== Démarrer Ryzom avec le client fraichement compilé ==

Vous devrez démarrer ryzom_client depuis le répertoire où résident les données du jeu.

Si ce n'est déjà fait, procurez-vous le jeu complet via l'archive .zip du site officiel de Ryzom. Décompressez-la où vous désirez que le jeu soit installé (nous assumerons: ~/games/ryzom)

Copiez le client Ryzom dans ce répertoire, de préférence sous un autre nom (autrement il risque d'être remplacé par le script de mise à jour de Ryzom).
$ cp /usr/local/games/ryzom_client ~/games/ryzom/ryzom_client_mybuild

Vous pouvez maintenant lancer Ryzom:
$ cd ~/games/ryzom
$ ./ryzom_client_mybuild

Amusez-vous bien !

== Sources ==

Ce même guide mais avec des instructions plus complètes pour compiler depuis un environnement chroot, compiler les outils ryzom (et pas seulement le client): [[Building_Ryzom_Client_On_Debian]]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:FR]]

FR Building Ryzom Client On Debian (Stripped Version)

2014-10-02T20:04:06Z

Cacatoes: Traduction

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}

== General ==

Cet article s'applique aux distributions Gnu/Linux Debian et dérivées. Pour compiler Ryzom sous Mac OS X, merci de consulter: [[Building Ryzom Client under Mac OS X]]

Ce guide est une version allégée de [[Building_Ryzom_Client_On_Debian]].

Nous assumerons donc ici que vous souhaitez compiler le client '''pour votre propre besoin''', et non pas pour:
* faire un paquet .deb
* avoir un client compatible avec d'autres distributions linux (utilisant une vieille version de libc6)
* compiler non seulement le client mais aussi les outils ryzom
* compiler de façon statique plutôt que dynamique
Auquel cas, veuillez suivre cet autre guide.

Les instructions précédées par un # sont à exécuter en tant que root. Celles avec un $ sont à lancer depuis votre compte utilisateur normal.

== Installer les dépendances de compilation de Ryzom ==

# aptitude 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

== Compiler les dépendances de Ryzom ==

D'abord, récupérez le code nécessaire:
$ 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

Puis construisez 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

Note: le paquet libwww-dev [https://packages.debian.org/sid/libwww-dev n'est pas disponible pour toutes les architectures] dans les dépots Debian. Il s'agit d'une librairie ancienne et non maintenue, et modifiée pour que Ryzom puisse continuer de l'utiliser. Si vous le pouvez, aidez-nous à la remplacer.

== Récupérer le code de Ryzom ==

$ cd ~
$ hg clone https://bitbucket.org/ryzom/ryzomcore
Nous changeons juste de branche (de ''default'' à ''compatibility'')
$ cd ryzomcore
$ hg update -c compatibility

Si vous avez besoin de mettre à jour le code plus tard, tapez juste:
$ hg pull && hg update

== Compiler Ryzom (dynamiquement) ==

$ cd ~
$ mkdir build && cd build

Nous utilisons les options ci-dessous pour cmake. Consultez le paragraphe [[Building_Ryzom_Client_On_Debian#CMake options]] de l'autre guide si vous souhaitez les modifier.

$ 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 ../ryzomcore/code

Puis lancez cmake à nouveau.
Ici, n est à remplacer par le nombre de «cores» dont votre processeur dispose:
$ make -jn

La version compilée est désormais dans bin/ryzom_client. Nous pouvons installer ryzom_client sur le système (stocké dans /usr/local) :

# make install
# ldconfig

== Démarrer Ryzom avec le client fraichement compilé ==

Vous devrez démarrer ryzom_client depuis le répertoire où résident les données du jeu.

Si ce n'est déjà fait, procurez-vous le jeu complet via l'archive .zip du site officiel de Ryzom. Décompressez-la où vous désirez que le jeu soit installé (nous assumerons: ~/games/ryzom)

Copiez le client Ryzom dans ce répertoire, de préférence sous un autre nom (autrement il risque d'être remplacé par le script de mise à jour de Ryzom).
$ cp /usr/local/games/ryzom_client ~/games/ryzom/ryzom_client_mybuild

Vous pouvez maintenant lancer Ryzom:
$ cd ~/games/ryzom
$ ./ryzom_client_mybuild

Amusez-vous bien !

== Sources ==

Ce même guide mais avec des instructions plus complètes pour compiler depuis un environnement chroot, compiler les outils ryzom (et pas seulement le client): [[Building_Ryzom_Client_On_Debian]]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:FR]]

Building Ryzom Client On Debian

2014-10-02T19:44:55Z

Cacatoes: /* General */ adding stripped version for less control over building process

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}
{{ToTrad|FR|FR translation needed please}}

== General ==

This page applies for Debian-based GNU/Linux distributions. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client under Mac OS X]]

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 ? ===

There is a couple of valables reasons :
* 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 ==

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.
I choosed squeeze because the libc version is pretty old, so the static binary compiled should work on (almost) every linux system.
$ command means run as simple user
# command means run as root
#$ command means run as simple user inside chroot
## command means run as root inside chroot

Don't forget to change USER by your username or it won't work :p
# apt-get install debootstrap dchroot
$ mkdir -p /home/USER/chroot/ryzom_squeeze64
$ mkdir -p /home/USER/chroot/ryzom_squeeze32
# debootstrap --arch amd64 squeeze /home/USER/chroot/ryzom_squeeze64 http://ftp.fr.debian.org/debian
# 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 :)
# 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 :
/proc /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/dev /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/sys /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/tmp /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0

# 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 :
#$ 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 :

#$ 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 ../ryzomcore/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)
## 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 ? ==

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 !

== Creating a package for ryzom ==
TODO : pbuilder tutorial

== CMake options ==

=== Option specific to RyzomCore ===

*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 ===

TODO

=== Common option set to build a client ===

Standard client compilation :
#$ 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) :
#$ cmake -DFINAL_VERSION=OFF -DCMAKE_BUILD_TYPE=Debug ALLOTHEROPTIONS ..
== Auto-build script ==

A simple script to build different (static) version of the client : [http://manda.glorf.fr/client/static_build]

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]
== 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]

For the chroot & client building : [http://sevmek.free.fr/static/howto-ryzom2.0.txt]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:EN]]

EN Support

2014-10-02T19:42:10Z

Cacatoes: /* Linux FAQ and Tutorials */

{{TabLang|EN|Support DE|EN Support|ES|FR Support|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please.}}

For support, please make a difference between CSRs (able to help you with more than advices) and volunteer players who can only help you with words, but have no power to help you change your name or remove your ban.

''Note: improve the following list by adding the names of the CSR and their specialties, precising who's a CSR, an Anim or anything else and also which language each of them can speak (with an estimation of their mastery of each language going from 1 to 5, 5 being perfect and 1 being "can help with a translator"?)''

=GNU/LINUX=

== Linux FAQ and Tutorials ==
*[[Building Ryzom Client On Debian]]
*[[Building Ryzom Client On Debian (Stripped Version)]]
*[[Linux_FAQ_EN]]

==Linux To do list==

{{ToTrad|FR|FR translation needed please}}

{| border="1" cellpadding="5" cellspacing="0"
!Task
!Assigned to
!Display
!Progress
!Status
|-
|Write a tutorial or complete the FAQ page for each regular technical question related to Linux.
If the tutorial already exist, please copy it in this wiki to enable the translations, adding the link to the source.
|All the Linux team
|FAQ: http://forge.ryzom.com/wiki/Linux_FAQ_EN
Tutorial: create a new page
|WIP
|Added on http://app.ryzom.com/app_forum/index.php?page=post/view/141841 as soon as verified
|-
|Look at the unsticky topics about Linux in the EN Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be added in the "Linux FAQ and Linux Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Linux in the DE Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be added in the "Linux FAQ and Linux Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Linux in the FR Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be added in the "Linux FAQ and Linux Tutorials" topic.
|
|
|To do
|
|-

|}

==Linux Team ==
''They are joinable on [[EN_IRC|IRC]].''
*CSR Emiro (Deutsch, English)
*Glorf (French, English)
*Kervala (French, English)
*Madi (French, English)
*Zatalyz (French, simple English)
*Daulath (French, ?)
*Zorroargh (French, Spanish, English)
*Shikitiwa (French, ?)

= MAC =

==Mac FAQ and tutorials==

* [[Building_Ryzom_Client_under_Mac_OS_X]]
* [[Ryzom_Client_2.1.0_Mac OS X]]

==Mac Todo list==

{{ToTrad|FR|FR translation needed please}}

{| border="1" cellpadding="5" cellspacing="0"
!Task
!Assigned to
!Display
!Progress
!Status
|-
|Write a tutorial for each regular technical question related to Mac.
If the tutorial already exist, please copy it in this wiki to enable the translations, adding the link to the source.
|All the Mac team
|
Tutorial: create a new page
|WIP
|Added on http://app.ryzom.com/app_forum/index.php?page=topic/view/20964/ as soon as verified
|-
|Write a Mac FAQ
|
|
|
|
|-
|Look at the sticky topics about Mac in the EN Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be unstick or added in the "Mac FAQ and Mac Tutorials" topic.
|
|
|To do
|
|-
|Look at the sticky topics about Mac in the DE Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be unstick or added in the "Mac FAQ and Mac Tutorials" topic.
|
|
|To do
|
|-
|Look at the sticky topics about Mac in the FR Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be unstick or added in the "Mac FAQ and Mac Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Mac in the EN Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be added in the "Mac FAQ and Mac Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Mac in the DE Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be added in the "Mac FAQ and Mac Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Mac in the FR Support part of the WebIG forums
then report in the discussion part of this page
which ones have to be added in the "Mac FAQ and Mac Tutorials" topic.
|
|
|To do
|
|-

|}

==Mac Team==
''They are joinable on [[EN_IRC|IRC]].''
*Jazzy (French)
*Kervala (French, English)
*Lod (French)
*SIELA1915 (English, Français, Deutsch)

=WINDOWS =

==Windows FAQ and tutorials==

==Windows Team==
*CSR Aileya (Deutsch, English)
*CSR Emiro (Deutsch, English)
*Kervala (French, English)

==Windows FAQ and To do list==

{{ToTrad|FR|FR translation needed please}}

{| border="1" cellpadding="5" cellspacing="0"
!Task
!Assigned to
!Display
!Progress
!Status
|-
|Write a tutorial for each regular technical question related to Windows.
If the tutorial already exist, please copy it in this wiki to enable the translations,

adding the link to the source.
|All the Windows team
|
Tutorial: create a new page
|To do
|
|-
|Write a Mac FAQ
|
|
|
|
|-
|Look at the sticky topics about Windows in the FR Support part of the WebIG forums
then report in the discussion part of this page which ones have to be unstick or added

in the future"Windows FAQ and Windows Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Windows in the EN Support part of the WebIG forums
then report in the discussion part of this page which ones have to be added

in the future "Windows FAQ and Windows Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Windows in the DE Support part of the WebIG forums
then report in the discussion part of this page which ones have to be added

in the future"Windows FAQ and Windows Tutorials" topic.
|
|
|To do
|
|-
|Look at the unsticky topics about Windows in the FR Support part of the WebIG forums
then report in the discussion part of this page which ones have to be added

in the future"Windows FAQ and Windows Tutorials" topic.
|
|
|To do
|
|-

|}

=More about Support=

Creating tutorials on how to install Ryzom under Linux, Mac and Windows and how to troubleshoot the most common problems on the various platforms. This part of the Wiki is the ideal place to store tricks that will be useful when a customer's got troubles!

When you create a tutorial, don't forget to add three types of categories:
*Linux, Mac, Windows or any OS
*Support
*Tutorials

{{TPInWikiRyzom}}
[[Category: Tutorials]]
[[Category: Support]]
[[Category: EN]]

Building Ryzom Client On Debian2

2014-10-02T19:12:52Z

Cacatoes: moved to another page

Building Ryzom Client On Debian2

2014-10-02T19:07:36Z

Cacatoes: /* Why should i build my own client ? */

Building Ryzom Client On Debian2

2014-10-02T19:05:57Z

Cacatoes:

Building Ryzom Client On Debian2

2014-10-02T18:59:35Z

Cacatoes: /* General */

Building Ryzom Client On Debian2

2014-10-02T18:56:47Z

Cacatoes: /* Compiling ryzom dependencies */

Building Ryzom Client On Debian2

2014-10-02T18:56:31Z

Cacatoes: /* Compiling ryzom dependencies */

Building Ryzom Client On Debian2

2014-10-02T18:55:34Z

Cacatoes: /* General */

Building Ryzom Client On Debian2

2014-10-02T18:54:01Z

Cacatoes: /* Compiling ryzom dependencies */

Building Ryzom Client On Debian2

2014-10-02T18:49:22Z

Cacatoes: /* Downloading ryzom dependencies */

Building Ryzom Client On Debian2

2014-10-02T18:49:01Z

Cacatoes:

Building Ryzom Client On Debian2

2014-10-02T18:47:49Z

Cacatoes:

Building Ryzom Client On Debian2

2014-10-02T18:46:59Z

Cacatoes: /* Sources */

Building Ryzom Client On Debian2

2014-10-02T18:45:55Z

Cacatoes: /* Starting Ryzom with the newly built client */

Building Ryzom Client On Debian2

2014-10-02T18:44:00Z

Cacatoes: /* Downloading ryzom dependencies */

Building Ryzom Client On Debian2

2014-10-02T18:41:22Z

Cacatoes: /* General */

Building Ryzom Client On Debian2

2014-10-02T18:36:49Z

Cacatoes: /* Starting Ryzom with the newly built client */

Building Ryzom Client On Debian2

2014-10-02T18:35:12Z

Cacatoes: /* Building Ryzom (dynamically linked) */

Building Ryzom Client On Debian2

2014-10-02T18:15:09Z

Cacatoes: Attempt to make a simple tutorial for debian compilation

Building Ryzom Client On Debian

2014-09-30T14:22:42Z

Cacatoes: /* Sources */

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}
{{ToTrad|FR|FR translation needed please}}

== General ==

This page applies for Debian-based GNU/Linux distributions. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client under Mac OS X]]

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.
I choosed squeeze because the libc version is pretty old, so the static binary compiled should work on (almost) every linux system.
$ command means run as simple user
# command means run as root
#$ command means run as simple user inside chroot
## command means run as root inside chroot

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] :)

== Setting up the chroot ==

Don't forget to change USER by your username or it won't work :p
# apt-get install debootstrap dchroot
$ mkdir -p /home/USER/chroot/ryzom_squeeze64
$ mkdir -p /home/USER/chroot/ryzom_squeeze32
# debootstrap --arch amd64 squeeze /home/USER/chroot/ryzom_squeeze64 http://ftp.fr.debian.org/debian
# 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 :)
# 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 :
/proc /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/dev /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/sys /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/tmp /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0

# 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

Luabind :

#$ cd packaging/luabind
#$ mkdir build && cd build
#$ cmake -DWITH_STATIC=ON ..
#$ make
## make install

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

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 :
#$ 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 :

#$ 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 ../ryzomcore/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)
## 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, libwww+libsquish+libcpptest+libluabind that 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).
Also see building a package later, this building method is the best to do that :)

== Creating a package for ryzom ==
TODO : pbuilder tutorial

== CMake options ==

=== Option specific to RyzomCore ===

*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 ===

TODO

=== Common option set to build a client ===

Standard client compilation :
#$ 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) :
#$ cmake -DFINAL_VERSION=OFF -DCMAKE_BUILD_TYPE=Debug ALLOTHEROPTIONS ..
== Auto-build script ==

A simple script to build different (static) version of the client : [http://manda.glorf.fr/client/static_build]

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]
== 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]

For the chroot & client building : [http://sevmek.free.fr/static/howto-ryzom2.0.txt]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:EN]]

Building Ryzom Client On Debian

2014-09-27T10:41:16Z

Cacatoes: /* Compiling ryzom dependencies */ fix dir

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}
{{ToTrad|FR|FR translation needed please}}

== General ==

This page applies for Debian-based GNU/Linux distributions. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client under Mac OS X]]

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.
I choosed squeeze because the libc version is pretty old, so the static binary compiled should work on (almost) every linux system.
$ command means run as simple user
# command means run as root
#$ command means run as simple user inside chroot
## command means run as root inside chroot

== Setting up the chroot ==

Don't forget to change USER by your username or it won't work :p
# apt-get install debootstrap dchroot
$ mkdir -p /home/USER/chroot/ryzom_squeeze64
$ mkdir -p /home/USER/chroot/ryzom_squeeze32
# debootstrap --arch amd64 squeeze /home/USER/chroot/ryzom_squeeze64 http://ftp.fr.debian.org/debian
# 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 :)
# 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 :
/proc /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/dev /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/sys /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/tmp /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0

# 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 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

Luabind :

#$ cd packaging/luabind
#$ mkdir build && cd build
#$ cmake -DWITH_STATIC=ON ..
#$ make
## make install

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

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 :
#$ 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 :

#$ 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 ../ryzomcore/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)
## 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, libwww+libsquish+libcpptest+libluabind that 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).
Also see building a package later, this building method is the best to do that :)

== Creating a package for ryzom ==
TODO : pbuilder tutorial

== CMake options ==

=== Option specific to RyzomCore ===

*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 ===

TODO

=== Common option set to build a client ===

Standard client compilation :
#$ 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) :
#$ cmake -DFINAL_VERSION=OFF -DCMAKE_BUILD_TYPE=Debug ALLOTHEROPTIONS ..
== Auto-build script ==

A simple script to build different (static) version of the client : [http://manda.glorf.fr/client/static_build]

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]
== 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]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:EN]]

Building Ryzom Client On Debian

2014-09-27T10:35:53Z

Cacatoes: /* Compiling ryzom dependencies */ cd to wrong directory

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}
{{ToTrad|FR|FR translation needed please}}

== General ==

This page applies for Debian-based GNU/Linux distributions. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client under Mac OS X]]

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.
I choosed squeeze because the libc version is pretty old, so the static binary compiled should work on (almost) every linux system.
$ command means run as simple user
# command means run as root
#$ command means run as simple user inside chroot
## command means run as root inside chroot

== Setting up the chroot ==

Don't forget to change USER by your username or it won't work :p
# apt-get install debootstrap dchroot
$ mkdir -p /home/USER/chroot/ryzom_squeeze64
$ mkdir -p /home/USER/chroot/ryzom_squeeze32
# debootstrap --arch amd64 squeeze /home/USER/chroot/ryzom_squeeze64 http://ftp.fr.debian.org/debian
# 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 :)
# 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 :
/proc /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/dev /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/sys /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/tmp /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0

# 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 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

Luabind :

#$ cd packaging/luabind
#$ mkdir build && cd build
#$ cmake -DWITH_STATIC=ON ..
#$ make
## make install

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

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/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 :
#$ 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 :

#$ 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 ../ryzomcore/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)
## 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, libwww+libsquish+libcpptest+libluabind that 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).
Also see building a package later, this building method is the best to do that :)

== Creating a package for ryzom ==
TODO : pbuilder tutorial

== CMake options ==

=== Option specific to RyzomCore ===

*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 ===

TODO

=== Common option set to build a client ===

Standard client compilation :
#$ 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) :
#$ cmake -DFINAL_VERSION=OFF -DCMAKE_BUILD_TYPE=Debug ALLOTHEROPTIONS ..
== Auto-build script ==

A simple script to build different (static) version of the client : [http://manda.glorf.fr/client/static_build]

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]
== 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]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:EN]]

Building Ryzom Client On Debian

2014-09-26T21:40:30Z

Cacatoes: /* Setting up the chroot */ also creating subdirs

{{tabLang|EN|DE|{{FULLPAGENAME}}|ES|FR|RU}}

{{ToTrad|DE|DE translation needed please}}
{{ToTrad|ES|ES translation needed please}}
{{ToTrad|FR|FR translation needed please}}

== General ==

This page applies for Debian-based GNU/Linux distributions. To compile Ryzom client under Mac OS X, please check this page : [[Building Ryzom Client under Mac OS X]]

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.
I choosed squeeze because the libc version is pretty old, so the static binary compiled should work on (almost) every linux system.
$ command means run as simple user
# command means run as root
#$ command means run as simple user inside chroot
## command means run as root inside chroot

== Setting up the chroot ==

Don't forget to change USER by your username or it won't work :p
# apt-get install debootstrap dchroot
$ mkdir -p /home/USER/chroot/ryzom_squeeze64
$ mkdir -p /home/USER/chroot/ryzom_squeeze32
# debootstrap --arch amd64 squeeze /home/USER/chroot/ryzom_squeeze64 http://ftp.fr.debian.org/debian
# 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 :)
# 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 :
/proc /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/dev /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/sys /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0
/tmp /home/USER/chroot/ryzom_squeeze64/proc none rbind 0 0

# 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 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

Luabind :

#$ cd packaging/luabind
#$ mkdir build && cd build
#$ cmake -DWITH_STATIC=ON ..
#$ make
## make install

libwww-dev :

#$ cd ~/dep_ryzomcore/libwww
#$ ./autogen.sh
#$ ./configure --with-ssl=no --with-zlib --with-expat --with-gnu-ld --enable-shared
#$ make
## make install

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/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 :
#$ 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 :

#$ 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 ../ryzomcore/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)
## 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, libwww+libsquish+libcpptest+libluabind that 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).
Also see building a package later, this building method is the best to do that :)

== Creating a package for ryzom ==
TODO : pbuilder tutorial

== CMake options ==

=== Option specific to RyzomCore ===

*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 ===

TODO

=== Common option set to build a client ===

Standard client compilation :
#$ 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) :
#$ cmake -DFINAL_VERSION=OFF -DCMAKE_BUILD_TYPE=Debug ALLOTHEROPTIONS ..
== Auto-build script ==

A simple script to build different (static) version of the client : [http://manda.glorf.fr/client/static_build]

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]
== 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]
<references />

{{TPInWikiRyzom}}
[[Category:Tutorials]][[Category:EN]]