Hi Martin, The purpose is to isolate Dalvik and its dependencies from rest of the Android stack. It is for those times when you have a look at the entire Android stack and have a thought like:
"Hmm. I would like to know only Dalvik code and its dependencies and am really not interested in the entire stack right now". The uses could be several. Some examples are: - Porting onto another CPU architecture - Using another toolchain for an existing architecture - Removing bionic dependency - Removing kernel android shared memory / binder dependency Avtar On Fri, Jan 8, 2010 at 3:58 AM, Martin Luessi <mlue...@gmail.com> wrote: > Hi, > > Can someone please clarify the exact purpose of this project, i.e., > the purpose of a standalone dalvik wm, to me. Will the standalone wm > only be able to run applications which do not depend on any external > android libraries (e.g. window manager, sqlite, media framework) or is > the goal to create a wm which enables android applications to run on > Linux (i.e the modified wm could use gstreamer instead of android's > OpenCore media framework etc). > > Martin > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting >
-- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
