This is very much a work in progress that is not ready to be used. But to answer some of your questions:
- there will be a feature added to the build system to build your add-on. It's just not there yet. - to add your library to the device system image, please read: http://groups.google.com/group/android-platform/browse_thread/thread/618971d3f7608f4c/c09b6000c94890cb Xav On Mon, Feb 9, 2009 at 1:56 PM, Josh Guilfoyle <[email protected]> wrote: > > I have noticed recent support coming into the master branch that seems > to support vendor add-ons to extend the public API. Is this support > something we can start using today, and if so, how? > > I'd like to introduce a few extra classes to a vendor-specific SDK API > and have supporting implementations running on the emulator but it's > unclear exactly how to connect these mechanics in the current master > branch. For instance, how do I get my vendor-specific jar files added > to the "add-ons" folder in the "make sdk" target? And, how would I > connect the source code into the existing build system such that the > implementation makes its way to the system.img? This is a long term > goal and does not necessarily need to be backward compatible to the > 1.0 or 1.1 SDK releases. > > > > -- Xavier Ducrohet Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
