aboutsummaryrefslogtreecommitdiffstats
path: root/sdkmanager/libs/sdklib/tests/Android.mk
Commit message (Collapse)AuthorAgeFilesLines
* Added parser for new devices schemaMichael Wright2012-06-131-1/+1
| | | | Change-Id: Ib8a4a750b56f9ea94abd21c445958726343e760c
* Add missing notice files.Xavier Ducrohet2011-03-151-3/+2
| | | | | | | | | | Also fix some makefiles to make sure the notices are picked up. - move the makefile outside of the source folder. - resources are now in the source folder directly instead of being inside src/resources. It's much simpler. Change-Id: Ica8ee4c2bc8a9b035d23fc914d4137cdca7e567d
* AVD and ADT eclipse plugin to support processor-specific platform images and ↵Johnnie Birch2011-03-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | emulators. This is a first (and largest) patch in a series of patches over the next month to extend the AVD and ADT eclipse plugin to support processor-specific platform images and emulators. This patch is intended to co-exist with patches to create x86 emulator environments and overall SDK support. There is an overall expectation that the sdk building process will be updated to meet the following expectations... It is not in the scope of these UI patches to change the overall sdk building structure. expectation #1: tools/emulator[.exe] -- ARM tools/emulator-x86[.exe] -- x86 tools/emulator-foo[.exe] -- an arbitrary additional architecture (extensible) expectation #2: platforms/android-XXX/images/arm - location of kernel/images for ARM platforms/android-XXX/images/x86 - location of kernel/images for x86 platforms/android-XXX/images/foo - location of kernel/images for arbitrary architecture expectation #3 In the event that add-ons are in the SDK, add-ons/addon_XXX/images/arm - location of kernel/images for ARM add-ons/addon_XXX/images/x86 - location of kernel/images for x86 add-ons/addon_XXX/images/foo - location of kernel/images for arbitrary architecture NOTE: For "earlier"/legacy api levels, it is assumed that it is ARM only and the images will be in platforms/android-XXX/images and add-ons/addon_XXX/images When an API level is chosen in AVD, it scans the appropriate API directories and determines if the image directory is "legacy" or if it has subdirectories. In the latter case, it populates the list of potential processors using these directory names (and some prettyprinting for well known architectures) tested using "android" command line to start AVD on linux and windows tested using Eclipse plugin AVD integration on linux and windows REMINDER: You need to change the directory layout of images and add the right emulator-XXX[.exe] to test it If one uses the "android" command line to create an AVD from the command line, the processor type is assumed to be arm today. A future patch will be needed to add command line processor type selectivity Change-Id: Ifd7c39bf93c6e926f62407bfed024d2789efb41a
* Make the sdklib/sdkuilib tests built by the build system.Xavier Ducrohet2011-02-241-0/+27
Change-Id: I9ec9175e0734a5b07fa5b3879cdf7b1ef0056d27