HOWTO Build Android-X86 Full Source
====================================
Last Modified on 23-Dec-2008 23:10
I Summarized how to build android full source for x86 target.
0. My development environments
- OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
- CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
R60 Laptop )
- RAM: Samsung DDR Ram
- Target: Eee PC (ASUS)
1. Query of Linux distribution information
- At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
And then, confirm system information on your linux distribution
like belows.
$ uname -a
Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
2008 i686 GNU/Linux
$ gcc --version
gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
2. repo init and Sync
- You have to download android full source for x86 architecture like
ASUS Eee PC 701.
- Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
asus/eee_701.git".
$ cd ~
$ mkdir bin_x86 && cd bin_x86
$ mkdir mydroid && cd mydroid
$ repo init -u git://android.git.kernel.org/platform/manifest.git -b
cupcake
$ repo sync
$ vi ./.repo/local_manifest.xml
<manifest>
<project name="platform/vendor/asus/eee_701" path="vendor/asus/
eee_701"/>
</manifest>
$ repo sync
... A new repo command ( 1.8) is available.
... You should upgrade soon:
$ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
vector-fst.h
$ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
$ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
#include <string.h>
and so on......
Got my hands on a eee701 today, will try this as soon as I get home
and install Ubuntu!
Yesterday I tried to compile in Slack12, perhaps later I will post the
compile barf.
> HOWTO Build Android-X86 Full Source
> ====================================
> Last Modified on 23-Dec-2008 23:10
> I Summarized how to build android full source for x86 target.
> 0. My development environments
> - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> R60 Laptop )
> - RAM: Samsung DDR Ram
> - Target: Eee PC (ASUS)
> 1. Query of Linux distribution information
> - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> And then, confirm system information on your linux distribution
> like belows.
> $ uname -a
> Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> 2008 i686 GNU/Linux
> $ gcc --version
> gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 2. repo init and Sync
> - You have to download android full source for x86 architecture like
> ASUS Eee PC 701.
> - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> asus/eee_701.git".
> $ cd ~
> $ mkdir bin_x86 && cd bin_x86
> $ mkdir mydroid && cd mydroid
> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> cupcake
> $ repo sync
> $ vi ./.repo/local_manifest.xml
> <manifest>
> <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> eee_701"/>
> </manifest>
> $ repo sync
> ... A new repo command ( 1.8) is available.
> ... You should upgrade soon:
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
> vector-fst.h
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
> $ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
> #include <string.h>
> and so on......
Using gcc-4.2 instead of gcc-4.3 should help avoid modifying source,
that is
$ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
CC=gcc-4.2 CXX=g++-4.2 make ........
On Dec 23, 11:11 pm, "Lim,GeunSik" <lee...@gmail.com> wrote:
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
> vector-fst.h
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
> $ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
> #include <string.h>
> and so on......
> Using gcc-4.2 instead of gcc-4.3 should help avoid modifying source,
> that is
> $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
> CC=gcc-4.2 CXX=g++-4.2 make ........
> On Dec 23, 11:11 pm, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > 3. Building x86 android full source
> > $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -
> > j2 installer_img
i have done all this and i have the .img files but i am not able to
create a working live usb. The grub loader seems to be going into some
kind of loop. How do i get past that ? any ideas?
Gowtham
On Dec 23, 10:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> HOWTO Build Android-X86 Full Source
> ====================================
> Last Modified on 23-Dec-2008 23:10
> I Summarized how to build android full source for x86 target.
> 0. My development environments
> - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> R60 Laptop )
> - RAM: Samsung DDR Ram
> - Target: Eee PC (ASUS)
> 1. Query of Linux distribution information
> - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> And then, confirm system information on your linux distribution
> like belows.
> $ uname -a
> Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> 2008 i686 GNU/Linux
> $ gcc --version
> gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 2. repo init and Sync
> - You have to download android full source for x86 architecture like
> ASUS Eee PC 701.
> - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> asus/eee_701.git".
> $ cd ~
> $ mkdir bin_x86 && cd bin_x86
> $ mkdir mydroid && cd mydroid
> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> cupcake
> $ repo sync
> $ vi ./.repo/local_manifest.xml
> <manifest>
> <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> eee_701"/>
> </manifest>
> $ repo sync
> ... A new repo command ( 1.8) is available.
> ... You should upgrade soon:
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
> vector-fst.h
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
> $ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
> #include <string.h>
> and so on......
i have done all this and i have the .img files but i am not able to
create a working live usb. The grub loader seems to be going into some
kind of loop. How do i get past that ? any ideas?
Gowtham
On Dec 23, 10:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> HOWTO Build Android-X86 Full Source
> ====================================
> Last Modified on 23-Dec-2008 23:10
> I Summarized how to build android full source for x86 target.
> 0. My development environments
> - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> R60 Laptop )
> - RAM: Samsung DDR Ram
> - Target: Eee PC (ASUS)
> 1. Query of Linux distribution information
> - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> And then, confirm system information on your linux distribution
> like belows.
> $ uname -a
> Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> 2008 i686 GNU/Linux
> $ gcc --version
> gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 2. repo init and Sync
> - You have to download android full source for x86 architecture like
> ASUS Eee PC 701.
> - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> asus/eee_701.git".
> $ cd ~
> $ mkdir bin_x86 && cd bin_x86
> $ mkdir mydroid && cd mydroid
> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> cupcake
> $ repo sync
> $ vi ./.repo/local_manifest.xml
> <manifest>
> <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> eee_701"/>
> </manifest>
> $ repo sync
> ... A new repo command ( 1.8) is available.
> ... You should upgrade soon:
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
> vector-fst.h
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
> $ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
> #include <string.h>
> and so on......
-----Original Message-----
From: android-porting@googlegroups.com 代表 rams
Sent: 2008-12-25 (星期四) 21:45
To: android-porting@googlegroups.com
Subject: [android-porting] Re: Howto build Android full source for X86 Architecture like EeePC(ASUS)
Hi All,
Will these steps work for a Desktop PC
<Intel Dual Core, Ubuntu 8.10>
without affecting anything in my harddisk?
Please help.
Thanks
Ram.
On Thu, Dec 25, 2008 at 10:12 AM, Rich <miser...@gmail.com> wrote:
> Seriously.. video, please? I'm really interested in how good this
> looks.
Ok, after some work I get installer.img from android sources.
I'm trying to use it on 1) QEMU x86 version 2) a generic x86 PC (not
Asus eee).
In the first case linux kernel loads, but the installer stops trying
to lauch init script
(I guess there are some scripts to modify to permit android to work
properly on
an emulated environment). In particular, I obtain something like
init: Unable to open persistent property directory /data/property
errno:2
installer : waiting for device: /dev/block/sdb2
The secondo case in more interesting. I've used make-live script to
copy installer.img
on an USB hard drive. Android kernel and init scripts start without
problems.
The problem is that after the first loading I obtain a "black screen",
but with ALT+F1
I can use the sh prompt. I think that the black screen appears because
I haven't an
Intel 915 video card on the pc...but I'm not really sure.
Any tips or suggestion?
On 25 Dic, 15:55, "gowtham gowda" <gowth...@gmail.com> wrote:
for the first case, most likely your USB hard drive is not /dev/block/
sdb, to use it to install Android on your system, kill the /system/bin/
installer process and run '/system/bin/installer -p /dev/block/
WHAT_YOUR_HARDDRIVE_IS2' (e.g., my USB stick is sdd, I use /dev/block/
sdd2)
for the second case, I think what you guessed is right. To be sure of
it, if you got ethernet, 'adb logcat' could help you. To build
required modules, you may wanna read 'vendor/asus/eee_701/modules/
module.versions', check out android-2.6.25 kernel, and start from
'vendor/asus/eee_701/kernel.config'.
On Dec 26, 8:58 pm, Stargatto <carl.ro...@virgilio.it> wrote:
> Ok, after some work I get installer.img from android sources.
> I'm trying to use it on 1) QEMU x86 version 2) a generic x86 PC (not
> Asus eee).
> In the first case linux kernel loads, but the installer stops trying
> to lauch init script
> (I guess there are some scripts to modify to permit android to work
> properly on
> an emulated environment). In particular, I obtain something like
> init: Unable to open persistent property directory /data/property
> errno:2
> installer : waiting for device: /dev/block/sdb2
> The secondo case in more interesting. I've used make-live script to
> copy installer.img
> on an USB hard drive. Android kernel and init scripts start without
> problems.
> The problem is that after the first loading I obtain a "black screen",
> but with ALT+F1
> I can use the sh prompt. I think that the black screen appears because
> I haven't an
> Intel 915 video card on the pc...but I'm not really sure.
> Any tips or suggestion?
> On 25 Dic, 15:55, "gowtham gowda" <gowth...@gmail.com> wrote:
1) Android SDK & Sources : What we get from google
contains a built Emulator along with ramdisk, data & system imgs.
It is an ARM Emulator (QEMU) which emulates a ARM processor architecture.
2) Android Sources : When we get android sources, run . ./envsetup.sh
& lunch 1, It gives the Emulated ARM Environment (QEMU).
3) A generic x86 PC: This is the build which will make Android to work
on X86 architectures like Asus ePC, Normal Desktop etc. We have the
live script to make it and run.
4) QEMU x86 version: Is this the QEMU emulated environment of Android
running on X86? What are the steps to make it work? choosecombo steps?
On Fri, Dec 26, 2008 at 9:59 PM, freedom <koansin....@gmail.com> wrote:
> for the first case, most likely your USB hard drive is not /dev/block/
> sdb, to use it to install Android on your system, kill the /system/bin/
> installer process and run '/system/bin/installer -p /dev/block/
> WHAT_YOUR_HARDDRIVE_IS2' (e.g., my USB stick is sdd, I use /dev/block/
> sdd2)
> for the second case, I think what you guessed is right. To be sure of
> it, if you got ethernet, 'adb logcat' could help you. To build
> required modules, you may wanna read 'vendor/asus/eee_701/modules/
> module.versions', check out android-2.6.25 kernel, and start from
> 'vendor/asus/eee_701/kernel.config'.
> On Dec 26, 8:58 pm, Stargatto <carl.ro...@virgilio.it> wrote:
> > Ok, after some work I get installer.img from android sources.
> > I'm trying to use it on 1) QEMU x86 version 2) a generic x86 PC (not
> > Asus eee).
> > In the first case linux kernel loads, but the installer stops trying
> > to lauch init script
> > (I guess there are some scripts to modify to permit android to work
> > properly on
> > an emulated environment). In particular, I obtain something like
> > init: Unable to open persistent property directory /data/property
> > errno:2
> > installer : waiting for device: /dev/block/sdb2
> > The secondo case in more interesting. I've used make-live script to
> > copy installer.img
> > on an USB hard drive. Android kernel and init scripts start without
> > problems.
> > The problem is that after the first loading I obtain a "black screen",
> > but with ALT+F1
> > I can use the sh prompt. I think that the black screen appears because
> > I haven't an
> > Intel 915 video card on the pc...but I'm not really sure.
> > Any tips or suggestion?
> > On 25 Dic, 15:55, "gowtham gowda" <gowth...@gmail.com> wrote:
For use on qemu or generic PC, you may need to compile the kernel with VESA
Frame buffer support and specify the VESA mode when boot: vga=788 (800x600,
that may be a good resolution, 785 for 640x480, 791 for 1024x768). You can
add it in grub's menu.lst
For disk file with qemu, it may be possible to use dd image of the
make-live script created usb disk. I haven't tried yet, but it may be
possible.
--
Chen
On Fri, Dec 26, 2008 at 8:58 PM, Stargatto <carl.ro...@virgilio.it> wrote:
> Ok, after some work I get installer.img from android sources.
> I'm trying to use it on 1) QEMU x86 version 2) a generic x86 PC (not
> Asus eee).
> In the first case linux kernel loads, but the installer stops trying
> to lauch init script
> (I guess there are some scripts to modify to permit android to work
> properly on
> an emulated environment). In particular, I obtain something like
> init: Unable to open persistent property directory /data/property
> errno:2
> installer : waiting for device: /dev/block/sdb2
> The secondo case in more interesting. I've used make-live script to
> copy installer.img
> on an USB hard drive. Android kernel and init scripts start without
> problems.
> The problem is that after the first loading I obtain a "black screen",
> but with ALT+F1
> I can use the sh prompt. I think that the black screen appears because
> I haven't an
> Intel 915 video card on the pc...but I'm not really sure.
I run logcat and the same happens with some other keys.
2) If I try to activate WiFi, the UI says "Unable to start WI-FI" and the logcat shows the error:
E/WifiService( 1935): Failed to load Wi-Fi driver.
3) I read in other posts that Android doesn't support a mouse pointer but the mouse events should be handled nevertheless. Is that so? Because I tried and there are neither responses to mouse events in the UI nor the logcat.
Finally, where can I find info on how to troubleshoot a running system (I only know the logcat so far)?
Thanks Lee for the detailed instructions. Do you know if this build
works in Virtual Environment(like VMWare or VirtualBox?).
What changes do I need to make if I need to run this in virtual
environment?
Also, Do you know if the vanilla cupcake branch will work for the
virtual environment? Or do I need to pull in the Asus tree?
Thanks
On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> HOWTO Build Android-X86 Full Source
> ====================================
> Last Modified on 23-Dec-2008 23:10
> I Summarized how to build android full source for x86 target.
> 0. My development environments
> - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> R60 Laptop )
> - RAM: Samsung DDR Ram
> - Target: Eee PC (ASUS)
> 1. Query of Linux distribution information
> - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> And then, confirm system information on your linux distribution
> like belows.
> $ uname -a
> Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> 2008 i686 GNU/Linux
> $ gcc --version
> gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 2. repo init and Sync
> - You have to download android full source for x86 architecture like
> ASUS Eee PC 701.
> - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> asus/eee_701.git".
> $ cd ~
> $ mkdir bin_x86 && cd bin_x86
> $ mkdir mydroid && cd mydroid
> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> cupcake
> $ repo sync
> $ vi ./.repo/local_manifest.xml
> <manifest>
> <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> eee_701"/>
> </manifest>
> $ repo sync
> ... A new repo command ( 1.8) is available.
> ... You should upgrade soon:
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
> vector-fst.h
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
> $ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
> #include <string.h>
> and so on......
> 1) Android SDK & Sources : What we get from google
> contains a built Emulator along with ramdisk, data & system imgs.
> It is an ARM Emulator (QEMU) which emulates a ARM processor architecture.
Yes.
> 2) Android Sources : When we get android sources, run . ./envsetup.sh
> & lunch 1, It gives the Emulated ARM Environment (QEMU).
(I dont remember which lunch selection it is but,) yes the qemu from the
android tree only supports ARM tergets at this point.
> 3) A generic x86 PC: This is the build which will make Android to work
> on X86 architectures like Asus ePC, Normal Desktop etc. We have the
> live script to make it and run.
There is no support for generic PCs, but it should be possible to create a
more generic x86 target without a kernel, no installer, but just a basic
ramdisk and system image.
There is some basic support for EeePC 701, though others have had success
running it on other similar hardware (building your own kernel might be
necessary). Common issue is the lack of correct framebuffer drivers. As
someone suggested on this thread, try building the kernel with vesafb to
make it easier for bringup.
> 4) QEMU x86 version: Is this the QEMU emulated environment of Android
> running on X86? What are the steps to make it work? choosecombo steps?
QEMU provided runs ON x86, but only runs ARM target code.
> On Fri, Dec 26, 2008 at 9:59 PM, freedom <koansin....@gmail.com> wrote:
>> for the first case, most likely your USB hard drive is not /dev/block/
>> sdb, to use it to install Android on your system, kill the /system/bin/
>> installer process and run '/system/bin/installer -p /dev/block/
>> WHAT_YOUR_HARDDRIVE_IS2' (e.g., my USB stick is sdd, I use /dev/block/
>> sdd2)
>> for the second case, I think what you guessed is right. To be sure of
>> it, if you got ethernet, 'adb logcat' could help you. To build
>> required modules, you may wanna read 'vendor/asus/eee_701/modules/
>> module.versions', check out android-2.6.25 kernel, and start from
>> 'vendor/asus/eee_701/kernel.config'.
>> On Dec 26, 8:58 pm, Stargatto <carl.ro...@virgilio.it> wrote:
>> > Ok, after some work I get installer.img from android sources.
>> > I'm trying to use it on 1) QEMU x86 version 2) a generic x86 PC (not
>> > Asus eee).
>> > In the first case linux kernel loads, but the installer stops trying
>> > to lauch init script
>> > (I guess there are some scripts to modify to permit android to work
>> > properly on
>> > an emulated environment). In particular, I obtain something like
>> > init: Unable to open persistent property directory /data/property
>> > errno:2
>> > installer : waiting for device: /dev/block/sdb2
>> > The secondo case in more interesting. I've used make-live script to
>> > copy installer.img
>> > on an USB hard drive. Android kernel and init scripts start without
>> > problems.
>> > The problem is that after the first loading I obtain a "black screen",
>> > but with ALT+F1
>> > I can use the sh prompt. I think that the black screen appears because
>> > I haven't an
>> > Intel 915 video card on the pc...but I'm not really sure.
>> > Any tips or suggestion?
>> > On 25 Dic, 15:55, "gowtham gowda" <gowth...@gmail.com> wrote:
I have managed to run it under both Vmware and Virtualbox. You need to
compile the kernel with proper driver: vesafb, ethernet, scsci or ide, etc.
You may be able to use the dd image of the make-live created usb key.
--
Chen
On Sat, Dec 27, 2008 at 2:58 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> Thanks Lee for the detailed instructions. Do you know if this build
> works in Virtual Environment(like VMWare or VirtualBox?).
> What changes do I need to make if I need to run this in virtual
> environment?
> Also, Do you know if the vanilla cupcake branch will work for the
> virtual environment? Or do I need to pull in the Asus tree?
> Thanks
> On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > HOWTO Build Android-X86 Full Source
> > ====================================
> > Last Modified on 23-Dec-2008 23:10
> > I Summarized how to build android full source for x86 target.
> > 0. My development environments
> > - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> > - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> > R60 Laptop )
> > - RAM: Samsung DDR Ram
> > - Target: Eee PC (ASUS)
> > 1. Query of Linux distribution information
> > - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> > And then, confirm system information on your linux distribution
> > like belows.
> > $ uname -a
> > Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> > 2008 i686 GNU/Linux
> > $ gcc --version
> > gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> > Copyright (C) 2008 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions. There
> > is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> > 2. repo init and Sync
> > - You have to download android full source for x86 architecture like
> > ASUS Eee PC 701.
> > - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> > asus/eee_701.git".
> > $ cd ~
> > $ mkdir bin_x86 && cd bin_x86
> > $ mkdir mydroid && cd mydroid
> > $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> > cupcake
> > $ repo sync
> > $ vi ./.repo/local_manifest.xml
> > <manifest>
> > <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> > eee_701"/>
> > </manifest>
> > $ repo sync
> > ... A new repo command ( 1.8) is available.
> > ... You should upgrade soon:
> I have managed to run it under both Vmware and Virtualbox. You need to
> compile the kernel with proper driver: vesafb, ethernet, scsci or ide, etc.
> You may be able to use the dd image of the make-live created usb key.
> --
> Chen
> On Sat, Dec 27, 2008 at 2:58 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> > Thanks Lee for the detailed instructions. Do you know if this build
> > works in Virtual Environment(like VMWare or VirtualBox?).
> > What changes do I need to make if I need to run this in virtual
> > environment?
> > Also, Do you know if the vanilla cupcake branch will work for the
> > virtual environment? Or do I need to pull in the Asus tree?
> > Thanks
> > On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > > HOWTO Build Android-X86 Full Source
> > > ====================================
> > > Last Modified on 23-Dec-2008 23:10
> > > I Summarized how to build android full source for x86 target.
> > > 0. My development environments
> > > - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> > > - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> > > R60 Laptop )
> > > - RAM: Samsung DDR Ram
> > > - Target: Eee PC (ASUS)
> > > 1. Query of Linux distribution information
> > > - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> > > And then, confirm system information on your linux distribution
> > > like belows.
> > > $ uname -a
> > > Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> > > 2008 i686 GNU/Linux
> > > $ gcc --version
> > > gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> > > Copyright (C) 2008 Free Software Foundation, Inc.
> > > This is free software; see the source for copying conditions. There
> > > is NO
> > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > > PURPOSE.
> > > 2. repo init and Sync
> > > - You have to download android full source for x86 architecture like
> > > ASUS Eee PC 701.
> > > - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> > > asus/eee_701.git".
> > > $ cd ~
> > > $ mkdir bin_x86 && cd bin_x86
> > > $ mkdir mydroid && cd mydroid
> > > $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> > > cupcake
> > > $ repo sync
> > > $ vi ./.repo/local_manifest.xml
> > > <manifest>
> > > <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> > > eee_701"/>
> > > </manifest>
> > > $ repo sync
> > > ... A new repo command ( 1.8) is available.
> > > ... You should upgrade soon:
Could you drop the vmware file at some place? I'm willing to share it
on my fast internet connection. Would be very nice to have a look at
Android running on X86 hardware!
On Dec 27, 2:43 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> I have managed to run it under both Vmware and Virtualbox. You need to
> compile the kernel with proper driver: vesafb, ethernet, scsci or ide, etc.
> You may be able to use the dd image of the make-live created usb key.
> --
> Chen
> On Sat, Dec 27, 2008 at 2:58 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> > Thanks Lee for the detailed instructions. Do you know if this build
> > works in Virtual Environment(like VMWare or VirtualBox?).
> > What changes do I need to make if I need to run this in virtual
> > environment?
> > Also, Do you know if the vanilla cupcake branch will work for the
> > virtual environment? Or do I need to pull in the Asus tree?
> > Thanks
> > On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > > HOWTO Build Android-X86 Full Source
> > > ====================================
> > > Last Modified on 23-Dec-2008 23:10
> > > I Summarized how to build android full source for x86 target.
> > > 0. My development environments
> > > - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> > > - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> > > R60 Laptop )
> > > - RAM: Samsung DDR Ram
> > > - Target: Eee PC (ASUS)
> > > 1. Query of Linux distribution information
> > > - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> > > And then, confirm system information on your linux distribution
> > > like belows.
> > > $ uname -a
> > > Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> > > 2008 i686 GNU/Linux
> > > $ gcc --version
> > > gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> > > Copyright (C) 2008 Free Software Foundation, Inc.
> > > This is free software; see the source for copying conditions. There
> > > is NO
> > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > > PURPOSE.
> > > 2. repo init and Sync
> > > - You have to download android full source for x86 architecture like
> > > ASUS Eee PC 701.
> > > - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> > > asus/eee_701.git".
> > > $ cd ~
> > > $ mkdir bin_x86 && cd bin_x86
> > > $ mkdir mydroid && cd mydroid
> > > $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> > > cupcake
> > > $ repo sync
> > > $ vi ./.repo/local_manifest.xml
> > > <manifest>
> > > <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> > > eee_701"/>
> > > </manifest>
> > > $ repo sync
> > > ... A new repo command ( 1.8) is available.
> > > ... You should upgrade soon:
> Hi Chen, could u pls list the steps to do this(i.e. running the image
> in virtualbox)?
> thanks
> Sri
> On Dec 26, 5:43 pm, "Chen Yang" <sunsety...@gmail.com> wrote:
> > I have managed to run it under both Vmware and Virtualbox. You need to
> > compile the kernel with proper driver: vesafb, ethernet, scsci or ide, etc.
> > You may be able to use the dd image of the make-live created usb key.
> > --
> > Chen
> > On Sat, Dec 27, 2008 at 2:58 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> > > Thanks Lee for the detailed instructions. Do you know if this build
> > > works in Virtual Environment(like VMWare or VirtualBox?).
> > > What changes do I need to make if I need to run this in virtual
> > > environment?
> > > Also, Do you know if the vanilla cupcake branch will work for the
> > > virtual environment? Or do I need to pull in the Asus tree?
> > > Thanks
> > > On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > > > HOWTO Build Android-X86 Full Source
> > > > ====================================
> > > > Last Modified on 23-Dec-2008 23:10
> > > > I Summarized how to build android full source for x86 target.
> > > > 0. My development environments
> > > > - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> > > > - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> > > > R60 Laptop )
> > > > - RAM: Samsung DDR Ram
> > > > - Target: Eee PC (ASUS)
> > > > 1. Query of Linux distribution information
> > > > - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> > > > And then, confirm system information on your linux distribution
> > > > like belows.
> > > > $ uname -a
> > > > Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> > > > 2008 i686 GNU/Linux
> > > > $ gcc --version
> > > > gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> > > > Copyright (C) 2008 Free Software Foundation, Inc.
> > > > This is free software; see the source for copying conditions. There
> > > > is NO
> > > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > > > PURPOSE.
> > > > 2. repo init and Sync
> > > > - You have to download android full source for x86 architecture like
> > > > ASUS Eee PC 701.
> > > > - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> > > > asus/eee_701.git".
> > > > $ cd ~
> > > > $ mkdir bin_x86 && cd bin_x86
> > > > $ mkdir mydroid && cd mydroid
> > > > $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> > > > cupcake
> > > > $ repo sync
> > > > $ vi ./.repo/local_manifest.xml
> > > > <manifest>
> > > > <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> > > > eee_701"/>
> > > > </manifest>
> > > > $ repo sync
> > > > ... A new repo command ( 1.8) is available.
> > > > ... You should upgrade soon:
|
