thanks fadden and hackbod for your insight. I don't have my testing machine here so I cannot try your suggestion fadden (will do it on monday).
I know the simulator target is not the real thing, but anyway I'd like to experiment it and see what comes out. During the process I hope I will gain a deeper knowledge of the android system and its different components, even if most of them are hidden in the simulator version ... so, as long as I get errors like the one above I will try to overcome them. The error at this point seems to be much more basic than the lack of system components (can't even read the jar file), so one thing at a time. I understand the binder kernel driver will be necessary (probably the whole android kernel is recommended no?), but I didn't understand the main entry part of your explanation hackbod. Can you please elaborate a bit more or give a concrete example of what you mean. Thanks for your help, Filipe On 8 Nov, 05:01, hackbod <[EMAIL PROTECTED]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
