Hi Rupesh, I have downloaded the android file system & uImage released by you from the following link.
http://embdroid.homeftp.net/ANDROID.tar.bz2 So i want to know Is this sufficient to see android running on this board ?? My doubt is when we build android on host system (Ubuntu Desktop ) we install some dependencies like "flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev" to build it & android also requires X11 to build itself. But on host it links everythng from the hosts (/usr/lib) So to see android running we also need X11 to be compiled with android toolchain & above mentioned dependecies plus X11 libs needs to a part of Android file system which is going to be mounted via nfs ?? So basically i want to know is the file system which u have published is enough to see android UI running on board ? If not then other then this basic filesystem what all dependencies we need to install as a part of the android root file system ?? Please dont mind of my queries as i am new to all this keernel & filesystem related stuff. Actually i want to port android on TI OMAP 3530 EVM & want to see the atleast UI, so i am not getting the clues :( Please please help me out. My personal id is [EMAIL PROTECTED] Thanks in advance Nimit Manglick On Thu, Nov 20, 2008 at 10:24 PM, Misael Lopez <[EMAIL PROTECTED]> wrote: > > Expanding comments... "mkimage" binary comes from u-boot compilation. > So first, compile u-boot and in <uboot_dir>/tools/ (not sure if this > is the exact path, but it's in tools dir) you will find this > "mkimage". Then just copy it to a directory you have exported in your > PATH. > > Misa > > 2008/11/20 Rupesh Gujare <[EMAIL PROTECTED]>: > > Nimit, > > > > Nimit Manglick wrote: > > > > <my_android_path>/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin > > > > But i am getting the following error :- > > > > "mkimage" command not found - U-Boot images will not be built > > > > and there is NO "uImage" formed in arch/arm/boot. But zImage formed. > > > > Error is self explanatory. > > You need "mkimage" command on your development machine, which is missing. > > > > Regards, > > > > -- > > Rupesh Gujare > > http://embinux.com > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
