
Originally Posted by
kundancool
I am trying to develop applications for linux on linux (ubuntu as i use it)
In the firmware development section?

Originally Posted by
kundancool
I would at least ask peoples to explain what sdk to download
I would say a sdk for A1200 or E6 with some modifications. But it is hard to say which one. It depends if
you wonna go a legal way by using a reverse engineered sdk or a half stolen sdk with adaption. It is like personal attitude.
Also it depends on what you wonna do. If you want develop some applications you can start with every sdk. All will give you nice functions to develop applications. But when you want to improve some applications it would be easier to stick to the developers used sdk. Furthermore it depends on the libraries on your phone/firmware version maybe you need to reverse engineer some libraries
to fine tune your sdk.
In principle there is no standard sdk several people was working on different sdk's. There are different headers from:
samr7 foxe6 (ruthfox) blackhawk donga eakrin and others (forgot somebody sorry)

Originally Posted by
kundancool
and a little more precise question, like : how to have ubuntu ready to develop ezx softs...
That is a realy global question. I think you not even started trying to make an enviroment for developing.
I think it is realy important to start to try there are some informations around, it is also good to read some
package documentation from released toolchains. To find solutions is the daily business of a programmer.
With some linux and compile knowledge it is not so hard to do it.
First you need a crosstool or a toolchain to build one. (samr7, kegel, mkezx, openembedded)
Second you need a sdk for your phone model now it doesn't matter which one.
Third you need the libraries from your phone.
Fourth you need to setup the enviroment for sdk/crosstool depends on where you installed everything.
Fith you need a hello world program to check if the enviroment is setup right.
Zero you need to start (include reading and trying) and then asking precise when you are stuck.
There are different ways and possibilities to reach the goal.

Originally Posted by
kundancool
Easy steps you know you will have to do, like wich scripts are you using at bootup to setup the environemnt
I think it isn't a good idea to setup the enviroment at bootup. It could be that you want compile something for the host.
And if you have set advanced parameter in your enviroment script there could be different for other libraries or programs you want to compile.
In the end now I have talked to much so here is one example how to do it. The everything in one thread solution.
This is the fastest and easiest way with a precompiled crosstool and not so much knowledge is needed.
Keep in mind many people did a lot of work for each part that it makes so simple for you.
It is realy funny first there was a sdk for linux but no step by step tutorial.
Then eakrin made a realy good one for cygwin and then principle and structure was ported back to Linux. 
So here Lubomyr's howto from motofanru:
1. package you will need
make
automake
autoconf
patch
2. Libraries from phone
Code:
cd /usr/lib
tar zcvf /mmc/mmca1/a1200-lib.tar.gz *
3. The crosstool from MKEZX toolchain (Jeremy)
RapidShare: 1-CLICK Web hosting - Easy Filehosting
4. The sdk here it is from Blackhawk
http://keaglez.e2mod.com/upload/sdk/...80i-SDK.tar.gz
5. games enviroment from Eug for easy sdl coding
MEGAUPLOAD - The leading online storage and file delivery service
6. Extract on Linux
It is done as su. (I would do it different but I will keep it simple.)
Code:
mkdir /opt/a1200
mkdir /opt/sdk
cd /
tar -C /opt -xzvf /a1200-crosstool.tar.gz
tar -C /usr/local -xzvf /games-env-linux.tar.gz
tar -C /opt/a1200 -xzvf /a1200-lib.tar.gz
tar -C /opt/sdk -xzvf /a1200-e2-e680i-SDK.tar.gz
cp -a /opt/sdk/a1200/* /opt/a1200
7. Set enviroment
Code:
source /usr/local/setenv-a1200.sh
8. Compiling (Eakrin)
http://www.motorolafans.com/forums/a...s-helloezx.zip
Goto /home/user
extract helloworld and change folder
this helloezx project contain 3 files. main.cpp, helloezx.h, and helloezx.cpp. first create a project file for helloezx by
Code:
progen -o helloezx.pro
create makefile for complier by command
Code:
tmake helloezx.pro -o Makefile
create helloezx 's binary file by
make the binary "smaller" (only after debug is done)
Code:
arm-linux-strip helloezx
testing your first app by copy helloezx file into your mmc and execute this commands via telnet.
Code:
. /home/native/.profile <-- this command start with dot and space too.
/mmc/mmca1/HelloEZX