VideoLAN Wiki - User contributions [en]

MosaicExampleSetup

2008-07-02T09:55:48Z

X-h: /* Setup */

= Example set-up for a conference: Plans =

== Problem description ==

For a conference we needed a web stream for participants who were not able to come. The set-up needed to be flexible as well transportable, since the conference took place at two venues which were several hundred meters apart. VLC was chosen because there was already a somehow working set-up available which was modified for this conference.

== Hardware ==

We were using a dual-core AMD box (Athlon X2 4600+) with 1 GB of memory and only two PCI slots (Fujitsu Siemens PC). So nothing out of the ordinary. We had two PolyCom remote controllable cameras which can output SVIDEO signals which we feed into to BT878 based grabber cards.

== Software ==

We used the vlc version coming with Ubuntu Gutsy 0.8.6c along with xawtv for direct control of the cameras (the encoding process and buffering of the clients usually introduce a lag of a few seconds which makes it hard to steer the camera efficiently.

== Network distribution ==

One of our problems was that at one of the conference venues the network bandwidth was somehow limited and we feared to overload that network. We thus decided to stream only to a single dedicated box which is connected to a network with a much larger bandwidth. This box was restreaming the content to anyone interested.

= Details =

== Needed devices ==

=== Video ===
Grabber cards registered their devices where the camera output can be viewed from:
/dev/video0
/dev/video1

The very first step is to check, if these are working. For this, start
xawtv -c /dev/video0
and we saw a blue window, because xawtv sets the input mode to composite not SVIDEO. To change this, right-click on the blue window, and change the input to SVIDEO. I have not found a possibility to change this via the command line.

If ''video0'' is working, try the same with ''video1'' it should work as well.

=== Audio ===

The grabber cards I used, do have audio input but I only got very bad quality. With the on-board audio I got a much better quality so this was used. If you are a fan of a graphical interface try to record input from ''/dev/dsp'' (need the OSS kernel modules) with ''audacity''. Don't simply connect the output of the sound card to loudspeakers and the input of your microphone to the microphone input of your computer. The sound card may directly connect those two channels without the software having the possibility to record anything. If you find the input of the grabber cards are good enough, they are usually labeled ''/dev/dsp0'' or something like this.

== Setup ==

For a simple set-up with two equally sized images next to each other I use the following config file for vlc:

# first camera uses /dev/video0 and the on-board sound /dev/audio or /dev/dsp
new cam1 broadcast enabled
setup cam1 input v4l:/dev/video0:norm=PAL:channel=1:adev=/dev/audio
setup cam1 option rtsp-tcp
setup cam1 output #transcode{vcodec=mp4v,vb=512,scale=1}:duplicate{dst=mosaic-bridge{id=1,height=400,width=300},
select=video,dst={transcode{acodec=mp3,ab=64,channels=1}:bridge-out{id=0}},select=audio}

# second camera. Important: adev=/dev/null otherwise I couldn't get it to run
new cam2 broadcast enabled
setup cam2 input v4l:/dev/video1:norm=PAL:channel=1:adev=/dev/null
setup cam2 output #transcode{vcodec=mp4v,vb=512,scale=1}:duplicate{dst=mosaic-bridge{id=2,height=400,width=300}}

# set up for the background
new background broadcast enabled
setup background input fake:
setup background option mosaic-width=800
setup background option mosaic-height=300
setup background option mosaic-rows=1
setup background option mosaic-cols=2
setup background option mosaic-position=1
setup background option mosaic-order="1,2"
setup background option fake-file="back.gif"
setup background option fake-width=800
setup background option fake-height=300
setup background option fake-fps="8"
setup background output #transcode{sfilter=mosaic,soverlay,vcodec=mp4v,acodec=mp3,ab=64,channels=1,scale=1}:bridge-in{id-offset=100}:std{access=http{mime=video/x-asf-stream},mux=asf,dst=:8080}

# put it all together
control background play
control cam1 play
control cam2 play

For us it was not so important to have both images the same. The first camera just showed the audience while the second one looked at the projections made which needed to be of higher quality. We used therefore a special background image with a logo in the bottom left corner and this configuration:

new cam1 broadcast enabled
setup cam1 input v4l:/dev/video0:norm=PAL:channel=1:adev=/dev/audio
setup cam1 option rtsp-tcp
setup cam1 output #transcode{vcodec=mp4v,vb=384,scale=1}:duplicate{dst=mosaic-bridge{id=1,height=300,width=400},select=video,dst={transcode{acodec=mp3,ab=64,channels=1}:bridge-out{id=0}},select=audio}

new cam2 broadcast enabled
setup cam2 input v4l:/dev/video1:norm=PAL:channel=1:adev=/dev/null
setup cam2 output #transcode{vcodec=mp4v,vb=1500,scale=1}:duplicate{dst=mosaic-bridge{id=2,height=600,width=800},select=video}

new background broadcast enabled
setup background input fake:
setup background option mosaic-width=1200
setup background option mosaic-height=600
setup background option mosaic-rows=2
setup background option mosaic-cols=3
setup background option mosaic-position=1
setup background option mosaic-order="1,2,0,0,0,0"
setup background option fake-file="aei3.gif"
setup background option fake-width=1200
setup background option fake-height=600
setup background option fake-fps="8"
setup background option mosaic-keep-picture=1
setup background option mosaic-keep-aspect-ratio=1
setup background output #transcode{sfilter=mosaic,soverlay,vcodec=mp4v,vb=2000,acodec=mp3,ab=64,channels=1,scale=1}:bridge-in{id-offset=100}:std{access=http{mime=video/x-asf-stream},mux=asf,dst=:8080}

control background play
control cam1 play
control cam2 play

Either of these set-ups will start a streaming server listening on port 8080 for incoming http connections.

Out next problem was, how shall we prevent our small internet connection from the conference venue from being saturated?

== Internet setup ==

We used a very simple but effective way. For this we not only needed our streaming server (from now on named '''origin'''), but also another server on a much faster network (named '''broadcast'''). We started the server on '''origin''' with

vlc -vvv --color -I telnet --vlm-conf conference.conf --ttl 10 --upd-caching 2000

Then we start a ssh tunnel from '''origin''' to '''broadcast''' (best placed into a screen environment):

ssh -N -c blowfish -R8000:localhost:8080 account@broadcast

This will forward the local port 8080 (on '''origin''') to port 8000 on '''broadcast'''.

Finally, we start another vlc instance on '''broadcast''' to restream the original stream:

vlc -vvv http://localhost:8000/ --udp-caching 1500 --sout '#standard{access=http{mime=video/x-ms-asf},mux=asf,dst:7070}'

== Final tips ==

=== Port multiplication ===
If you need to "multiply" a port easily, you can use iptables on Linux:

#possibly not all of these modules are strictly needed:
modprobe xt_tcpup
modprobe ip_tables
modprobe iptable_filter
modprobe ip_conntraqck
modprobe iptable_nat
modprobe ipt_state
modprobe ipt_MASQUERADE
modprobe ipt_REDIRECT

echo "1" > /proc/sys/net/ipv4/ip_forward

# I'm flushing everything here, this may not be good for you
iptables -F
iptables -F -t nat
iptables -A INPUT -i lo -j ACCEPT
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8080 -j REDIRECT --to-ports 7070

This will forward all requests to port 8080 transparently to port 7070 (where our broadcast server listens). Note: Port 8080 might be better because some firewalls allow only http related ports out and 8080 is a typical proxy port.

= Credits =

Thanks a lot for the folks on #videolan, especially ILEoo for helping me a lot when need was great! Without your help I don't think I would have finished this set-up in time!

ARMCompileOldPDA

2007-09-05T14:43:11Z

X-h: ogg move from cvs to subversion

== Cross compile VLC for ARM-based platforms ==

Last updated: v0.0.2, 19 march 2004
This document describes all the steps to cross compile vlc for ARM based platforms. It describes how to build a cross compilation toolchain, how to build the libraries needed by vlc and the compilation of the vlc itself.

== Introduction ==

This document is only a first draft. It does not intend to cover all subjects and is written for vlc version 0.7.2. You may still have some problems at some steps or find better way to do them. If you have any comment do not hesitate to contact us.
Which platforms are targeted ?

I will describe here how to compile vlc for an ARM based PDA running linux. It includes for example :

* Compaq - iPaq (H36xx, H38xx,...), using Familiar Linux
** GNU Portable Environment (GPE)
** Opie
* YOPY/Linupy
* Zaurus

== Requirements for cross-compilation ==
=== Why cross-compiling ? ===

It is of course possible to compile directly on the targeted platform. But there are a lot of great advantages to cross-compile :

* The most important one is probably the speed, because a desktop computer is most of the time faster than a PDA for compilation.
* Another big problem is that a complete compilation toolchain does take a great amount of disk space. And this space is usually very limited on embedded systems.
* And there also may not be enough memory to compile big files.

==Building the toolchain==
===Prerequisite===
====Importants paths====

During this section, we will use the following paths :

I would personally advise to compile everything as a normal user and then install everything as root.

====${SRCDIR}====
This is where the sources will be located and where the compilation will be done. (eg: /usr/src or /home/foobar/arm-src).

====${PREFIX}====

This is where you want to install your cross compilation toolchain. It can be either installed system-wide (in /usr/local/arm/2.95.3 for example). Installation steps (i.e. make install) will have to be done as root. Or it can be installed in user-land, for the user's own use (/home/foobar/arm/2.95.3 for example). In this paper, the chosen prefix is /usr/local/arm/2.95.3, you will have to adapt the commands to what you choose..

====Files needed====

Download the following files and put them in the ${SRCDIR}. Most of them are available on the "VideoLAN website".

* binutils-2.11.2.tar.gz
* linux-2.4.19.tar.bz2
* patch-2.4.19-rmk4.bz2
* gcc-2.95.3.tar.gz
* gcc-2.95.3.diff.bz2
* gcc-2.95.3.diffbis.bz2
* gcc-2.95.3.diff2
* glibc-2.2.5.tar.gz
* glibc-linuxthreads-2.2.5.tar.gz
* SDL-1.2.5.tar.gz
* glib-1.2.10.tar.gz
* ffmpeg.tar.gz
* mad-0.14.2b.tar.gz
* flac-1.1.0.tar.gz
* libdvbpsi-0.1.2.tar.gz
* a52dec-0.7.4.tar.gz

==Binutils==

Compiling binutils is pretty simple :
tar -xzf binutils-2.11.2.tar.gz
cd binutils-2.11.2
./configure --target=arm-linux --prefix=/usr/local/arm/2.95.3
make
make install

==Preparing linux kernel==

Before building the glibc library the right kernel header files should be available. Therefor the kernel that is going to be used needs to be prepared so all necessary header files are present. Follow these steps.
tar -xzf linux-2.4.19.tar.bz2
bunzip2 patch-2.4.19-rmk4.bz2
cd linux-2.4.19
make mrproper
patch -p1 < ../patch-2.4.19-rmk4.bz2
make clean ARCH=arm CROSS_COMPILE=arm-linux-
make ARCH=arm h3600_config

'''Do not forget''' to save the configuration even if no changes are made !
make ARCH=arm menuconfig
make symlinks ARCH=arm CROSS_COMPILE=arm-linux-
mkdir -p /usr/local/arm/2.95.3/arm-linux/include
cp -Rf include/asm include/asm-arm include/linux \
/usr/local/arm/2.95.3/arm-linux/include
cd /usr/local/arm/2.95.3/arm-linux
ln -s include sys-linux

==Basic cross compiler (gcc)==

tar -xvzf gcc-2.95.3.tar.gz
bunzip2 gcc-2.95.3.diff.bz2
bunzip2 gcc-2.95.3.diffbis.bz2
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diff
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diffbis
cd gcc-2.95.3
./configure --target=arm-linux --disable-threads --enable-languages=c \
--prefix=/usr/local/arm/2.95.3 --with-headers=linux-2.4.19/include
make
make install

==Compiling glibc==
Depending on your target, you may choose another glibc version (eg: 2.1.3 for linupy 1.4)
tar -xvzf glibc-2.2.5.tar.gz
cd glibc-2.2.5
tar -xvzf ../glibc-linuxthreads-2.2.5.tar.gz
CC=arm-linux-gcc ./configure arm-linux --target=arm-linux \
--prefix=/usr/local/arm/2.95.3/arm-linux --enable-add-ons

The following step takes quite a long time!
CC=arm-linux-gcc make

If you have problems compiling glibc due to pread/pwrite, edit sysdeps/unix/sysv/linux/kernel-features.h and turn __ASSUME_PREAD_SYSCALL and __ASSUME_PWRITE_SYSCALL from 1 to 0.
CC=arm-linux-gcc make install

==Full cross compiler (gcc)==

Now it is time to build a cross-compiler that can built user space libraries too. Follow these steps:
rm -Rf gcc-2.95.3
tar -xvzf gcc-2.95.3.tar.gz
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diff
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diff2
cd gcc-2.95.3
./configure --target=arm-linux --prefix=/usr/local/arm/2.95.3
make
make install

==Misc==

Add /usr/local/arm/2.95.3/bin to your PATH. Add the following line (depends on your shell) to your shell's configuration file :
export PATH=/usr/local/arm/2.95.3/bin:$PATH

I would advise you to completely log out and then log in again, so that the change would be taken into account. You can now check that when you type arm-linux-gcc, it launches the cross-compiler.

Next are some packages that you may compile by yourself, but I found it was easier to use the precompiled packages. You can take them at "ipkgfind">. You may find packages with other version numbers which should not be a problem.

* libgcc1_3.1.1-1_arm.ipk This provides libgcc.so.1 which is needed to compile some libraries.
* xlibs_4.1-5_arm.ipk, xlibs-dev_4.1.0-16_arm.ipk Those are the libraries ans the development files for X windows.
* zlib1g_1.1.4-3_arm.ipk, zlib1g-dev_1.1.3-fam1_arm.ipk These libraries are needed by some libraries to compile.

Install these packages on your compiler box in /usr/local/arm/2.95.3/arm-linux : You can use the script install.sh :

#!/bin/sh
# script to install .ipk into the arm-toolchain
# usage : ./install.sh foobar.ipk

if ! tar -xvzf $1 2> /dev/null
then
ar xv $1 2> /dev/null
fi
cp data.tar.gz /usr/local/arm/2.95.3/arm-linux
cd /usr/local/arm/2.95.3/arm-linux
tar -xvzf data.tar.gz

==Setting up Opie cross-compile environment==

Download the Opie SDK from the website [http://opie.handhelds.org/ OPIE website] using the menuitem "Download Opie SDK" or try the direct link here: "Download Opie SDK". Download all files to your ${SOURCES}/opie directory.
Opie SDK

The Opie SDK does not come with a README file or installation instructions. I give them here instead. There are two tar files in the download a OpieSDK.tar.gz2 and a kdevelop_src.tar.bz2. The last file is a modified kdevelop for use with the OpieSDK. In this tutorial we will not use that. Unpack OpieSDK.tar.bz2 in your sources cd ${SOURCES}/opie directory.
cd ${SOURCES}/opie
tar -xjvf OpieSdk.tar.bz2

It creates a directories structure ${SOURCES}/opie/opt/OpieSDK. Inside that directory a script is present to start_kdevelop. Modify this script so that it uses the correct paths for you setup.
#!/bin/sh
source ${SOURCES}/opie/opt/OpieSdk/dev_env

export KDEDIR=${SOURCES}/opie/opt/OpieSdk/kde
export PATH=${SOURCES}/opie/opt/OpieSdk/kde/bin:$PATH
kbuildsycoca
kdevelop

Save the script. Do the same with the script arm_source
source ${SOURCES}/opie/opt/OpieSdk/dev_env
export QTDIR=$QTDIR_ARM
export OPIEDIR=$OPIEDIR_ARM

Save the script and modify the script host_source in the same manner as above.
source ${SOURCES}/opie/opt/OpieSdk/dev_env
export QTDIR=$QTDIR_NAT
export OPIEDIR=$OPIEDIR_NAT

Save the script and modify the script dev_env in the same manner as above.
export PYTHONPATH=${SOURCES}/opie/opt/OpieSdk/python/opie:${SOURCES}/opie/opt/OpieSdk/python/sip
export PATH=/usr/local/arm/2.95.3/bin:/opt/OpieSdk/host_tools:${SOURCES}/opie/opt/OpieSdk/opie/x86/qt-2.3.7/bin:$PATH
export PATH=${SOURCES}/opie/opt/OpieSdk/opie/x86/qmake:$PATH
export QTDIR_NAT=${SOURCES}/opie/opt/OpieSdk/opie/x86/qt-2.3.7
export OPIEDIR_NAT=${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk
export QTDIR_ARM=${SOURCES}/opie/opt/OpieSdk/opie/arm/qt-2.3.7
export OPIEDIR_ARM=${SOURCES}/opie/opt/OpieSdk/opie/arm/sdk
export OPIE_SDK_BASE=${SOURCES}/opie/opt/OpieSdk/
export OPIE_SDK_QMAKE_BASE=${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk/mkspecs/qws/
export OPIE_DOC=${SOURCES}/opie/opt/OpieSdk/apidocs

export LD_LIBRARY_PATH=${SOURCES}/opie/opt/OpieSdk/sip/lib:$OPIEDIR_NAT/lib:$QTDIR_NAT/lib:$LD_LIBRARY_PATH
export OPIE_LANGUAGES=de:en:cz:da:dk:es:fr:hu:it:ja:ko:lv:mk:nl:no:pl:pt:pt_BR:ru:sl:zh_CN:zh_TW

The symbolic linke to the tool qmake points now to the wrong place. We need to fix this symbolic link. Here is the way to do that.
cd host_tools
ln -sf ${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk/qmake/qmake qmake
cd ../

Now it is time to fire up our development environment and start hacking in Opie.

==Cross compiling libraries needed by vlc==

Download ipaq-config.site to ${SOURCES}. When downloading source tarballs copy them to your ${SOURCES} directory. Each section is supposed to begin with cd ${SOURCES}.

===SDL===

It is not clean at all but did not found a better working method. Using config.site it compiles well, but when linking with vlc there are problems !

/usr/local/arm/2.95.3/arm-linux/bin should contain the cross compiler without the prefix arm-linux-.
tar -xvzf SDL-1.2.5.tar.gz
cd SDL-1.2.5
./configure --enable-release --target=arm-linux --host=arm-linux \
--disable-esd \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr \
--x-includes=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/include \
--x-libraries=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/lib \
--disable-video-opengl

export PATH=/usr/local/arm/2.95.3/arm-linux/bin:$PATH

make && make install

===Glib/GTK+===

tar -xvzf glib-1.2.10.tar.gz
cd glib-1.2.10
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make
make install
cd ..
tar -xvzf gtk+-1.2.10.tar.gz
cd gtk+-1.2.10
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr --with-glib=../glib-1.2.10
make
make install

===ffmpeg===

tar -xvzf ffmpeg.tar.gz
cd ffmpeg
./configure --arch=armv4l --cc=arm-linux-gcc --disable-mmx \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr --enable-shared
cd libavcodec
make

Vlc does not require that you install ffmpeg.

===mad===

tar -xvzf mad-0.14.2b.tar.gz
cd mad-0.14.2b
./configure --enable-release --target=arm-linux --host=arm-linux \
--disable-esd \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr \
--x-includes=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/include \
--x-libraries=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/lib \
--disable-video-opengl
export PATH=/usr/local/arm/2.95.3/arm-linux/bin:$PATH
make

===gpe===

Not described.

===tremor===

Tremor is an integer decoder for the vorbis audio codec. Download the source through subversion at the "xiph.org" website.

svn co http://svn.xiph.org/trunk/Tremor
cd Tremor
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make

===ogg===

For ogg, it is the same as Tremor.
svn co http://svn.xiph.org/trunk/ogg
cd ogg
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make

===flac===

tar -xvzf flac-1.1.0.tar.gz
cd flac-1.1.0
./configure --enable-release --host=arm-linux --target=arm-linux \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr

It will probably fail (due to the xmms plugin), but it is not a problem, we will continue installation by hand.
cp -Rf include/FLAC /usr/local/arm/2.95.3/arm-linux/include
cd src/libFLAC
make install

===libdvbpsi===

tar -xvzf libdvbpsi-0.1.2.tar.gz
cd libdvbpsi-0.1.2
./bootstrap
./configure --target=arm-linux --host=arm-linux
make

===a52===

tar -xvzf a52dec-0.7.4.tar.gz
cd a52dec-0.7.4
./configure --enable-release --host=arm-linux --target=arm-linux \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make && make install

==Cross compiling vlc itself==

First of all, run the ./bootstrap script. Then run one of the ipkg/rules.*, according to what you want to compile. Finally you just have to type make and you'll get a stand alone vlc.

Run arm-linux-strip to remove symbols and so the size of the file, and now you can test it easily on your PDA.

Enjoy !

==Version==
Made by Marc Ariberti and Jean-Paul Saman.
Adapted to the wiki by [[User:J-b|Jean-Baptiste Kempf]].

ARMCompileOldPDA

2007-09-05T14:32:30Z

X-h: Update Tremor for subversion (was cvs)

== Cross compile VLC for ARM-based platforms ==

Last updated: v0.0.2, 19 march 2004
This document describes all the steps to cross compile vlc for ARM based platforms. It describes how to build a cross compilation toolchain, how to build the libraries needed by vlc and the compilation of the vlc itself.

== Introduction ==

This document is only a first draft. It does not intend to cover all subjects and is written for vlc version 0.7.2. You may still have some problems at some steps or find better way to do them. If you have any comment do not hesitate to contact us.
Which platforms are targeted ?

I will describe here how to compile vlc for an ARM based PDA running linux. It includes for example :

* Compaq - iPaq (H36xx, H38xx,...), using Familiar Linux
** GNU Portable Environment (GPE)
** Opie
* YOPY/Linupy
* Zaurus

== Requirements for cross-compilation ==
=== Why cross-compiling ? ===

It is of course possible to compile directly on the targeted platform. But there are a lot of great advantages to cross-compile :

* The most important one is probably the speed, because a desktop computer is most of the time faster than a PDA for compilation.
* Another big problem is that a complete compilation toolchain does take a great amount of disk space. And this space is usually very limited on embedded systems.
* And there also may not be enough memory to compile big files.

==Building the toolchain==
===Prerequisite===
====Importants paths====

During this section, we will use the following paths :

I would personally advise to compile everything as a normal user and then install everything as root.

====${SRCDIR}====
This is where the sources will be located and where the compilation will be done. (eg: /usr/src or /home/foobar/arm-src).

====${PREFIX}====

This is where you want to install your cross compilation toolchain. It can be either installed system-wide (in /usr/local/arm/2.95.3 for example). Installation steps (i.e. make install) will have to be done as root. Or it can be installed in user-land, for the user's own use (/home/foobar/arm/2.95.3 for example). In this paper, the chosen prefix is /usr/local/arm/2.95.3, you will have to adapt the commands to what you choose..

====Files needed====

Download the following files and put them in the ${SRCDIR}. Most of them are available on the "VideoLAN website".

* binutils-2.11.2.tar.gz
* linux-2.4.19.tar.bz2
* patch-2.4.19-rmk4.bz2
* gcc-2.95.3.tar.gz
* gcc-2.95.3.diff.bz2
* gcc-2.95.3.diffbis.bz2
* gcc-2.95.3.diff2
* glibc-2.2.5.tar.gz
* glibc-linuxthreads-2.2.5.tar.gz
* SDL-1.2.5.tar.gz
* glib-1.2.10.tar.gz
* ffmpeg.tar.gz
* mad-0.14.2b.tar.gz
* flac-1.1.0.tar.gz
* libdvbpsi-0.1.2.tar.gz
* a52dec-0.7.4.tar.gz

==Binutils==

Compiling binutils is pretty simple :
tar -xzf binutils-2.11.2.tar.gz
cd binutils-2.11.2
./configure --target=arm-linux --prefix=/usr/local/arm/2.95.3
make
make install

==Preparing linux kernel==

Before building the glibc library the right kernel header files should be available. Therefor the kernel that is going to be used needs to be prepared so all necessary header files are present. Follow these steps.
tar -xzf linux-2.4.19.tar.bz2
bunzip2 patch-2.4.19-rmk4.bz2
cd linux-2.4.19
make mrproper
patch -p1 < ../patch-2.4.19-rmk4.bz2
make clean ARCH=arm CROSS_COMPILE=arm-linux-
make ARCH=arm h3600_config

'''Do not forget''' to save the configuration even if no changes are made !
make ARCH=arm menuconfig
make symlinks ARCH=arm CROSS_COMPILE=arm-linux-
mkdir -p /usr/local/arm/2.95.3/arm-linux/include
cp -Rf include/asm include/asm-arm include/linux \
/usr/local/arm/2.95.3/arm-linux/include
cd /usr/local/arm/2.95.3/arm-linux
ln -s include sys-linux

==Basic cross compiler (gcc)==

tar -xvzf gcc-2.95.3.tar.gz
bunzip2 gcc-2.95.3.diff.bz2
bunzip2 gcc-2.95.3.diffbis.bz2
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diff
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diffbis
cd gcc-2.95.3
./configure --target=arm-linux --disable-threads --enable-languages=c \
--prefix=/usr/local/arm/2.95.3 --with-headers=linux-2.4.19/include
make
make install

==Compiling glibc==
Depending on your target, you may choose another glibc version (eg: 2.1.3 for linupy 1.4)
tar -xvzf glibc-2.2.5.tar.gz
cd glibc-2.2.5
tar -xvzf ../glibc-linuxthreads-2.2.5.tar.gz
CC=arm-linux-gcc ./configure arm-linux --target=arm-linux \
--prefix=/usr/local/arm/2.95.3/arm-linux --enable-add-ons

The following step takes quite a long time!
CC=arm-linux-gcc make

If you have problems compiling glibc due to pread/pwrite, edit sysdeps/unix/sysv/linux/kernel-features.h and turn __ASSUME_PREAD_SYSCALL and __ASSUME_PWRITE_SYSCALL from 1 to 0.
CC=arm-linux-gcc make install

==Full cross compiler (gcc)==

Now it is time to build a cross-compiler that can built user space libraries too. Follow these steps:
rm -Rf gcc-2.95.3
tar -xvzf gcc-2.95.3.tar.gz
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diff
patch -p1 -d gcc-2.95.3 < gcc-2.95.3.diff2
cd gcc-2.95.3
./configure --target=arm-linux --prefix=/usr/local/arm/2.95.3
make
make install

==Misc==

Add /usr/local/arm/2.95.3/bin to your PATH. Add the following line (depends on your shell) to your shell's configuration file :
export PATH=/usr/local/arm/2.95.3/bin:$PATH

I would advise you to completely log out and then log in again, so that the change would be taken into account. You can now check that when you type arm-linux-gcc, it launches the cross-compiler.

Next are some packages that you may compile by yourself, but I found it was easier to use the precompiled packages. You can take them at "ipkgfind">. You may find packages with other version numbers which should not be a problem.

* libgcc1_3.1.1-1_arm.ipk This provides libgcc.so.1 which is needed to compile some libraries.
* xlibs_4.1-5_arm.ipk, xlibs-dev_4.1.0-16_arm.ipk Those are the libraries ans the development files for X windows.
* zlib1g_1.1.4-3_arm.ipk, zlib1g-dev_1.1.3-fam1_arm.ipk These libraries are needed by some libraries to compile.

Install these packages on your compiler box in /usr/local/arm/2.95.3/arm-linux : You can use the script install.sh :

#!/bin/sh
# script to install .ipk into the arm-toolchain
# usage : ./install.sh foobar.ipk

if ! tar -xvzf $1 2> /dev/null
then
ar xv $1 2> /dev/null
fi
cp data.tar.gz /usr/local/arm/2.95.3/arm-linux
cd /usr/local/arm/2.95.3/arm-linux
tar -xvzf data.tar.gz

==Setting up Opie cross-compile environment==

Download the Opie SDK from the website [http://opie.handhelds.org/ OPIE website] using the menuitem "Download Opie SDK" or try the direct link here: "Download Opie SDK". Download all files to your ${SOURCES}/opie directory.
Opie SDK

The Opie SDK does not come with a README file or installation instructions. I give them here instead. There are two tar files in the download a OpieSDK.tar.gz2 and a kdevelop_src.tar.bz2. The last file is a modified kdevelop for use with the OpieSDK. In this tutorial we will not use that. Unpack OpieSDK.tar.bz2 in your sources cd ${SOURCES}/opie directory.
cd ${SOURCES}/opie
tar -xjvf OpieSdk.tar.bz2

It creates a directories structure ${SOURCES}/opie/opt/OpieSDK. Inside that directory a script is present to start_kdevelop. Modify this script so that it uses the correct paths for you setup.
#!/bin/sh
source ${SOURCES}/opie/opt/OpieSdk/dev_env

export KDEDIR=${SOURCES}/opie/opt/OpieSdk/kde
export PATH=${SOURCES}/opie/opt/OpieSdk/kde/bin:$PATH
kbuildsycoca
kdevelop

Save the script. Do the same with the script arm_source
source ${SOURCES}/opie/opt/OpieSdk/dev_env
export QTDIR=$QTDIR_ARM
export OPIEDIR=$OPIEDIR_ARM

Save the script and modify the script host_source in the same manner as above.
source ${SOURCES}/opie/opt/OpieSdk/dev_env
export QTDIR=$QTDIR_NAT
export OPIEDIR=$OPIEDIR_NAT

Save the script and modify the script dev_env in the same manner as above.
export PYTHONPATH=${SOURCES}/opie/opt/OpieSdk/python/opie:${SOURCES}/opie/opt/OpieSdk/python/sip
export PATH=/usr/local/arm/2.95.3/bin:/opt/OpieSdk/host_tools:${SOURCES}/opie/opt/OpieSdk/opie/x86/qt-2.3.7/bin:$PATH
export PATH=${SOURCES}/opie/opt/OpieSdk/opie/x86/qmake:$PATH
export QTDIR_NAT=${SOURCES}/opie/opt/OpieSdk/opie/x86/qt-2.3.7
export OPIEDIR_NAT=${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk
export QTDIR_ARM=${SOURCES}/opie/opt/OpieSdk/opie/arm/qt-2.3.7
export OPIEDIR_ARM=${SOURCES}/opie/opt/OpieSdk/opie/arm/sdk
export OPIE_SDK_BASE=${SOURCES}/opie/opt/OpieSdk/
export OPIE_SDK_QMAKE_BASE=${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk/mkspecs/qws/
export OPIE_DOC=${SOURCES}/opie/opt/OpieSdk/apidocs

export LD_LIBRARY_PATH=${SOURCES}/opie/opt/OpieSdk/sip/lib:$OPIEDIR_NAT/lib:$QTDIR_NAT/lib:$LD_LIBRARY_PATH
export OPIE_LANGUAGES=de:en:cz:da:dk:es:fr:hu:it:ja:ko:lv:mk:nl:no:pl:pt:pt_BR:ru:sl:zh_CN:zh_TW

The symbolic linke to the tool qmake points now to the wrong place. We need to fix this symbolic link. Here is the way to do that.
cd host_tools
ln -sf ${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk/qmake/qmake qmake
cd ../

Now it is time to fire up our development environment and start hacking in Opie.

==Cross compiling libraries needed by vlc==

Download ipaq-config.site to ${SOURCES}. When downloading source tarballs copy them to your ${SOURCES} directory. Each section is supposed to begin with cd ${SOURCES}.

===SDL===

It is not clean at all but did not found a better working method. Using config.site it compiles well, but when linking with vlc there are problems !

/usr/local/arm/2.95.3/arm-linux/bin should contain the cross compiler without the prefix arm-linux-.
tar -xvzf SDL-1.2.5.tar.gz
cd SDL-1.2.5
./configure --enable-release --target=arm-linux --host=arm-linux \
--disable-esd \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr \
--x-includes=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/include \
--x-libraries=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/lib \
--disable-video-opengl

export PATH=/usr/local/arm/2.95.3/arm-linux/bin:$PATH

make && make install

===Glib/GTK+===

tar -xvzf glib-1.2.10.tar.gz
cd glib-1.2.10
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make
make install
cd ..
tar -xvzf gtk+-1.2.10.tar.gz
cd gtk+-1.2.10
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr --with-glib=../glib-1.2.10
make
make install

===ffmpeg===

tar -xvzf ffmpeg.tar.gz
cd ffmpeg
./configure --arch=armv4l --cc=arm-linux-gcc --disable-mmx \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr --enable-shared
cd libavcodec
make

Vlc does not require that you install ffmpeg.

===mad===

tar -xvzf mad-0.14.2b.tar.gz
cd mad-0.14.2b
./configure --enable-release --target=arm-linux --host=arm-linux \
--disable-esd \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr \
--x-includes=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/include \
--x-libraries=/usr/local/arm/2.95.3/arm-linux/usr/X11R6/lib \
--disable-video-opengl
export PATH=/usr/local/arm/2.95.3/arm-linux/bin:$PATH
make

===gpe===

Not described.

===tremor===

Tremor is an integer decoder for the vorbis audio codec. Download the source through subversion at the "xiph.org" website.

svn co http://svn.xiph.org/trunk/Tremor
cd Tremor
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make

===ogg===

For ogg, it is the same as Tremor.
cvs -d :pserver:anoncvs@xiph.org:/usr/local/cvsroot login
cvs -d :pserver:anoncvs@xiph.org:/usr/local/cvsroot co ogg
cd ogg
CONFIG_SITE=../ipaq-config.site ./configure \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make

===flac===

tar -xvzf flac-1.1.0.tar.gz
cd flac-1.1.0
./configure --enable-release --host=arm-linux --target=arm-linux \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr

It will probably fail (due to the xmms plugin), but it is not a problem, we will continue installation by hand.
cp -Rf include/FLAC /usr/local/arm/2.95.3/arm-linux/include
cd src/libFLAC
make install

===libdvbpsi===

tar -xvzf libdvbpsi-0.1.2.tar.gz
cd libdvbpsi-0.1.2
./bootstrap
./configure --target=arm-linux --host=arm-linux
make

===a52===

tar -xvzf a52dec-0.7.4.tar.gz
cd a52dec-0.7.4
./configure --enable-release --host=arm-linux --target=arm-linux \
--prefix=/usr/local/arm/2.95.3/arm-linux/usr
make && make install

==Cross compiling vlc itself==

First of all, run the ./bootstrap script. Then run one of the ipkg/rules.*, according to what you want to compile. Finally you just have to type make and you'll get a stand alone vlc.

Run arm-linux-strip to remove symbols and so the size of the file, and now you can test it easily on your PDA.

Enjoy !

==Version==
Made by Marc Ariberti and Jean-Paul Saman.
Adapted to the wiki by [[User:J-b|Jean-Baptiste Kempf]].