And um... I don't see how this is going to work. You can't just run an android application. You need to have the rest of the system going, and it needs to launch the process to have it run. More than that, you'd need to have at least the binder driver installed and running in your desktop kernel, since that is used for almost all of the IPCs between processes -- without, when you run the .apk, it will be unable to get any connection at all to anything else and not do anything. And even more, Android applications don't even have a "main" entrypoint, they publish a set of components that the system loads into their process and manages, so you would need to have that done as well.
The simulator is really not much of a bases for "running apps natively on the desktop." Yes, it compiles things to native code and runs those, but the environment is -really- different from the actual android system. When running as a simulator, EVERYTHING is in a single process (all system services, all applications, everything) and there is a little bit of code in places to spawn threads to kind-of emulate processes. So you could use the simulator as a way to get versions of things that are compiled for your desktop system, but there is significant work ahead of you to actually bring that up and running in some semblance of an android system. On Nov 7, 2:34 pm, fadden <[EMAIL PROTECTED]> wrote: > On Nov 7, 11:23 am, Filipe Abrantes <[EMAIL PROTECTED]> wrote: > > > [on root dir] > > cp Home.class development/samples/Home/src/com/example/android/home/ > > cd development/samples/Home/src > > ../../../../out/host/linux-x86/bin/dx --dex --output=Home.jar com/ > > example/android/home/Home.class > > > Then I run dalvik with: > > > ./run-dalvik -cp Home.jar Home > > Looks like the class name should be "com.example.android.home.Home", > not "Home". --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
