The tool level provided along with the 'gingerbread_release' tag is r7
(looking at the associated tags in the git tree and confirmed by
looking at the changes.txt in platform/android/sdk). However, on
developer.android.com it mentions that API level 10 requires tool
level r9 or greater, and
Hi there, we've got an addon that builds a custom library jar. I can
see that the javadocs with the correct package list are getting
generated in the output directory:
android/out/target/common/docs/mylibrary
However, it looks as though the javadocs are missing in the final
sdk.zip (open project
(other than the startup
flag) that I'm not aware of?
Thanks
T
On Feb 8, 1:35 pm, todd.lee todd@ca.flextronics.com wrote:
Hi there,
For our device emulator, we want to create larger default sizes for
the /system and /data partitions.
Of course we can do this with the -partition-size option
Hi there,
I've got some changes to the platform that I would like to document in
our internal development build of the Android SDK.
It looks to me as though I should be able to generate the 'api diff'
automatically using tools within the build but I seem to be missing
something...
My setup is
Ah - so just as a follow-up here, I discovered the the current.xml
file in frameworks/base/api is auto-generated via make update-api
So my configuration for framework_docs_LOCAL_DROIDDOC_OPTIONS was
wrong at:
-since ./frameworks/base/api/xx.xml xx \
which I gather should read:
-since
. make sdk makes
a generic SDK with all components which we extract and rezip only the
components we want: docs (content of docs/), samples (content of
samples/android-#), platform (content of platforms/android-#), etc...
Xav
On Fri, Dec 10, 2010 at 6:19 AM, todd.lee todd
I'm new to the group and just looking for some information on
publishing our own repository that the SDK manager can access.
We're looking to distribute the following:
- custom platform based stock android
- addon library
- images for custom emulator
- offline docs
- sample code
I've been able
