This is currently not supported by the official SDK.
There is however work being done to support this, both at the build
system level and in the developer tools (both Ant script and ADT)
In cupcake you will be able to build (and distribute) an SDK add-on
that will contain:
- new system image to run the emulator with your custom version of
Android, including your new library(ies)
- a jar file for developers to link against when using your new APIs (if any).
- custom emulator skins.
Developers will be able to choose what they wish to target (ie
standard Android platform, or add-on with optional APIs).
While some of this work is already in cupcake (if you do make SDK you
will see the SDK folder structure has changed and now contains
platforms/ and add-ons/ folders), it's unfortunately not ready.
I'll will post in here when you can start using it.
On Tue, Jan 6, 2009 at 6:51 PM, Nick <nick...@gmail.com> wrote:
Ok so if developing applications in native code is not currently
supported for 3rd party developers, could Google give an indication
(including whatever disclaimers about timeframes, non committalls
etc.) about if and possibly when this could be available?
An understandable technical explanation of why its not possible would
be greatly appreciated by many users of these boards. I saw one thread
which basically seemed to be saying the reason was for binary
compataibility reasons. I didn't understand how that is applicable to
my app developed only by me for me.
I had a look into the sample PlatformLibrary code, its make file and Readme.txt.
The library implements few methods which do a specific work.
I want to add a platform library of my own which is supposed to
implement one content provider, one service and a broadcast receiver.
Is it possible to do this in cupcake? How can I inform Android
platform that it should start my provider and service on device bootup
and broadcast receiver is registered with the platform.
Readme.txt says the JAR is not associated with any AndroidManifest.xml
file. But, provider, service and broadcast receiver are supposed to be
specified in AndroidManifest.xml of the application if they are built
into application code.
It really sounds like you're just looking to add an application,
though, not a (linkable) library.
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
Now we are looking at moving it inside a static library. Static
library need to contain service, provider and broadcast receiver.
Could we specify service, provider and receiver in application
manifest file which are actually part of static library and link it
with apk and how?