Simulator != Emulator
We make a significant distinction in those two terms:
The simulator is a special Linux x86 build that runs all of Android in
a single process on a Linux workstation. It is extremely finicky and
prone to breaking. The only reason we keep it around is that it is
currently the only way to run Valgrind.
The emulator is an ARM instruction emulator that runs the same image
as you would run on a device (provided that the HAL is written to deal
with hardware dependencies that may not exist in the emulation
environment). To run code on the emulator, you choose the generic
build.
If you are trying to run code in a target environment (and if you are
hanging out in android-porting, you probably are), you want to choose
the generic build.
On Dec 9, 10:13 pm, getandroid <[EMAIL PROTECTED]> wrote:
> may be I've built the whole android by chosing generic and not sim
> (when prompted by lunch) as joe suggested. As I'm trying to run the
> executable on simulator, is it that i've to build for sim and not
> generic???
>
> On Dec 10, 10:34 am, getandroid <[EMAIL PROTECTED]> wrote:
>
> > I did those steps and built the whole android again, but still i get
> > the same problem:
>
> > ./pvplayer_engine_test
> > ./pvplayer_engine_test: 1: Syntax error: "(" unexpected
>
> > I dont get any errors while building. I use ubuntu machine for
> > building android and trying the test app on emulator.
>
> > # adb.exe push pvplayer_engine_test /data
> > # adb.exe shell
>
> > From data folder I try to execute ./pvplayer_engine_test and get the
> > above problem
>
> > On Dec 8, 9:23 pm, "Joe Onorato" <[EMAIL PROTECTED]> wrote:
>
> > > Hi. Which directory are you in when you type that command?
>
> > > The easiest way to make sure that everything builds is to run these
> > > commands
> > > from the directory that you ran repo init from.
>
> > > source build/envsetup.sh
> > > lunch
> > > (pick generic, not sim)
> > > make
>
> > > If your machine has multiple CPUs or a multicore CPU, you can do make -jN,
> > > where N is the number of cores times two. Before you do that, try rm -rf
> > > out from that directory to clean out any builds that might be
> > > inconsistent.
>
> > > You don't need to set the ARCH or CROSS_COMPILE variables if you use
> > > envsetup.sh and lunch.
>
> > > -joe
>
> > > On Mon, Dec 8, 2008 at 4:32 AM, getandroid <[EMAIL PROTECTED]> wrote:
>
> > > > I do
>
> > > > make ARCH=arm CROSS_COMPILE=arm-eabi-
>
> > > > then the whole android get compiled but none of the external packages
> > > > get built!!!
> > > > is there any way to compile whole android code at once???
>
> > > > secondly, i compiledopencoreand got the executable
> > > > 'pvplayer_engine_test'
>
> > > > was trying to run this in emulator but it seems that it doesnot have
> > > > execute permission
> > > > chmod 0777 <file> is not working(even after doing this the permission
> > > > dont change).
>
> > > > On Dec 8, 11:59 am, "Joe Onorato" <[EMAIL PROTECTED]> wrote:
> > > > > That's odd. Usually it does compileopencorewhen you build the rest of
> > > > > android. How are you doing the android build?
>
> > > > > -joe
>
> > > > > On Mon, Dec 8, 2008 at 1:56 AM, getandroid <[EMAIL PROTECTED]> wrote:
>
> > > > > > Hi,
>
> > > > > > I was trying to build 'opencore' from the android package, as it
> > > > > > doesnot get built when u compile the whole android source code. So,
> > > > > > I
> > > > > > assume one has to build it seperately.
>
> > > > > > Does anyone know how to compileopencorefor arm arch. bcoz when i
> > > > > > give ARCH=arm & CROSS_COMPILE=arm-eabi- it says no rule to make
> > > > > > target. ???
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
