This isn't a matter of the OHA all.  The current Android SDK does not
support applications with native code.  Period.  The only situation where
native code is currently supported is for things that are built in to the
system image of a device, because in that case the native code can be
rebuilt each time the system changes to match that system and not break.

On Sat, Jan 24, 2009 at 11:51 AM, kozak <[email protected]> wrote:

>
> Hi Dianne,
>
> Thanks for the input. I would like to know what kind of licensing as
> of now allows 3rd party to develop native apps. Is it that only
> members of OHA get to develop native apps "for now" and it would be
> open to the open source community sometime in the future?
>
> Tersely put, what should a one (individual/company) do to develop
> native apps?
>
> 1. Become an OHA member?
> 2. Any other alternative?
>
> Thanks in advance
> Kozak
>
>
>
> On Jan 23, 4:54 am, Dianne Hackborn <[email protected]> wrote:
> > On Fri, Dec 26, 2008 at 8:43 PM, venu <[email protected]> wrote:
> > > 1. Can I have anroid w/o the davlick vm, application framework, and
> APIS ?
> >
> > You can take Linux + whatever user space libraries you want, but I
> > personally I wouldn't call this "Android" any more.
> >
> > > 2. The motivation here is write custom applications on top libraries
> > > provided by anriod platform ? In others words, I want to strip of java
> > > virtual m/c, application framework and use anroid ?
> >
> > That isn't Android.  A lot of what makes Android what it is the Java
> code,
> > which implements everything from window management and application and
> > process management to the user-space view hierarchy and other client
> > frameworks.
> >
> > > 3. Does Anroid platform have a shell which comes up once we boot on
> > > the target can be used to run applications (strictly for debugging
> > > purposes) ?
> >
> > Use adb for this.
> >
> > > 4. Motivation here is to use either c++ or c language for development
> > > of applications....
> >
> > Android applications at this point must include some Java code to
> interact
> > with the rest of the system.  If (and only if) you are writing an app
> that
> > will be shipped on a device, you can use JNI for its Java code to call
> some
> > native code that implements significant parts of the app.  But eventually
> > there needs to be Java code to interact with the activity manager, window
> > manager, etc.
> >
> > And of course right now native code in third party apps is NOT supported,
> so
> > those have to be all Java.
> >
> > --
> > Dianne Hackborn
> > Android framework engineer
> > [email protected]
> >
> > Note: please don't send private questions to me, as I don't have time to
> > provide private support.  All such questions should be posted on public
> > forums, where I and others can see and answer them.
> >
>


-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to