Hi, In order to develop for Android, I suggest that you use Linux on your host system. If your normal environment is Windows, then using VMWare or VirtualBox to run the Linux part will be probably the easiest way to go. I suggest Ubuntu, because Google seems to use that, and most instructions assume that you use that distribution.
Then the toolchain: Android comes with a precompiled gcc 4.2.1 based toolchain, so you won't need RVCT for now. Then there are 2 parts of an Android system: the kernel and the userland. The userland (system.img and data.img) gets created when you type "make" in the root Android directory. To compile the kernel you need to use a kernel tree that contains the Android patches. Luckily, Google is maintaining a git repository specifically for MSM based devices, altough I think they are using MSM7200A in the G1. In any case I would start with that kernel tree. It contains an msm_defconfig configuration, which seems to include the options necessary for Android. Then the next part is the initial bringup. There are actually 2 ways to do it: 1. Your hardware has a big enough NAND flash, and your bootloader is able to flash yaffs2 images. Then you can just flash the kernel and the 2 image files to the device, and hope for the best. :) Since your HW is so similar to what Google is working with, I think you have a chance to actually pull this off. :) 2. Otherwise you can start experimenting with other filesystems / boot configurations. This will probably mean that you have to change the kernel configuration and the build process to build images you like. Also, if your bootloader supports booting over the network, you may use an NFS root system for development and initial bringup. This has the advantage, that you don't have to deal with flashing new images if you just need to change small things. Also, if your flash size is limited, it is nice to have a practically unlimited development filesystem for your device, where you can put debugging tools like strace, gdb ... etc. Having direct filesystem access to your device filesystem is also nice in some cases. Finally, it is also possible to use an already working Linux system on the device to bootstrap Android using chroot. We used this method extensively, while the Android sources were not yet available. You can mix this method with the NFS root method to provide maximum flexibility. :) However, you will still need to use a kernel that includes the Android patches. Also, if your device has not too much memory, running both a "normal" Linux userland and the Android userland together may not be feasible. Best Regards, Gergely On Mon, Nov 10, 2008 at 4:11 AM, andre <[EMAIL PROTECTED]> wrote: > > I got the android sources and built it. > And then I checked the built image is working on emulator. > > But, I can't do anything after then. > This is the first time to work on linux. > > My development environment: > - MSM7500A target > - cygwin + RVCT2.2 > - have qualcomm original build > > Do I must build android sources with qualcomm original build? > I've read few documents, but I cannot understand. > > > Sorry for silly question. > > > Thank you, > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
