Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Automated refactor of Label.parseAbsolute() to always pass a repository mapping | 2018-06-27 | |
| | | | | | RELNOTES: None PiperOrigin-RevId: 202360925 | ||
* | Make createMainDexProguardSpec public. | 2018-01-19 | |
| | | | | | RELNOTES: None. PiperOrigin-RevId: 182579590 | ||
* | Bazel, Windows: sh_binary now builds a .cmd file | 2017-07-05 | |
| | | | | | | | | | | | | | | | | | | | | | | | | On Linux/MacOS, sh_binary creates an output file with the same name as the rule. The file is a symlink pointing to the main script of the rule (sh_binary.srcs only allows one file.) On Windows sh_binary also creates an output file called the same as the rule, but it's a copy of the main script file (due to lack of symlink support on Windows). However the rule now also creates the <rulename>.cmd output, which is a wrapper script similar to the java_binary-generated launcher. If however the sh_binary rule's name ends with ".exe", ".cmd", or ".bat", and its main file also ends with the same extension, then sh_binary will not create the launcher .cmd file, and will copy the main file to the output tree instead. Change-Id: Idcf92ce3bb254bd6d9a1fb5c659a52220efe19aa PiperOrigin-RevId: 160805720 | ||
* | Enable incremental dexing by default. | 2017-07-03 | |
| | | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/3045. RELNOTES: Enable --incremental_dexing for Android builds by default. Note that some dexopts are incompatible with incremental dexing, including --force-jumbo. PiperOrigin-RevId: 160650101 | ||
* | Open source AndroidBinaryMultidexTest. | 2017-04-11 | |
This includes tests for the feature in https://github.com/bazelbuild/bazel/issues/1936. RELNOTES: None PiperOrigin-RevId: 152734391 |