ArmadeusWiki - User contributions [en]

Gentoo installation prerequisites

2012-05-28T05:47:04Z

LouisX:

Works on Gentoo and Gentoo Hardened

<pre class="host">
sys-devel/binutils -multitarget
</pre>

LinuxInstall

2012-05-28T05:46:27Z

LouisX: /* Prerequisites for Linux installation */

<noinclude>
<big>How-To install Armadeus Software Development Kit (SDK) on Linux systems. This SDK is currently based on the (excellent) [http://buildroot.net/ Buildroot].</big>
</noinclude>

The installation was successfully tested on the following distributions:
* Debian Sarge (3.1), Etch (4.0), Lenny (5.0) & Squeeze
* X/KUbuntu Edgy Eft (6.10), Gutsy Gibbon (7.10), Hardy Heron (8.04) & Jaunty Jackalope (9.04)
* Ubuntu Dapper Drake (6.04), Hardy Heron (8.04), Intrepid Ibex (8.10) & Lucid Lynx (10.04) (64bits)
* Mandriva 2006
* Fedora Core 3 & 4, Fedora 10, Laughlin (14)
* Red Hat Enterprise 5.2
* Gentoo 10.0 (32 & 64 bits)
* SuSE 10.1, OpenSUSE 11.3

'''The installation may fail on:'''
* Ubuntu Karmic Koala (9.10): tslib fails to build

==Prerequisites for Linux installation==
{{Note|From here we assume that your Linux system has a ''make'' version '''greater or equal to''' 3.81. To check it:
<pre class="host">
$ make -v
GNU Make 3.81
...
</pre>
}}
For armadeus up to 3.4, make should be '''strictly''' make-3.81 (make-3.82 is too strict). A Fedora (14 and 15) -specific solution can be found later; other recent distributions such as mageia1 also have make-3.82, and a generic solution, based on configure&& make&& sudo make install can be used to install make-3.81 (which can be retrieved from http://ftp.gnu.org/gnu/make/make-6.81.tar.gz) in /usr/local/bin (and , according to one's PATH, make 3-81 can be invoked directly or as /usr/local/bin/make).

Depending on your distribution, some additional packages are required:

===Debian/Ubuntu based systems===
[[Ubuntu/Debian installation prerequisites]]

===Mandriva based systems===
[[Mandriva installation prerequisites]]

===RPM-based systems (RedHat, Fedora, CentOS)===
[[RedHat/Fedora installation prerequisites]]

===OpenSuse based systems===
[[OpenSuse installation prerequisites]]

===Gentoo based systems===
[[Gentoo installation prerequisites]]

==Get Armadeus software==
* '''If you are a "careful" user''', then download [https://sourceforge.net/projects/armadeus/files/ the latest stable installation tarball from SourceForge] and detar it wherever you want:
<pre class="host">
$ tar xjvf armadeus-4.1.tar.bz2
</pre>
* '''If you want the latest snapshot''', the whole development tree can checked out from the [[GIT]] repository. (SVN repository is no more maintained !!!)
<pre class="host">
$ git clone git://armadeus.git.sourceforge.net/gitroot/armadeus/armadeus armadeus
</pre>

* depending on your previous choice, a directory named ''armadeus/'' or ''armadeus-4.1/'' will be created on your hard-disk and will contain all the files you need.

'''Remarks''':
* '''Do not use spaces''' in the directory name !
* GIT write/push accesses are limited to the integrators ([[User:JulienB|JulienB]], [[User:Salocin68|Salocin68]], [[User:Jorasse|Jorasse]], [[User:FabienM|FabienM]])

==Configure SDK options==
{{Note|If you are new to Armadeus and have troubles compiling armadeus-4.1 using the following instructions, you may find some hints here: [[Armadeus 4.1 Troubleshots]]}}
*Go to the directory where you put the Armadeus sources:
<pre class="host">
$ cd armadeus/ (or armadeus-4.1/)
</pre>
*The first time you compile an Armadeus distribution you have to specify the target (here the APF9328) to work with.
<pre class="host">
$ make apf9328_defconfig
</pre>
This command reloads the default configuration to support your target and automatically start a Buildroot's configuration menu.

* Current valid default configurations are:
<pre class="host">
apf9328_defconfig apf27_defconfig pps_defconfig apf28_defconfig apf51_defconfig
</pre>

For PPS, please see [[APF27_PPS]] for details on its specific build.

* After some downloads, you will get the Buildroot configuration interface:

{{Note|If you ever made changes in the following steps, at any time you can reload the default configuration with the same command}}

[[Image:Menuconfig3.png]] 
*If you are not familiar with Buildroot here are some tips:
*# you can move the highlighted item with the "up"/"down" arrow keys
*# with the "left"/"right" arrow keys you can choose between "Select", "Exit" or "Help" buttons
*# "space"/"enter":
*#* selects the currently highlighted item if you are on the "Select" button
*#* go back in previous menu if you are on "Exit" button
*#* show you some Help for current item if you are on "Help" button
*# for more Help about Buildroot commands, select "Help" in the main configuration screen

*Update the memory configuration of your board:

:In menu:
:<pre class="config">System configuration ---> [*] Armadeus Device Support ---></pre>

:you can check and change the quantity of RAM available on your Armadeus board:
:[[Image:Build_config_memory.png]]
:For [[APF9328]] the memory can be either 16 or 32MiB (be sure to select 1 RAM chip)
:For [[APF27]] it could be either 64MiB or 128MiB (2 x 64MiB) (in that case be sure to select 2 chips of 64MiB instead of 1 chip of 128MiB).
:For [[APF51]] it could be either 256MiB or 512MiB (2x256MiB) (in such case be sure to select 2 chips of 256MiB instead of 1 chip of 512).
:For [[APF28]] The memory can be 128, 256, 512 or 1024MiB (be sure to select 1 RAM chip)

* You may decrease the compilation time by increasing the number of parallel jobs running simultaneously on your system (the result is not guaranteed). This option is located in
:<pre class="config">Build Options ---> (1) Number of jobs to run simultaneously</pre>

* During the toolchain/distribution automatic build, a lot of software archives are downloaded from Internet. The downloaded files are put by default in the ''armadeus/downloads/'' directory. '''If you have several views or plan to build the toolchain several times''', we advise you to put all the downloaded files in ''/local/downloads'' (for example). This is done by configuring Buildroot to use this directory for all your views. Nevertheless, buildroot will be downloaded separately for each build environment you set up.
:<pre class="config">Build options ---> (...) Download dir</pre>
:[[Image:Build_config_menu_download.png]] 
:[[Image:Build_config_download.png]]
'''Of course, ''/local/downloads'' should exists on your system and you should have writing rights on it !'''

* After the build, we advise you too to copy all the files in ''downloads/'' on a removable medium, in case you want to install the development tools on several systems.

* Now, Exit the configuration tool and save your configuration

* You can come back to this configuration menu, by typing (your changes will be kept):
<pre class="host">
make menuconfig
</pre>

==Launch build==
$ make
The toolchain and the full distribution are automatically built. During this procedure, several files are downloaded from Internet. 
'''Please wait for a while.... it takes at least one hour for the first run!''' 
By default, the downloaded files/tarball are put in the ''armadeus/downloads/'' directory. Please see the previous chapter to know how to optimize that if you plan to build several views or want to build faster.

==Enjoy the result==
The generated binary files can be found in the subdirectory ''buildroot/output/images'':
*''apf9328-u-boot.brec'' (only on [[APF9328]]): BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working (see [[BootLoader]] page)
*''XX-u-boot.bin'': U-Boot image file to be used with U-Boot itself, (see [[BootLoader#Update_U-Boot | updating U-Boot]])
*''XX-linux.bin'': Linux image to use with U-Boot, (see [[Target_Software_Installation#Linux_kernel_installation | updating Linux]])
*''XX-rootfs.jffs2'': JFFS2 filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''XX-rootfs.ubi'' (not supported on [[APF9328]]): [[UBIFS|UBI]] filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''apfXX-rootfs.tar'': for an NFS/MMC based rootfs, (see [[Network_Configuration#Boot_from_NFS | Booting from NFS]] & [[MultiMediaCard#Booting_from_MMC.2FSD | Booting from a MMC/SD]])

'''Please note the new naming convention of binary files and directories (since Armadeus 4.0)'''

*''buildroot/output/build'': contains all the build results for target filesystem, linux, busybox and u-boot...
*''buildroot/output/toolchain/'': cross compilation toolchain's build dir. Binaries usable for cross-compilation are in ''buildroot/output/host/usr/bin''.
*''buildroot/output/target/'': target filessytem before generating rootfs images

More information is available in the [http://buildroot.uclibc.org/buildroot.html Buildroot's documentation]

* Note: Previous versions (3.x) of Armadeus SDK stored the generated binary files at a different place: '' ''buildroot/binaries/XX/'' (where XX was the name of your board).

<noinclude>

You then copy the binary image to your server directory:
<pre class="host">
$ cp buildroot/output/images/* /tftpboot
</pre>

==To keep your local copy/repository up-to-date with the armadeus GIT repository==
<pre class="host">
$ git pull
</pre>
This will update your working directory to the latest release.

Note: if "git pull" fails because a directory or a file already exists, then do:
$ rm -rf <this-directory/file>
$ git pull

You can do a:
$ make apfXX_defconfig
to have the latest features automatically activated.

You have to do a '''make''' to rebuild binary files and then upload the binary files to your target.

Note: if definitively everything goes wrong while it worked before the last update.
You can apply the following procedure (all your modifications in buildroot will be lost):
$ rm -rf buildroot/
$ rm Makefile
$ git pull
$ make apfXX_defconfig
$ make
$ cp buildroot/output/images/* /tftpboot

Enjoy!
</noinclude>

Gentoo installation prerequisites

2012-05-28T05:39:05Z

LouisX: New page: Works on Gentoo and Gentoo Hardened <pre> sys-devel/binutils -multitarget </pre>

Works on Gentoo and Gentoo Hardened

<pre>
sys-devel/binutils -multitarget
</pre>

Qt/Embedded

2012-02-28T19:13:54Z

LouisX: /* Screen rotation */

Instructions to install and use QtEmbedded & Qt virtual frame buffer for Armadeus

== Introduction ==

This page will summarize the process to build, install and use Qt Embedded (previously known as Qtopia).

You will also find instructions to setup a Host development environment for simulating applications before deploying them on the target (Qt virtual frame buffer). The Builroot tree must be installed before the installation of Qt.

{{Note| We recommand at least 32 MBytes of RAM if you plan to design and run Qt based GUIs.}}

==Installation==

From November 20th 2007, Qt Embedded is now fully integrated in Armadeus Buildroot (old procedure is kept [[QtEmbedded Installation|here]]). So to install it you have to:
<pre class="host">
[armadeus]$ make menuconfig
</pre>
<pre class="config">
[*] Package Selection for the target --->
[*] Graphic libraries and applications (graphic/text) --->
*** other GUIs ***
[*] Qt --->
--- Qt
[ ] Compile with debug support
Library type (Shared library) --->
[*] Approve free license
[ ] Compatibility with Qt3
[*] Gui Module
Pixel depths --->
Fonts --->
freetype2 support (no freetype2 support) --->
[*] Enable GIF support
[ ] Enable libmng support
JPEG support (System libjpeg) --->
PNG support (No PNG support) --->
TIFF support (No TIFF support) --->
zlib support (Qt zlib) --->
(arm) The embedded platform we are making Qt for
[ ] SQL Module --->
Graphics drivers --->
Mouse drivers --->
Keyboard drivers --->
[ ] Phonon Module
[*] XML Module
[ ] XML Patterns Module
[ ] SVG Module
-*- Network Module
[ ] WebKit Module
[ ] STL support
[ ] Enable OpenSSL support
[*] Script Module
[ ] Script Tools Module
</pre>

'''(don't forget Pixel depths submenu options (at least 8 and 16))'''

*If you want touchscreen support:
<pre class="config">
Mouse drivers --->
...
[*] tslib
</pre>
then:
<pre class="host">
[armadeus]$ make
</pre>

1 hour and ~1 GBytes later (depending on your system and the configuration you choosed) your will have the beast. You can then reflash your rootfs.

==Touchscreen handling==
* Configure your touchscreen by loading the corresponding driver (depends on your APF) and calibrating it (at first use)
* Then, before launching Qt app, do
<pre class="apf">
# export QWS_MOUSE_PROTO="Tslib:/dev/input/eventXX (replace XX with the right number)
</pre>

==Keyboard handling==

===USB Keyboard===

====Qt configuration====

*If you manually build Qt, you have to add the USB keyboard driver option in the configuration:
<pre class="host">
$ configure -qt-kbd-linuxinput
</pre>

*If you let Buildroot build Qt, select the USB keyboard option in the configuration menu:
<pre class="config">
[*] Graphic libraries and applications (graphic/text) --->
*** other GUIs ***
[*] Qt --->
--- Qt
...
Mouse drivers --->
Keyboard drivers --->
[ ] tty
[*] linux input
[ ] qvfb
...
</pre>

====Linux configuration====

To use USB keyboard, there are some drivers to install in Linux.

*First open the Linux configuration menu:
<pre class="host">
[armadeus]$ make linux26-menuconfig
</pre>

*Select the keyboard drivers in the menu:
<pre class="config">
Device drivers --->
...
Input device support --->
...
*** Input Device Drivers ***
[*] Keyboards --->
--- Keyboards
<*> AT keyboard
< > Sun Type 4 and Type 5 keyboard
< > DECstation/VAXstation LK201/LK401 keyboard
< > XT keyboard
<M> Freescale MXC/IMX keypad support
< > Newton keyboard
< > Stowaway keyboard
< > GPIO Button
[*] Mice --->
...
...
</pre>

*Then clean your Linux installation and rebuild it:
<pre class="host">
[armadeus]$ make linux26-clean
[armadeus]$ make linux26
[armadeus]$ make
</pre>

====Embedded system configuration====

* First flash your new kernel and rootfs and boot the system.
* When you connect the USB keyboard to the system, a device is created in '''/dev/ttyX'''.
* Then you can tell Qt which driver to connect to the device to make it work:
<pre class="apf">
# export QWS_KEYBOARD="LinuxInput:/dev/ttyX"
</pre>

* Then you can launch an application and use your USB keyboard with it.

More infos are provided here: [http://doc.qt.nokia.com/4.7-snapshot/qt-embedded-charinput.html]

==Mouse handling==

===USB Mouse===

====Qt configuration====

*If you manually build Qt, you have to add the USB mouse driver option in the configuration:
<pre class="host">
$ configure -qt-mouse-pc .......
</pre>

*If you let Buildroot build Qt, select the USB mouse option in the configuration menu:
<pre class="config">
[*] Graphic libraries and applications (graphic/text) --->
*** other GUIs ***
[*] Qt --->
--- Qt
...
Graphics drivers --->
Mouse drivers --->
[*] pc
[ ] bus
[ ] linuxtp
[ ] yopy
[ ] vr41xx
[ ] tslib
[ ] qvfb
Keyboard drivers --->
...
</pre>

*Then build & install Qt or let Buildroot build.

====Linux configuration====

To use USB mouse, there are some drivers to install in Linux.

*First open the Linux configuration menu:
<pre class="host">
[armadeus]$ make linux26-menuconfig
</pre>

*Select the Mouse interface and PS/2 Mouse drivers in the menu:
<pre class="config">
Device drivers --->
...
Input device support --->
...
*** Userland interfaces ***
<*> Mouse interface
[*] Provide legacy /dev/psaux device
(1024) Horizontal screen resolution
(768) Vertical screen resolution
...
*** Input Device Drivers ***
[ ] Keyboards --->
[*] Mice --->
--- Mice
<M> PS/2 mouse
[*] ALPS PS/2 mouse protocol extension
[*] Logitech PS/2++ mouse protocol extension
[*] Synaptics PS/2 mouse protocol extension
[*] IBM Trackpoint PS/2 mouse protocol extension
[ ] Elantech PS/2 protocol extension
[ ] eGalax TouchKit PS/2 protocol extension
...
</pre>

*Then clean your Linux installation and rebuild it:
<pre class="host">
[armadeus]$ make linux26-clean
[armadeus]$ make linux26
[armadeus]$ make
</pre>

====Embedded system configuration====

* First flash your new kernel and rootfs and boot the system.
* When you connect the USB mouse to the system, a device is created in '''/dev/input/mouseXX'''. The touchscreen devices are also created as '''/dev/input/eventXX'''.
* To know which device is the USB mouse one, you have to check in:
<pre class="apf">
# cat /sys/class/input/mouseXX/device/name
</pre>
* Then you can tell Qt which driver to connect to the device to make it work:
**If you want the USB mouse only:
<pre class="apf">
# export QWS_MOUSE_PROTO="MouseMan:/dev/input/mouseXX"
</pre>
** For multiple pointer inputs, for example if you want to use an USB mouse along with a touchscreen, list all the possible pointers as follow:
<pre class="apf">
# export QWS_MOUSE_PROTO="MouseMan:/dev/input/mouseXX Tslib:/dev/input/eventXX"
</pre>

{{Note| For a dynamic detection of an USB mouse, you can use the automatic driver like this:
<pre class="apf">
# export QWS_MOUSE_PROTO="Tslib:/dev/input/eventXX Auto"
</pre>
}}

* Then you can launch an application and use your USB mouse with it.

More infos are provided here: [http://doc.qt.nokia.com/4.6/qt-embedded-pointer.html]

==Screen rotation==
* activate it with : ''-qt-gfx-transformed'' (from buildroot menuconfig),
* to use it on the command line (for example 270°) : ''-display transformed:rot270''
* or export the variable (for example 270°) : ''export QWS_DISPLAY=Transformed:Rot270.0
''

==Test==
If you want to test it, compile and put some examples in your TFTP directory:
<pre class="host">
$ make shell_env
$ source armadeus_env.sh
$ cd $ARMADEUS_QT_DIR/examples/widgets/
$ $ARMADEUS_QT_DIR/bin/qmake widgets.pro
$ make
...
$ cp digitalclock/digitalclock /tftpboot
$ cp calculator/calculator /tftpboot
</pre>

and then launch it on your APF (supposed you have a running & calibrated touchscreen):
<pre class="apf">
# cd /usr/bin/
# tftp -g -r calculator 192.168.0.xx (Host IP)
# chmod a+x calculator
# export QWS_MOUSE_PROTO="Tslib:/dev/input/event0"
#
# ./calculator -qws
</pre>

==Demo==
A client/server (with GUI) demo is available under: ''software/demos/ApfDacClientServer/''. It could be a good starting point to show you how to create standalone Qt applications (will probably require some modifications in ''src/build.sh'' depending on your Host Qt installation).

[[Image:qtdemo.png|center|frame|GUI with widgets taken from http://www.qt-apps.org]]

== Usage ==

By default Qt libraries are installed in /usr/lib/ directory of your target rootfs.

== How to cross-compile an application using Qt Embedded ==

The first thing you need to do is to define a specific "'''qmake''' specs directory" for armadeus. Here for example:

$ mkdir $APPLICATION_ROOT_DIR/mkspecs/linux-arm-g++

and install the two following files into this new directory: [http://www.armadeus.com/assos_downloads/qt/qmake.conf qmake.conf] & [http://www.armadeus.com/assos_downloads/qt/qplatformdefs.h qplatformdefs.h]. '''qmake.conf''' may be customized if necessary.

Then, you must define two typical environment variables :
'''QTDIR''' which defines the Qt installation path
& '''QMAKESPEC''' which defines the path to the configuration files of the '''qmake''' tool

Here two typical lines of a Qtopia application building script

$ export QTDIR=/usr/local/Trolltech/QtEmbedded-4.5.3
$ export QMAKESPEC= $APPLICATION_ROOT_DIR/mkspecs/linux-arm-g++

Adapt the '''QTDIR''' path to your own installation path and compile your code now, using theses commands:

# build the makefile with the '''qmake''' command (See Trolltech documentation for details about '''qmake'''):
$QTDIR/bin/qmake -spec my.pro
# and now compile the beast... :
$ make

Good luck....

== Phonon installation with Qt Embedded ==

=== Prerequisites ===
In order to use Phonon with Qt, first you need to install some other libraries.
You may even need to cross-compile them, depending on the platform you want to run Qt on.

==== For x86 platform ====
*You only have to install GStreamer and some plugins with the following command :
<pre class="host">
$ sudo apt-get install libgstreamer0.10-0
$ sudo apt-get install libgstreamer0.10-dev
$ sudo apt-get install libgstreamer-plugins-base0.10-0
$ sudo apt-get install libgstreamer-plugins-base0.10-dev
</pre>
{{Note | These packages are available for Linux Ubuntu ; but for other distributions, the names may vary.}}

*To use some audio, image or video format like mp3, mpeg2, png or ogg:
**First you must install on your system the needed libraries for the particular format you want (like libmpeg2, libpng, libmad...)
**Then you can install these gstreamer plugins:
<pre class="host">
$ sudo apt-get install gstreamer0.10-plugins-good
$ sudo apt-get install gstreamer0.10-plugins-ugly
</pre>
There also are other plugin packages which you can find the list at :
[http://gstreamer.freedesktop.org/documentation/ GStreamer]

==== For embedded platform ====
If you want to build Qt with Phonon for embedded platform, you'll need to cross-compile the following libraries for the same platform:
*libxml2 >= 2.7.7
*libcheck >= 0.9.8
*liboil >= 0.3.2
*gstreamer >= 0.10.0
*gst-plugins-base >= 0.10.0

There are some required libraries that you can compile and install with Buildroot:
*glib >= 2.16
*Optional:
**libpng
**tiff
**jpeg
**...

For additional audio and video formats, you have to cross-compile the corresponding libraries and then the following gstreamer's plugins :
*gst-plugins-good >= 0.10.0
*gst-plugins-ugly >= 0.10.0

=== Cross-compiling libraries ===
*First thing to do is to set the PKG_CONFIG_PATH environment variable to the directories containing your embedded libraries' pkgconfig files.

*To see what environment variable you can modify to impact the library cross-compiling, enter the command :
<pre class="host">
$ ./configure --help
</pre>
Then create a file to define all required environment variables for the cross-compiling.
For instance for glib2:
<pre class="config">
$ export CC=arm-linux-gcc
$ export CXX=arm-linux-g++
$ export CFLAGS="-I/usr/local/libxml2/include/libxml2"
$ export LDFLAGS=-L/usr/local/libxml2/lib
</pre>
And then, to create your environment, type :
<pre class="host">
$ source ENVIRONMENT_FILE
</pre>

*Finally you can configure your library like this:
<pre class="host">
$ ./configure --build=x86-linux --host=YOUR_EMBEDDED_PLATFORM --prefix==YOUR_INSTALLATION_PATH
</pre>
Then build and install the library.

=== Build Qt ===

==== For x86 platform ====
The PKG_CONFIG_PATH and pkgconfig files must be correctly set to point toward gstreamer's and glib's x86 libraries and headers.

All you need to do then is to configure Qt with the phonon option and its backend :
<pre class="host">
$ ./configure -embedded x86 -debug -no-cups -no-nis -depths 16,18,24 -no-qt3support -qvfb -phonon -phonon-backend -prefix YOUR_INSTALLATION_PATH -confirm-license
</pre>

Then build and install Qt and you will be able to use Phonon on your x86 platform.

==== For embedded platform ====
The PKG_CONFIG_PATH and pkgconfig files must be correctly set to point toward gstreamer's and glib's embedded libraries and headers.

Then you can configure Qt with glib, phonon and its backend and by adding the pkgconfig option :
<pre class="host">
$ ./configure -embedded YOUR_EMBEDDED_PLATFORM -xplatform YOUR_PLATFORM_MKSPECS -depths 16,18 -no-cups -no-nis -no-qt3support -phonon -phonon-backend -glib -prefix YOUR_INSTALLATION_PATH -force-pkg-config
</pre>

{{Note | You may need to give the cross-compiler the paths toward gstreamer's and glib's libraries and headers as configuration options.}}

=== Possible problems encountered ===
During Qt Embedded or prerequisited cross-compiling, you may get the following errors :

*''Impossible constraint in 'asm''':
It means you include the wrong headers needed by the library you compile in CFLAGS or CXXFLAGS. Do not include -I/usr/include or non-cross-compiled headers.

*''Cannot run test program'':
Your best shot is to look in configure.ac (or configure.in) and see if
there's a "cache variable" for that test. If so, you can set that
variable in your environment, to the expected answer for your target,
before running configure, and it should bypass the actual test.
If there's no cache variable, you'll need to modify configure.ac (or
configure.in) to set the variable manually, and rebuild configure.

*Do not forget to set your PKG_CONFIG_PATH variable to point toward the directory containing your embedded library pkgconfig files. By default, the x86 pkgconfig files are checked and so, errors occur.

*When installing libraries : ''arm-linux-g++: command not found''
You have to directly export the PATH toward your cross-compiler in the file libtool to get through this error.

*In gst-plugins-base, delete manually the compilation of ''icles'' in the file tests/Makefile. The lines to delete are l.377 and l.382.

== Work in progress / to do list ==

* Customization of the Qt libs to have a custom Qt/E library well designed for Armadeus usage.

==Licenses==
Since Qt 4.5.2 new licensing schemes are available: http://www.qtsoftware.com/products/licensing/licensing#qt-gnu-lgpl-v

== Links ==
* [[PyQt]]
* http://www.trolltech.com
* [http://lists.trolltech.com/qt-embedded-interest/2003-11/msg00007.html 16 colors framebuffer with Qt]
* [http://doc.trolltech.com/4.2/qtopiacore-envvars.html Qtopia Core Environment Variables]
* [http://thelins.se/learnqt/category/embedded-linux/ Tutorial on Qt setup for embedded devt]

[[Category: Qt]]
[[Category: Software]]
[[Category: Graphical User Interface]]