| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132551909
|
|
|
|
|
|
|
|
|
|
|
| |
It's not supposed to cover direct deps and trans
deps according to the documentation anyway. Also
prepare to move the --strictMerge flag. The
option isn't checked anymore. There's only one
type of merging.
--
MOS_MIGRATED_REVID=132444314
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132088164
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131995795
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131986739
|
|
|
|
|
|
|
|
|
| |
--apk_signing_method flag. Default is legacy_v1 which is the already existing functionality.
Promotes AndroidBinary.ApkActionBuilder to a toplevel abstract class ApkActionsBuilder with two implementations, one for default signing/zipaligning and one for ApkSignerTool based signing/zipaligning. In addition to build the action for constructing the APK, it now responsible for orchestrating the various tools to build, sign and zipalign the APK.
--
MOS_MIGRATED_REVID=131889338
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131832497
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131692718
|
|
|
|
|
|
|
|
|
|
| |
Behind a flag. Flow is:
parse -> merge -> validate
\--> compile
With fewer deps across the merge steps.
--
MOS_MIGRATED_REVID=131634115
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part 3 of the 3 new proposed android_library res
processing actions. Pulls a zip file from the
merging action, unpacks it, and then validates
the results with aapt. Get an R.txt and srcjar
w/ javadocs from aapt. In order to the get the
R.txt, I think you need to ask for the R.java
sources anyway.
Split the processResources() into a runAapt()
function that can be reused.
Hookup in bazel coming separately.
--
MOS_MIGRATED_REVID=131618410
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part 2 of the 3 new proposed android_library res
processing actions. The primary and deps are all
assumed to be parsed+summarized in a protobuf.
Represent that with a new class (similar to
DependencyAndroidData but w/out R.txt).
Avoid having "manifest" artifacts as deps input,
and instead use "label", since that is only used
in a warning. DepAD still uses the manifest for
#asSymbolFileProvider, so we keep it there.
Move loading the primary out of the merge function
so that we can share the merge function with this
style of primary data, and the existing style of
of primary data (UnvalidatedAndroidData).
This produces an R class.jar and a zip file to
pass along to a future validation action. Images
are stubbed out since they are irrelevant to the
validation action.
--
MOS_MIGRATED_REVID=131604421
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is already ignored and the real jar used as
the compileTime jar in AndroidCommon. It's only
used by the ide-resolve output group. The real
jar is pretty close to the header jar in terms
of content (field inits deleted).
Tradeoff: The real jar is ~33% bigger (w/ same
compression level), vs save build time and space
by skipping the hjar actions and artifacts.
At android_binary level, the hjar action can take
~40 seconds in some cases. At the library level,
the hjar time is pretty tiny.
hjars are not compressed. We could compress the
real jars to make up for the extra 30% size
(and beat the hjar size), but that adds ~25%
elapsed time to do the compression (e.g.,
10s vs 7.5s). Compression can shrink the jar
2-3x (37MB vs 100MB).
--
MOS_MIGRATED_REVID=131588283
|
|
|
|
| |
MOS_MIGRATED_REVID=131464027
|
|
|
|
|
|
|
| |
because they contain useless stub ids.
--
MOS_MIGRATED_REVID=131449999
|
|
|
|
|
|
|
| |
dependencies.
--
MOS_MIGRATED_REVID=131434655
|
|
|
|
|
|
|
|
|
|
| |
ProGuard:
- The list of dead code in the input class files (-printusage).
- The list of classes and class members matched by the various '-keep' options (-printseeds).
--
MOS_MIGRATED_REVID=131414162
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward with fixes.
--
MOS_MIGRATED_REVID=131224077
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130469884
|
|
|
|
|
|
|
| |
The only place we now don't handle InterruptedException is in the action graph created after analysis, since I'm not sure that will be around for that much longer.
--
MOS_MIGRATED_REVID=130327770
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130326607
|
|
|
|
|
|
|
|
|
|
| |
The processed manifest has applicationId subbing
while the merged one is before substitution (if
the developer hasn't migrated to the new gradle-
style manifest merger).
--
MOS_MIGRATED_REVID=130046777
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130016248
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This doesn't do anything yet, it's in preparation for the execroot rearranging
change. The execroot will have one bazel-out per repo, so it'll look like:
execroot/
repo1/
bazel-out/
local-fastbuild/
bin/
repo2/
bazel-out/
local-fastbuild/
bin/
genfiles/
repo3/
bazel-out/
local-fastbuild/
testlogs/
and so on. Thus, any output path (getBinDirectory() & friends) needs to know
what the repo name is. This changes so many places in the code I thought it
would be good to do separately, then just flip the functionality in the
execroot-rearranging commit.
While I was poking around, I changed all of the refs I could from getPackageRelativeArtifact() to getBin/GenfilesArtifact(), so that 1) rule implementation don't have to know as much about roots and 2) they'll be more isolated from other output dir changes.
`bazel info` and similar just return roots for the main repository.
The only "change" is passing around a target label in the Java rules.
Continues work on #1262.
--
MOS_MIGRATED_REVID=129985336
|
|
|
|
|
|
|
|
|
| |
don't do the split.
RELNOTES: Disable the Android split transition if --android_cpu and fat_apk_cpu are both empty.
--
MOS_MIGRATED_REVID=129931354
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a linker flag to set the internal DT_SONAME. This fixes #1578 for
SDK 24 and removes the warnings for previous SDKs. There is no need to
set the linker flag for android_librarys that depend on native code,
because the linker flag will be set by the android_binarys that depend
on that android_library.
Testing is done via `readelf` executable that is shipped with the NDK.
--
Change-Id: I16fdfe6522c8694ce51554289122bf035a61d9ec
Reviewed-on: https://bazel-review.googlesource.com/#/c/4302/
MOS_MIGRATED_REVID=129920256
|
|
|
|
|
|
|
|
|
|
| |
If header compilation is enabled, the compile-time dependency information is
produced by the header compilation action. The android rules were incorrectly
using the dependency information from the regular compilation, which defeated
the critical path improvement from header compilation.
--
MOS_MIGRATED_REVID=129505189
|
|
|
|
|
|
|
| |
on Windows by default)
--
MOS_MIGRATED_REVID=129319018
|
|
|
|
|
|
|
| |
We actually don't need it.
--
MOS_MIGRATED_REVID=129149261
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This change causes android_integration_test failing on Mac.
*** Original change description ***
Sets SONAME on shared objects in Android binaries.
Adds a linker flag to set the internal DT_SONAME. This fixes #1578 for
SDK 24 and removes the warnings for previous SDKs. There is no need to
set the linker flag for android_librarys that depend on native code,
because the linker flag will be set by the android_binarys that depend
on that android_library.
--
MOS_MIGRATED_REVID=129074607
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a linker flag to set the internal DT_SONAME. This fixes #1578 for
SDK 24 and removes the warnings for previous SDKs. There is no need to
set the linker flag for android_librarys that depend on native code,
because the linker flag will be set by the android_binarys that depend
on that android_library.
--
Change-Id: If6422f2c2677ec974a3682e3038d7fe159ed4978
Reviewed-on: https://bazel-review.googlesource.com/#/c/4210/
MOS_MIGRATED_REVID=128833820
|
|
|
|
|
|
|
| |
addTransitiveInputs
--
MOS_MIGRATED_REVID=128820723
|
|
|
|
|
|
|
|
| |
This way they can be shared with a resource merge
spawn action builder (similar cmdline conventions).
--
MOS_MIGRATED_REVID=128804575
|
|
|
|
|
|
|
|
| |
This reverts commit e65876a28965c72f7a48a16be3390ba7c5c97a6f.
This commit have not gone through the proper workflow.
Fixes #1582.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part of 3 proposed new actions:
- parsing action
- merging action
- validating action
Dependencies (directData and transitiveData)
expect the symbol files. If the merge action
produces the symbol files, then each merge
action depends on each other. Instead, produce
it in an action with just source resources as
prereqs to allow more parallelism.
Technically, we don't need a manifest as part
of the parameters. I debated about whether
to introduce a basic version of
UnvalidatedAndroidData or not.
--
MOS_MIGRATED_REVID=128599714
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
execroot change
This is in prep for making the execution root path for external repositories
../repo_name (instead of external/repo_name). Right now, the getRunfilesPath() returns that path, so that is renamed getExecRoot() (since the runfiles are really just a reflection of the execRoot structure). getSourceRoot() replaces getPathFragment, which has always been a confusing name (it's not clear from the name
what the difference is between it and getPackageFragment()). It returns the relative path to source files for external repositories (external/repo_name).
Also renamed/moved to more sensible class a few static RepositoryName fields.
--
MOS_MIGRATED_REVID=128594419
|
|
|
|
|
|
|
| |
removed from the global blazerc in unknown commit.
--
MOS_MIGRATED_REVID=128591745
|
|
|
|
|
|
|
|
|
|
| |
Adds a linker flag to set the internal DT_SONAME. This fixes #1578 for
SDK 24 and removes the warnings for previous SDKs. There is no need to
set the linker flag for android_librarys that depend on native code,
because the linker flag will be set by the android_binarys that depend
on that android_library.
Change-Id: I0d4fd78ffaf03c19ae3712bdeb28a52722a22f6f
|
|
|
|
|
|
|
|
| |
* Re-add proguard mapping file handling to ResourceShrinker to handle the fully Proguarded code, potentially including an obfuscation step.
* Update android_binary to provide the resource shrinker with the standard Proguard jar and obfuscation mapping instead of a custom built shrunk jar.
--
MOS_MIGRATED_REVID=128476602
|
|
|
|
|
|
|
|
|
|
| |
AndroidResourceSupportRule. This removes the exports_manifest attribute from
AndroidBinaryBaseRule and its children.
RELNOTES: Removes exports_manifest attribute from android_binary rule.
--
MOS_MIGRATED_REVID=128472120
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=128184440
|
|
|
|
|
|
|
| |
messages from manifest merging when using manifest_merger="android" on android_binary rules.
--
MOS_MIGRATED_REVID=127962630
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Forgot to do this, so we get compiler errors
since it can't find the R class imported under
the requested custom java package.
Also, avoid writing out the top-level R.class
file if there are no symbols. There is a test
that happens to check for this.
--
MOS_MIGRATED_REVID=127888913
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke Android targets with native code when cpu is explicitly set.
*** Original change description ***
RELNOTES: Improve Android split transition handling.
--
MOS_MIGRATED_REVID=127377943
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=127099896
|
|
|
|
| |
MOS_MIGRATED_REVID=127091947
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hook up the RClassGeneratorAction to blaze code.
This is currently only used for android_binary
targets to build the final R classes of the
binary + all of its libraries.
Behind a flag and off by default (flip on later).
--
MOS_MIGRATED_REVID=126935165
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the rclass_generator.sh, and fill in the
boiler-plate for mock tools, etc. Mostly cargo-
culting references to resources_processor.sh.
Rename earlier pieces to use RClassGenerator
prefix instead of AndroidResourceCompilation.
--
MOS_MIGRATED_REVID=126831848
|
|
|
|
| |
MOS_MIGRATED_REVID=126723341
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke some targets
--
MOS_MIGRATED_REVID=126574275
|
|
|
|
|
|
|
| |
by the Gradle resource shrinker in resources.txt.
--
MOS_MIGRATED_REVID=126420534
|