This patch depends on https://review.source.android.com/24052
It is used to ensure that the proper kernel image is copied to the
platform image's kernel-qemu.
This is needed because for ARMv7 platform builds, the image is
in prebuilt/android-arm/kernel/kernel-qemu-armv7, instead of
prebuilt/android-arm/kernel/kernel-qemu
Change-Id: I0f175a1ba3d97f5c7420597bdeebc7a353551194
The output of the platform tree build is llvm-rs-cc-2 and should
be used for apps targeting 12+. This is encoded in llvm-rs-cc.txt
The older (HC) version of llvm-rs-cc is copied from the prebuilt
and is used for apps targeting 11+.
Until new tools that can read/process llvm-rs-cc.txt are released,
old tools will use the HC version of llvm-rs-cc which ensure
proper compatibility.
Change-Id: Iddb924409cc9238531bf1a0448b14b7eac3396a5
This patch ensures that we copy the generated build.prop file to
the platform image directory. This file will later be used by the
emulator and other tools to determine various properties of the
image without having to parse the system.img file.
For example, this can be used to extract the target CPU architecture
and/or ABI, and automatically adjust emulation based on this.
Change-Id: Ia5b67c6fb93078b6b224b10e3322af88b99c50b9
This sample illustrates how to write an application that plays media
in the background, handles streaming media from the network and
reacts appropriately to system events like headphone disconnection and
audio focus changes, and also uses the notification system to
keep the user informed about what is happening.
This CL is a cherrypick of the old CL 104495 (originally in
honeycomb-mr1) into honeycomb-mr2. Original CL:
https://android-git.corp.google.com/g/#change,104495
Change-Id: Ib8b15ee920300adc093a8b52c17bd9c251ac74ca
Also remove ApiDemos from the package and instead
add each library-specific sample app to each v##
folder.
Change-Id: I2932bbb91c7122c122973902d1fcd159ca899381
The app demostrates the how to use voicemail provider APIs to insert new
voicemail records using a simple UI.
Change-Id: I22610e06a8b80518b9f0d811f72afe245a4148c6
This is sample code that controls a USB missle launcher using USB host APIs
Change-Id: Ic4201faccc4562bf114c70d50b0cab6a00d28a98
Signed-off-by: Mike Lockwood <lockwood@android.com>
When the "sdk_repo" modified is used during the SDK build,
this also generates the repository.xml and addon.xml files
for the new SDK repository packages and places them in
the DIST_DIR.
Example usage:
make -j 16 PRODUCT-sdk-sdk showcommands sdk_repo dist DIST_DIR=/dist/sdk
make -j 16 PRODUCT-google_sdk-sdk_addon showcommands sdk_repo dist DIST_DIR=/dist/addon
Also merges 3ea87ca65f
'Fix XMLNS detection in SDK Repo XSD files.'
to prevent a merge conflict later on.
Change-Id: Ib14fe820dab7a60bb5412968c146c30ec5ba81c7
When the "sdk_repo" modified is used during the SDK build,
this also generates the repository.xml and addon.xml files
for the new SDK repository packages and places them in
the DIST_DIR.
Example usage:
make -j 16 PRODUCT-sdk-sdk showcommands sdk_repo dist DIST_DIR=/dist/sdk
make -j 16 PRODUCT-google_sdk-sdk_addon showcommands sdk_repo dist DIST_DIR=/dist/addon
Also merges 3ea87ca65f
'Fix XMLNS detection in SDK Repo XSD files.'
to prevent a merge conflict later on.
Change-Id: Ic9832e71456d76f849406e641792f4285ffbf649
When the build is invoked with the fake target "sdk_repo" and
a main target of sdk, win_sdk or sdk_addon, we now create
packages in DIST_DIR that can directly be used to populate the
SDK Repository.
This is quite close to how we actually distribute the SDK.
Change-Id: I671e8ff1bc2a6e9f5c097241d65da1cfdde21154
When the "sdk_repo" modified is used during the SDK build,
this also generates the repository.xml and addon.xml files
for the new SDK repository packages and places them in
the DIST_DIR.
Example usage:
make -j 16 PRODUCT-sdk-sdk showcommands sdk_repo dist DIST_DIR=/dist/sdk
make -j 16 PRODUCT-google_sdk-sdk_addon showcommands sdk_repo dist DIST_DIR=/dist/addon
Change-Id: I4f60d3197cac8c22027534cb7686de087ddf1a90
When the build is invoked with the fake target "sdk_repo" and
a main target of sdk, win_sdk or sdk_addon, we now create
packages in DIST_DIR that can directly be used to populate the
SDK Repository.
This is quite close to how we actually distribute the SDK.
Change-Id: I1c4a120616697383792d7fb1b328cfcefac0b2f5
