Further clarification: <<< I was under the impression it is possible to download the java source code AND the C source code and build them all. >>>
It is possible to download the open source code and build for the emulator. If you want the code to run on a specific device, you need additional libraries that are not necessarily available in open source. These libraries are provided by the manufacturer and/or third party vendors and contain hardware specific code. <<< If its not possible does it just mean its not possible for 3rd party developers to do but it is possible for device manufacturers to do? >>> Manufacturers do write native code to adapt Android to their hardware in order to create these device specific libraries. This code is usually exposed through a hardware abstraction layer that hides the eccentricities of the device from the application developer. We do intend to support native code development in the future. We just want to take time to refine the native API's before we make them public. There is nothing more painful than changing an API because you overlooked something and then having to support the legacy API for years to come. On Feb 5, 10:57 am, Jean-Baptiste Queru <j...@android.com> wrote: > it is possible to make it work for a given device running a given > revision of the software. It is not currently possible to make it work > in a way that behaves predictably on different devices or different > revisions of the software (including, importantly, devices or software > revisions that haven't been released yet). > > That's why it's "not supported": if you make it work on your device > right now and it doesn't work in another environment, you shouldn't > expect to receive any help or to see any effort spent at the framework > level to try to make your application work in the future. The same is > true of undocumented classes, functions, or parameter values. > > JBQ > > > > On Wed, Feb 4, 2009 at 11:28 AM, fructose <david_prest...@hotmail.com> wrote: > > > I keep seeing this quote everywhere whenever anybody asks a question > > about about C code. > > > However I don't understand it, nor another quote which is used to > > futher explain it "The SDK does not include support for native ARM > > code". > > > I was under the impression it is possible to download the java source > > code AND the C source code and build them all. > > > Is this therefore incorrect, you cannot build the existing C code for > > a target platform and therefore make changes to it? > > > I want to know if it is possible to write some C code in, for example, > > the Library layer, and then write some Java code in the Apllication/ > > Application framework that accesses that C code via JNI. > > > If this is not possible will it be possible in the future, and if so > > at what point? > > > If its not possible does it just mean its not possible for 3rd party > > developers to do but it is possible for device manufacturers to do? > > Otherwise I don't understand how a device manufacturer can create a > > device containing proprietary functionality if there is no ability to > > write and access C code. Is Android forcing manufacturers to write > > *everything* in Java? > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
