OpenEmbedded for EZX
OE ( openembedded ) is an amazing tool, that compile programs! Huh
OE is made for simplify the compilation so you WILL appreciate how delicate and complex it can be coded internally AND also how its everyday use is just like a game (well at least for a dev, lol).
Please do not compare this particular "guide" to
OpenEmbedded "getting-started" wiki page, i just meant to explain one particular use of OE, step by step help to compile with OE, for EZX and Motorolafans members deserves that: they usually love developping!

First stage: the setup on a linux workstation:
(1) Install git if you don't have it.
Heh! C'mon, refer to your distros documentation for that, (on debian apt-get install git).
(2) Choose a suitable place then create its directory
Important note:
OE take only a few ( ~2?) hundred megas on the hard disk, that with all its dependencies but, later, it will download a lot of files, so make sure you have a few GIGABYTES (~5?) free on the partition you place it! Or you will have to move the folder later, witch take time
Code:
mkdir -p /home/<user>/OE.org/build/conf
i choosed the <user> folder, it is just an example,
you can decide whatever dir name and place you like to use for this also take care of replacing <user> by
your username if you want it in your "home" directory.
(3) Install bitbake first, it is the build tool OE will uses
Code:
cd /home/<user>/OE.org/
git clone git://git.openembedded.org/bitbake.git
cd bitbake
git-checkout 1.8.18
I think it is better to intentionnally retrieve bitbake version 1.8.18 on debian, as it don't require python 2.6...
(to test the latest bitbake, just clone, and don't apply the last 2 commands)
(4) Install OpenEmbedded itself
Code:
cd /home/<user>/OE.org/
git clone git://git.openembedded.org/openembedded
(5) Configuration
Code:
cp openembedded/conf/local.conf.sample build/conf/local.conf
Then edit your local.conf: you need to READ the help written inside each section to understand the file and oe
At more or less the beggining of the file, replace BBFILES field by something like:
Code:
BBFILES = "/home/<user>/OE.org/openembedded/recipes/*/*.bb"
For any ezx device, around the middle of the file, write:
Near the end, for now write:
Then, remove or comment the last line. It is a trap!
==============================================================================================================
DONE!
You saw that was easy, no?
I'm sure now you will recommend OE to anyone who want to begin developping on embedded systems. 
Now use OE everyday
: basicely:
Each time you want to compile something for your phone:- Setup the build environment.
Code:
export BBPATH=/home/<user>/OE.org/build:/home/<user>/OE.org/openembedded
export PATH=/home/<user>/OE.org/bitbake/bin:$PATH
Also note that OE is updated VERY frequently, so..- Take care of updating your tree from time to time:
Code:
cd /home/<user>/OE.org/openembedded
git pull
OE will need to download files from internet so you will need a connected computer.
Warning:WORK IN PROGRESS! WORK IN PROGRESS! WORK IN PROGRESS!
Please post comments or report error or ask any question directly here, thanks in advance!
Thanks for following, i hope to be able to write others stages, maybe one day we will be able to compile FSO2 out of this tuto, i really would love that, but our EZX devices support is only include in the DEVEL branch of OE, and brake quite frequently compared to the STABLE branch...
Have much more help and details on OE at OpenEmbedded getting started wiki page
I found a very useful blog post about bitbake and OE as well here, thanks Mr Ospite! : Neat compile/run cycle with git and OpenEmbedded | en dev | ao2.it