2009/6/25 Streets Of Boston <[email protected]> > > Will the NDK be as actively maintained as the SDK? >
That's the goal; yes (both come from the same Android development tools team). Apart from that, the NDK is all about providing a binary contract between the platform and your binaries. In other words, anything built with the official 1.5 NDK shall be supported by any future release of the platform (for a given CPU), without any recompilation. This care for stability is also why we do not expose many system libraries through it (a lot of things on the native side of Android are in flux to improve performance / footprint and add features). > > In other words: > If i have an app (written using the SDK) using some so-library > (written with the NDK) and deployed with my app and some new phones > hit the market, would i always be able to re-compile my so-library > using the NDK (if necessary) so that my app would work on these new > phones? If the phone uses an official Android system image, this is the kind of thing guaranteed by the NDK. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
