Android m preview source

Android m preview source

The official Gradle plugin to build Android applications.

The plugin adds several concepts to the Gradle DSL, all in the android extension:

• A default config. This lets you configure default values for your application.
• A product flavor. For example, a free or a paid-for flavour.
• A build type. There are 2 predefined build types, called release and debug . You can add additional build types.

If you do not define any flavors for your product, only the values from the default config are used. Flavor settings override the default config.

From this, the plugin will add the appropriate tasks to build each combination of build type and product flavor. The plugin will also define the following source directories:

• src/main/java — Java source to be included in all application variants.
• src/main/res — Resources to be included in all application variants.
• `src/main/AndroidManifest.xml’ — The application manifest (currently shared by all application variants).
• src/$BuildType/java — Java source to be included in all application variants with the given build type.
• src/$BuildType/res — Java source to be included in all application variants with the given build type.
• src/$ProductFlavor/java — Resources to be included in all application variants with the given product flavor.
• src/$ProductFlavor/res — Resources to be included in all application variants with the given product flavor.
• src/test/java — Test source to be included in all test applications.
• src/test$ProductFlavor/java — Test source to be include for the test application for the given product flavor.

You can configure these locations by configuring the associated source set provided by the android extension.

Compile time dependencies are declared in the usual way.

Have a look at the tests/basic/build.gradle build file and other projects in tests customized/build.gradle to see the DSL in action.

Configuration options

• android.target — required.
• android.defaultConfig.versionCode — defaults to that specified in src/main/AndroidManifest.xml
• android.defaultConfig.versionName — defaults to that specified in src/main/AndroidManifest.xml
• android.productFlavors.$flavor.packageName — defaults to that specified in src/main/AndroidManifest.xml
• android.productFlavors.$flavor.versionCode — defaults to $
• android.productFlavors.$flavor.versionName — defaults to $
• android.buildTypes.$type.zipAlign — defaults to true for release and false for debug
• android.sourceSets.main.java.srcDirs — defaults to src/main/java
• android.sourceSets.main.resources.srcDirs — defaults to src/main/res
• android.sourceSets.$flavor.java.srcDirs — defaults to src/$flavor/java
• android.sourceSets.$flavor.resources.srcDirs — defaults to src/$flavor/res
• android.sourceSets.$buildType.java.srcDirs — defaults to src/$buildType/java
• android.sourceSets.$buildType.resources.srcDirs — defaults to src/$buildType/res
• android.sourceSets.test.java.srcDirs — defaults to src/test/java
• android.sourceSets.test$Flavor.java.srcDirs — defaults to src/test$Flavor/java
• dependencies.compile — compile time dependencies for all applications.

Contents

The source tree contains the following:

• The builder directory contains the builder library.
• The gradle directory contains the plugin implementation.
• The tests directory contains various test applications used both as samples and tests by the plugin build system.

Usage

To build the plugin, run ./gradlew uploadArchives

To build the plugin for release, removing the SNAPSHOT from the version, run ./gradlew —init-script release.gradle

To import the plugin into the IDE, run ./gradlew idea or ./gradlew eclipse .

To build a test application:

1. cd into the root directory of the test application.
2. Edit the local.properties file to point at your local install of the Android SDK. Normally, these files would not be checked into source control, but would be generated when the project is bootstrapped.
3. Run ../../gradlew tasks to see the tasks that are available.

You can also run these tasks:

• assemble — builds all combinations of build type and product flavor
• assemble$BuildType — build all flavors for the given build type.
• assemble$ProductFlavor — build all build types for the given product flavor.
• assemble$ProductFlavor$BuildType — build the given application variant.
• install$ProductFlavor$BuildType — build and install the given application variant.

Implementation

For each variant (product-flavor, build-type):

• Generates resource source files into build/source from resource directories (main-source-set, product-flavor-source-set, build-type-source-set)
• Compile source files (main-source-set, product-flavor-source-set, build-type-source-set, generated-source).
• Converts the bytecode into build/libs
• Crunches resources in build/resources
• Packages the resource into build/libs
• Assembles the application package into build/libs .

Источник

Android m preview source

The official Gradle plugin to build Android applications.

The plugin adds several concepts to the Gradle DSL, all in the android extension:

• A default config. This lets you configure default values for your application.
• A product flavor. For example, a free or a paid-for flavour.
• A build type. There are 2 predefined build types, called release and debug . You can add additional build types.

If you do not define any flavors for your product, only the values from the default config are used. Flavor settings override the default config.

From this, the plugin will add the appropriate tasks to build each combination of build type and product flavor. The plugin will also define the following source directories:

• src/main/java — Java source to be included in all application variants.
• src/main/res — Resources to be included in all application variants.
• `src/main/AndroidManifest.xml’ — The application manifest (currently shared by all application variants).
• src/$BuildType/java — Java source to be included in all application variants with the given build type.
• src/$BuildType/res — Java source to be included in all application variants with the given build type.
• src/$ProductFlavor/java — Resources to be included in all application variants with the given product flavor.
• src/$ProductFlavor/res — Resources to be included in all application variants with the given product flavor.
• src/test/java — Test source to be included in all test applications.
• src/test$ProductFlavor/java — Test source to be include for the test application for the given product flavor.

You can configure these locations by configuring the associated source set provided by the android extension.

Compile time dependencies are declared in the usual way.

Have a look at the tests/basic/build.gradle build file and other projects in tests customized/build.gradle to see the DSL in action.

Configuration options

• android.target — required.
• android.defaultConfig.versionCode — defaults to that specified in src/main/AndroidManifest.xml
• android.defaultConfig.versionName — defaults to that specified in src/main/AndroidManifest.xml
• android.productFlavors.$flavor.packageName — defaults to that specified in src/main/AndroidManifest.xml
• android.productFlavors.$flavor.versionCode — defaults to $
• android.productFlavors.$flavor.versionName — defaults to $
• android.buildTypes.$type.zipAlign — defaults to true for release and false for debug
• android.sourceSets.main.java.srcDirs — defaults to src/main/java
• android.sourceSets.main.resources.srcDirs — defaults to src/main/res
• android.sourceSets.$flavor.java.srcDirs — defaults to src/$flavor/java
• android.sourceSets.$flavor.resources.srcDirs — defaults to src/$flavor/res
• android.sourceSets.$buildType.java.srcDirs — defaults to src/$buildType/java
• android.sourceSets.$buildType.resources.srcDirs — defaults to src/$buildType/res
• android.sourceSets.test.java.srcDirs — defaults to src/test/java
• android.sourceSets.test$Flavor.java.srcDirs — defaults to src/test$Flavor/java
• dependencies.compile — compile time dependencies for all applications.

Contents

The source tree contains the following:

• The builder directory contains the builder library.
• The gradle directory contains the plugin implementation.
• The tests directory contains various test applications used both as samples and tests by the plugin build system.

Usage

To build the plugin, run ./gradlew uploadArchives

To build the plugin for release, removing the SNAPSHOT from the version, run ./gradlew —init-script release.gradle

To import the plugin into the IDE, run ./gradlew idea or ./gradlew eclipse .

To build a test application:

1. cd into the root directory of the test application.
2. Edit the local.properties file to point at your local install of the Android SDK. Normally, these files would not be checked into source control, but would be generated when the project is bootstrapped.
3. Run ../../gradlew tasks to see the tasks that are available.

You can also run these tasks:

• assemble — builds all combinations of build type and product flavor
• assemble$BuildType — build all flavors for the given build type.
• assemble$ProductFlavor — build all build types for the given product flavor.
• assemble$ProductFlavor$BuildType — build the given application variant.
• install$ProductFlavor$BuildType — build and install the given application variant.

Implementation

For each variant (product-flavor, build-type):

• Generates resource source files into build/source from resource directories (main-source-set, product-flavor-source-set, build-type-source-set)
• Compile source files (main-source-set, product-flavor-source-set, build-type-source-set, generated-source).
• Converts the bytecode into build/libs
• Crunches resources in build/resources
• Packages the resource into build/libs
• Assembles the application package into build/libs .

Источник

Working on bionic

What are the big pieces of bionic?

libc/ — libc.so, libc.a

The C library. Stuff like fopen(3) and kill(2) .

libm/ — libm.so, libm.a

The math library. Traditionally Unix systems kept stuff like sin(3) and cos(3) in a separate library to save space in the days before shared libraries.

libdl/ — libdl.so

The dynamic linker interface library. This is actually just a bunch of stubs that the dynamic linker replaces with pointers to its own implementation at runtime. This is where stuff like dlopen(3) lives.

libstdc++/ — libstdc++.so

The C++ ABI support functions. The C++ compiler doesn’t know how to implement thread-safe static initialization and the like, so it just calls functions that are supplied by the system. Stuff like __cxa_guard_acquire and __cxa_pure_virtual live here.

linker/ — /system/bin/linker and /system/bin/linker64

The dynamic linker. When you run a dynamically-linked executable, its ELF file has a DT_INTERP entry that says “use the following program to start me”. On Android, that‘s either linker or linker64 (depending on whether it’s a 32-bit or 64-bit executable). It’s responsible for loading the ELF executable into memory and resolving references to symbols (so that when your code tries to jump to fopen(3) , say, it lands in the right place).

tests/ — unit tests

The tests/ directory contains unit tests. Roughly arranged as one file per publicly-exported header file.

benchmarks/ — benchmarks

The benchmarks/ directory contains benchmarks.

What’s in libc/?

Adding system calls

Adding a system call usually involves:

1. Add entries to SYSCALLS.TXT. See SYSCALLS.TXT itself for documentation on the format.
2. Run the gensyscalls.py script.
3. Add constants (and perhaps types) to the appropriate header file. Note that you should check to see whether the constants are already in kernel uapi header files, in which case you just need to make sure that the appropriate POSIX header file in libc/include/ includes the relevant file or files.
4. Add function declarations to the appropriate header file.
5. Add at least basic tests. Even a test that deliberately supplies an invalid argument helps check that we’re generating the right symbol and have the right declaration in the header file. (And strace(1) can confirm that the correct system call is being made.)

Updating kernel header files

As mentioned above, this is currently a two-step process:

1. Use generate_uapi_headers.sh to go from a Linux source tree to appropriate contents for external/kernel-headers/.
2. Run update_all.py to scrub those headers and import them into bionic.

Updating tzdata

This is fully automated:

Verifying changes

If you make a change that is likely to have a wide effect on the tree (such as a libc header change), you should run make checkbuild . A regular make will not build the entire tree; just the minimum number of projects that are required for the device. Tests, additional developer tools, and various other modules will not be built. Note that make checkbuild will not be complete either, as make tests covers a few additional modules, but generally speaking make checkbuild is enough.

Running the tests

The tests are all built from the tests/ directory.

Device tests

Host tests

The host tests require that you have lunch ed either an x86 or x86_64 target.

Against glibc

As a way to check that our tests do in fact test the correct behavior (and not just the behavior we think is correct), it is possible to run the tests against the host’s glibc. The executables are already in your path.

Gathering test coverage

For either host or target coverage, you must first:

• $ export NATIVE_COVERAGE=true
  • Note that the build system is ignorant to this flag being toggled, i.e. if you change this flag, you will have to manually rebuild bionic.
• Set bionic_coverage=true in libc/Android.mk and libm/Android.mk .

Coverage from device tests

acov will pull all coverage information from the device, push it to the right directories, run lcov , and open the coverage report in your browser.

Coverage from host tests

First, build and run the host tests as usual (see above).

The coverage report is now available at covreport/index.html .

LP32 ABI bugs

This probably belongs in the NDK documentation rather than here, but these are the known ABI bugs in LP32:

off_t is 32-bit. There is off64_t , but no _FILE_OFFSET_BITS support. Many of the off64_t functions are missing in older releases, and stdio uses 32-bit offsets, so there’s no way to fully implement _FILE_OFFSET_BITS .

Источник