| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118563271
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118561661
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118560010
|
|
|
|
|
|
|
| |
This is necessary because build-runfiles depends on the msys shared library, which (as per DLL lookup rules on Windows) is checked under the entries of PATH.
--
MOS_MIGRATED_REVID=118556684
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel http://ci.bazel.io/job/Bazel/417/JAVA_VERSION=1.8,PLATFORM_NAME=linux-x86_64/console
by using a Guava 20 feature, while Gauva 20 is not yet released.
*** Original change description ***
Set -fmodules-cache-path to be rooted in the genfiles directory whenever modules are enabled.
Also warn when -fmodules-cache-path is explicitly set by the user (either in configuration or rule attributes)
--
MOS_MIGRATED_REVID=118555994
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bazel clean never runs any actions, hence any message
about running actions would confuse the user. Therefore,
signal that clean is a non-building command so that the
experimental UI knows not the report about progress of
building.
--
Change-Id: I193f199b052e990992359bc9efdbe34db397ac5f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3125
MOS_MIGRATED_REVID=118554435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118547283
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118532668
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118525960
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118523482
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=118518790
|
|
|
|
|
|
|
| |
--objc_generate_debug_symbols. These are delivered in distinct files, with an architecture identifier.
--
MOS_MIGRATED_REVID=118510432
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118500217
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118488877
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118488791
|
|
|
|
|
|
|
| |
Avoids spurious diagnostics about annotation processor generated class names not matching the file path.
--
MOS_MIGRATED_REVID=118488628
|
|
|
|
|
|
|
| |
JavaBuilder overwrites files when extracting source jars, silently ignoring duplicates. It it'd be better if it didn't, but until it's fixed turbine should have the same behaviour.
--
MOS_MIGRATED_REVID=118487939
|
|
|
|
|
|
|
| |
RELNOTES: Restrict file types allowed for "strings" attribute to ".strings".
--
MOS_MIGRATED_REVID=118479031
|
|
|
|
|
|
|
|
|
| |
modules are enabled.
Also warn when -fmodules-cache-path is explicitly set by the user (either in configuration or rule attributes)
--
MOS_MIGRATED_REVID=118478856
|
|
|
|
|
|
|
|
| |
This is so that we can access the build options during creation, which is a
step towards making the coverage module stateless.
--
MOS_MIGRATED_REVID=118475354
|
|
|
|
|
|
|
| |
This is mostly mechanical, cleaning up the vestigal marks of combining the value and key. The only mildly odd change is making the OverwritableConsumer and NonOverwritableConsumer package visible, for testing purposes.
--
MOS_MIGRATED_REVID=118474980
|
|
|
|
|
|
|
| |
":extra_entitlements".
--
MOS_MIGRATED_REVID=118473605
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118473491
|
|
|
|
|
|
|
| |
--
Change-Id: I7830558b688fb648d6f931bf79e82b9ee65bb18c
Reviewed-on: https://bazel-review.googlesource.com/c/3160/
MOS_MIGRATED_REVID=118472905
|
|
|
|
|
|
|
| |
This makes the late initialization of BuildView more obviously safe.
--
MOS_MIGRATED_REVID=118469655
|
|
|
|
|
|
|
| |
ConfigurationDistinguisher.EXTENSION to "IOS_APPLICATION" and "IOS_EXTENSION".
--
MOS_MIGRATED_REVID=118468650
|
|
|
|
|
|
|
|
|
| |
Introduces two new interfaces:
DataValue, which compliments DataKey and allows a cleaner interface MergeConflict
AndroidDataSet.KeyValueConsumer, abstraction that allows a common interface for consuming parsed resources, which is a lot cleanr for DataValue as well.
--
MOS_MIGRATED_REVID=118466739
|
|
|
|
|
|
|
| |
those modules already contain all the headers that are needed.
--
MOS_MIGRATED_REVID=118457691
|
|
|
|
|
|
|
| |
looking up actions registered from Aspects that use a non-empty AspectParameters.
--
MOS_MIGRATED_REVID=118455180
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As explained in commit 37f3e9ee, after completion of the build, there
is no need any more to update the progress bar. Instead, its last line,
if any, can just float into the scroll-back buffer. From then on, STDOUT
and STDERR events are just passed through. Do so as well for any late
INFO, WARNING, or ERROR events. This will allow avoiding pointless
messages in commands like 'bazel clean' (the patch removing those messages
will also provide an appropriate integration test).
Unfortunately, to make this work properly, we must ensure that both
event handlers get informed about the fact that we have a no-build
command. To do this, we register the event handler with the intended
IO stream on the event bus, as well as a passively observing variant of the
event handler that has direct acces to the full output stream.
--
Change-Id: I148dc0065b6343e4a2a225b2d4fa615b4f720ff5
Reviewed-on: https://bazel-review.googlesource.com/#/c/3124
MOS_MIGRATED_REVID=118444275
|
|
|
|
|
|
|
| |
tests without binary_under_test
--
MOS_MIGRATED_REVID=118422688
|
|
|
|
|
|
|
|
|
| |
".plist"].
RELNOTES: Restrict file types used for "entitlements" attribute to [".entitlements", ".plist"]
--
MOS_MIGRATED_REVID=118416261
|
|
|
|
|
|
|
| |
non-keep-going build. Setting errorDepKey was only mostly harmless, to mix memes. (Actually, it was quite harmful.)
--
MOS_MIGRATED_REVID=118410594
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118410183
|
|
|
|
|
|
|
|
|
| |
The lack of cc_library dependencies in generated Xcode projects can be worked around using _fully_linked.a and objc_import, but some include files still fail to propagate. In particular this affects genrule outputs and proto headers.
This fixes that issue.
--
MOS_MIGRATED_REVID=118397125
|
|
|
|
|
|
|
| |
instances by dependant objc_binary targets.
--
MOS_MIGRATED_REVID=118395529
|
|
|
|
|
|
|
| |
before)
--
MOS_MIGRATED_REVID=118394551
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118383557
|
|
|
|
|
|
|
|
|
| |
encountered during a build
Currently when evaluating a file or symlink leading to an external mutable object, Blaze throws an exception with unclear messages. The message does not contain the actual path but rather [/]/[] instead. This change updates FileFunction to allow bubbling up the error with the accurate path.
--
MOS_MIGRATED_REVID=118381323
|
|
|
|
|
|
|
| |
instead of DefaultSubject.
--
MOS_MIGRATED_REVID=118261285
|
|
|
|
|
|
|
| |
we could get an NPE if one initializes a data structure the other uses. Also delete an unused field and do a small visibility drive-by.
--
MOS_MIGRATED_REVID=118248373
|
|
|
|
| |
MOS_MIGRATED_REVID=118246740
|
|
|
|
|
|
|
| |
catastrophe. It doesn't add any logging information, and can mask the source of a crash if the crash has broken some invariants. <speculation>For instance, if we are crashing due to an OutOfMemoryError, the graph map may be in an inconsistent state where an attempt to add to it deleted a node</speculation>.
--
MOS_MIGRATED_REVID=118242401
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=118242131
|
|
|
|
|
|
|
|
|
|
| |
Removes ResourceMap from AndroidDataSet, now the merge operates directly on the AndroidDataSet instances.
Change tests to use Map<DataKey, Data?> instead of List<Data?>.
Add tests for finding conflicts during AndroidDataSet creation.
Make MergeConflict more test friendly by sorting Paths on creation.
--
MOS_MIGRATED_REVID=118240635
|
|
|
|
|
|
|
|
| |
Removes the remaining IO from Resolver, which is now only responsible for
rule dependency logic.
--
MOS_MIGRATED_REVID=118240098
|
|
|
|
|
|
|
| |
can trigger on it.
--
MOS_MIGRATED_REVID=118234431
|
|
|
|
|
|
|
|
|
| |
it is incorrect.
Currently when you build an app using the built-in rule, the resources compile to google.bazel.R, but the GMS libs need com.google.android.gms.R, so InflateExceptions occur - AdView for one.
--
MOS_MIGRATED_REVID=118204766
|
|
|
|
|
|
|
| |
Making the other classes much more testable!
--
MOS_MIGRATED_REVID=118203206
|
|
|
|
|
|
|
|
|
| |
FileStateValues for output files can make their way into the Skyframe graph if a source file is symlink to an output file.
Also fix a bug where ExternalFilesHelper#isExternalFileSeen would always return true after returning true once in the past. This meant if an external file ever made its way into the Skyframe graph, we would always do a full graph scan at the beginning of each build (iow, we would always waste some CPU time doing nothing interesting).
--
MOS_MIGRATED_REVID=118190190
|