- 31 Jul, 2015 1 commit
-
-
Daniel Rosenberg authored
ro.build.system_root_image is true if the root directory is built into the system image. Change-Id: I17208ebd004c63aebb09db6c3e5f795619e73bd2
-
- 29 Jul, 2015 4 commits
-
-
Tao Bao authored
When creating incremental OTAs, we should always use the fstab from the source build instead of the target. Bug: 21948974 Change-Id: Iff44130f88a679b253ea1adcfac4ed8566ce9cc7
-
Ying Wang authored
-
Elliott Hughes authored
-
Elliott Hughes authored
Change-Id: I11284ceddf08eb284af56360f0cf80f4725c98e9
-
- 28 Jul, 2015 6 commits
-
-
Tao Bao authored
-
Fredrik Roubert authored
Currently, DEX2OATD_DEPENDENCY is created by appending $(DEX2OATD) to the value of DEX2OAT_DEPENDENCY and then if USE_DEX2OAT_DEBUG is set, DEX2OAT_DEPENDENCY is set to DEX2OATD_DEPENDENCY, adding a dependency on $(DEX2OAT) even in configurations where this will not be built. This change removes DEX2OATD and DEX2OATD_DEPENDENCY entirely to instead assign dex2oat or dex2oatd to DEX2OAT depending on USE_DEX2OAT_DEBUG, making it possible to build with these flags set: USE_DEX2OAT_DEBUG=true ART_BUILD_HOST_NDEBUG=false ART_BUILD_HOST_DEBUG=true ART_BUILD_TARGET_NDEBUG=false ART_BUILD_TARGET_DEBUG=true make build-art-host Change-Id: I4fa75d1b7e9751c73c43ec943fd8446cc231a070
-
Elliott Hughes authored
-
Elliott Hughes authored
There's no implementation of these functions. Change-Id: Ic12286ccd1a392be32e5da67e5b7637bac4820f6
-
Dan Albert authored
-
- 27 Jul, 2015 3 commits
-
-
Dan Albert authored
Change-Id: I2cd97b453ad24cc4e5d59b4035e861df41b8cbb9
-
Ying Wang authored
-
Ying Wang authored
Change-Id: I31740673829e578d7fc0edd895868bf1f21cfe15
-
- 24 Jul, 2015 6 commits
-
-
Ying Wang authored
-
Ying Wang authored
Fix mmma uses like "mmma ./external/apache-harmony" by removing the leading ./ in entries in BUILD_MODULES_IN_PATHS. Change-Id: I414e734c8a29434fc89ddb2b745613c33709c5e3
-
Colin Cross authored
-
Brian Carlstrom authored
-
Colin Cross authored
If USE_NINJA=true, use kati to translate makefiles into ninja files, and then execute them with ninja. Builds kati from source using simplified versions of the rules in binary.mk and definitions.mk. Adds two new goals when USE_NINJA=true: generateonly will regenerate build.ninja but not rebuild (useful for comparing build.ninja output between runs), and fastincremental will skip regenerating build.ninja and go directly to running ninja, providing ~5 second incremental builds. Change-Id: Ib85399e730f1fbb1be7371fafeee7d1c31080771
-
Brian Carlstrom authored
Change-Id: Ie9b550367f7c6b91d46dc2506c420a45b0d39703
-
- 23 Jul, 2015 2 commits
-
-
Colin Cross authored
-
Colin Cross authored
Add blueprint, kati, and soong subdirectories to .gitignore so nothing gets committed there when new subprojects are added to the manifest. Change-Id: I888b94a89c87d99c8d28e8abd07a830f9cd86702
-
- 21 Jul, 2015 13 commits
-
-
Ying Wang authored
-
Ying Wang authored
-
Ying Wang authored
Change-Id: I6a84ec59194c48f4291480cb0c94db0da488518c
-
Ying Wang authored
- Deleted unused functions in definitions.mk. - lint is never fully functional in the platform source tree. - Retire LOCAL_DIST_BUNDLED_BINARIES: now the build system/framework supports JNI embedded in apk. Change-Id: I6314cb20d1544c704ccbc4c1f9cccb9c54fb5a51
-
Ying Wang authored
-
Colin Cross authored
-
Evgenii Stepanov authored
-
Tao Bao authored
-
Shinichiro Hamaji authored
-
Shinichiro Hamaji authored
I'm adding a rule which regenerates ninja files to kati: https://github.com/shinh/kati/commit/8666cfba20bf4ff0e59053dcfa7bcac9896bcf16 With this regeneration rule, unnecessary re-generation will happen when these .mk files are updated even if there are no changes in their contents. With this patch, these .mk files are updated only when the contents will be actually changed. Change-Id: I4c796f9454502f6bb25019b3806ca577ea5258c1
-
Ying Wang authored
-
Ying Wang authored
For apps_only (also PDK build) we use prebuilt host tools in prebuilts/sdk/tools; For platform build we use tools built from source. Auto-clean intermediate files of these tools when build type change is detected. Bug: 20213206 Change-Id: I9173af322684c017fdb91a3abfbe39ecfe5650e9 (cherry-pick from commit 036b53b6)
-
- 20 Jul, 2015 2 commits
-
-
Evgenii Stepanov authored
Workaround for https://code.google.com/p/address-sanitizer/issues/detail?id=387. Change-Id: I151c3f0eb7e2a4c92a64192a0b43ac17646eab5c
-
Dan Albert authored
-
- 19 Jul, 2015 1 commit
-
-
Tao Bao authored
A few properties are stored as links to the files in the out/ directory, which are no longer available when (re)packing from target_files zip. Redirect those properties to the actual files in the unzipped directory when repacking. Change-Id: I18e930cbea224ab9c6db8d4e721b1c266a671db6
-
- 18 Jul, 2015 1 commit
-
-
Colin Cross authored
Using $(BUILD_NUMBER) inside a rule causes odd behavior, as the rule is different every time make is run, but since make doesn't depend on the command line it only ends up being built with the new value if some other dependency has changed. To allow ninja, which does depend on the command line, to provide the same behavior, store the build number in out/build_number.txt, and use a shell expansion to cat the file in rules that use it. This will cause the rule command to stay identical between builds, while still getting the new build number if the rule is rerun for a dependency. Also use the same trick for BUILD_FINGERPRINT, and the date in droiddoc rules. Change-Id: I6c5e6b6b3ef4c613563d7f5604df0e401575ba5f
-
- 17 Jul, 2015 1 commit
-
-
Colin Cross authored
-