I believe my target is for ARM because I have successfully loaded the ROM onto my Nexus One.
On Feb 1, 8:18 am, Deva R <[email protected]> wrote: > Hi, > "generic" target means its built to be run on x86 emulator. > can you build for ARM target (so as it can be made run on Nexus One)?? > > > > On Mon, Jan 31, 2011 at 8:40 PM, Hank <[email protected]> wrote: > > My app is being installed into the generic product. How do I go about > > loading this generic system onto my Nexus One? > > > On Jan 29, 3:51 am, Deva R <[email protected]> wrote: > >> (just a thought) > >> if multiple level .mk 's are used, search in your setup if > >> PRODUCT_PACKAGES is later overridden by another "PRODUCT_PACKAGES:=" > >> make it to "PRODUCT_PACKAGES+=" > > >> On Sat, Jan 29, 2011 at 2:05 AM, freakingtux > > >> <[email protected]> wrote: > >> > Hi, > > >> > On Thursday, January 27, 2011 9:45:47 PM UTC+1, Hank wrote: > > >> >> I have been trying to make my application a pre-loaded application on > >> >> the Android OS Kernel. Within these two makefiles: generic.mk and > >> >> core.mk, I added my application to the list of pre-loaded applications > >> >> found under PRODUCT_PACKAGES:=, but when I load my custom kernel my > >> >> application is not installed. Is there something else I need to do? > > >> > I think it's better to add such packages to your device .mk files see > >> > PRODUCT_PACKAGES in > >> > device/htc/dream/device_dream.mk > > >> > Greetings > > >> > -- > >> > unsubscribe: [email protected] > >> > website:http://groups.google.com/group/android-porting > > >> -- > >> Regards, > >> Devawww.bittoggler.com > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-porting > > -- > Regards, > Devawww.bittoggler.com -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
