| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
command to CMD.EXE.
Fix https://github.com/bazelbuild/bazel/issues/2040#issuecomment-322980147
RELNOTES: None
PiperOrigin-RevId: 165562681
|
|
|
|
|
|
|
| |
We rarely need it, it's not useful to keep it in memory.
RELNOTES: None.
PiperOrigin-RevId: 165562119
|
|
|
|
|
|
|
|
|
| |
of the configuration in genrules.
This is necessary because if one uses a java_runtime rule that has java_home="$(VAR") and VAR is set to an absolute path, BuildConfiguration won't be able to resolve VAR (since it's a Make variable and thus can't affect other Make variables), Blaze won't be able to tell that it's an absolute value and thus will prepend the package name of the java_runtime rule to it, e.g. resulting in a//foo/bar instead of /foo/bar if the java_runtime rule is in package a.
RELNOTES: None.
PiperOrigin-RevId: 165555251
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
host configuration.
I think the comment I'm deleting is misleading. PAR file construction
already has special handling of the input manifest, and host tools do
get their runfiles when executed remotely. They don't get them for
local execution, but users who care about that don't need to pass the
non-default --nobuild_runfile_links option.
RELNOTES: None.
PiperOrigin-RevId: 165535870
|
|
|
|
|
|
|
|
|
|
| |
roots
It also changes a few accessors of utility methods in Skyframe library. It
refactors the QueryExpressionMapper to use a general QueryExpressionVisitor.
RELNOTES: None
PiperOrigin-RevId: 165534908
|
|
|
|
|
|
|
|
| |
In the future += on lists will work like .extend (by mutating the list) instead
of copying the list items to a new list (current behavior). Some .bzl files
need to be cleaned up to be compatible with both behaviors.
PiperOrigin-RevId: 165528261
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2829
Without this change, there is no way to use Bazel to build a release Android build (--noincremental_dexing) with java 8 and protos.
RELNOTES: Java protos are compiled to Java 7 bytecode.
PiperOrigin-RevId: 165500316
|
|
|
|
| |
PiperOrigin-RevId: 165493537
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165489091
|
|
|
|
|
|
|
| |
is a target.
RELNOTES: None
PiperOrigin-RevId: 165482057
|
|
|
|
| |
PiperOrigin-RevId: 165478994
|
|
|
|
|
|
|
| |
Add unit tests for individual flag usage output. Also move around some of the sample expansion function test options, which could be used more widely, to minimize recreating the boilerplate samples.
RELNOTES: None.
PiperOrigin-RevId: 165478776
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 165477209
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165471665
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165469671
|
|
|
|
|
| |
RELNOTES: Top-level `if` statements are now forbidden.
PiperOrigin-RevId: 165469101
|
|
|
|
|
|
|
|
| |
After this change, it will be easier to move the validate() methods to a
separate visitor.
RELNOTES: None.
PiperOrigin-RevId: 165467838
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165465128
|
|
|
|
|
|
| |
Fixes #3329.
PiperOrigin-RevId: 165443367
|
|
|
|
| |
PiperOrigin-RevId: 165439218
|
|
|
|
|
|
|
|
|
|
| |
As part of the migration away from android_resources, add a flag that causes
failures if android_resources is encountered. This makes it easier to test that
all android_resources targets have been removed without actually breaking any
builds.
RELNOTES: none
PiperOrigin-RevId: 165437983
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165434934
|
|
|
|
|
|
|
| |
A bug was introduced in patch 9626bb4923c74c6d3c09b7438eb24b32191053df, where a cache miss would not result in action re-execution, making the cache miss non-recoverable.
RELNOTES: fixes #3552
PiperOrigin-RevId: 165434579
|
|
|
|
|
|
| |
Closes #3554.
PiperOrigin-RevId: 165426323
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 165422514
|
|
|
|
|
|
|
| |
disk have changed since it was launched, print *which* files have changed.
RELNOTES: Improved logging when workers have to be restarted due to its files having changed.
PiperOrigin-RevId: 165419664
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165419360
|
|
|
|
|
|
| |
This requires us to have OptionsData for all usage messages, since static functionality is being removed, but this should already have been the case. It was added as an optional argument when the expansion function feature was added, but there is actually no reason not to require it, as the public interface for usage text was already computing the optionsData anyway.
PiperOrigin-RevId: 165386893
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allowing add(Object) is too loose and can easily lead to programmer mistakes.
Because of type erasure, we can't use the same overload name for (eg.) add(NestedSet<String>) and add(NestedSet<Artifact>). The API is overhauled to use the same terms everywhere, eg. "add", "addPaths", "addExecPaths". This is similar to how it used to be a few CLs ago.
The API is overhauled to make sure it's consistent for all types. While tedious, the facade methods immediately dispatch to internal helpers, so implementation wise it's not too heavy.
While large, this CL is almost entirely an automated refactor.
PiperOrigin-RevId: 165358287
|
|
|
|
|
|
| |
replace the startup option after a deprecation period.
PiperOrigin-RevId: 165340514
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to perform a more gradual migration away from the
android_resources rule. Specifically, rather than move all android_resources
targets and simultaneously move all resources attributes, we can now first
transform all android_resources rules into android_library rules, and then
afterwards migrate dependencies on those rules from resources into deps. This
allows a two-part migration.
The resources attribute, once allowed to take android_library targets, should
continue to work exactly as before.
There is one change in behavior - for this to work, android_library targets now
need to build an output APK during resource processing. This APK will be
removed once the resources attribute is removed.
Once the migration is complete, the resources attribute will be removed
completely.
RELNOTES: none
PiperOrigin-RevId: 165313447
|
|
|
|
|
| |
RELNOTES: Removing a few unused objc_provider keys.
PiperOrigin-RevId: 165230824
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 165215334
|
|
|
|
|
|
|
|
|
|
|
| |
Send the startup options tagged with their origin so that the server has correct information about the command line as the client received it.
Removes the unconditional stderr printing of all bazelrc startup options in the bazel client. Instead, the startup options are sent to the server and the same informational printing is gated on the --announce_rc option. This avoids unconditional log spam to stderr early in startup. If the server is unreachable or there are errors parsing startup options, the message is still printed to stderr.
Fixes https://github.com/bazelbuild/bazel/issues/2530.
RELNOTES: --announce_rc now controls whether bazelrc startup options are printed to stderr.
PiperOrigin-RevId: 165211007
|
|
|
|
|
|
|
|
| |
This flag has been a noop for a while.
RELNOTES[INC]: Noop flag --deprecated_generate_xcode_project deleted.
PiperOrigin-RevId: 165199302
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165193696
|
|
|
|
|
|
|
|
|
| |
This enforces certain memory-efficient patterns. For deliberate use of dynamic strings, explicitly named overloads are introduced, with javadoc that guides the programmer into making the right choice.
This CL is a memory no-op on benchmarks, but it tries to prevent backslide by making sure programmers make conscious choices when they construct their command lines.
RELNOTES: None
PiperOrigin-RevId: 165185997
|
|
|
|
|
|
| |
of CcToolchainProvider as a "toolchain" in platform-based toolchain resolution.
PiperOrigin-RevId: 165185303
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165177605
|
|
|
|
| |
Change-Id: I56592ed4e507389d329377436223716c00348869
|
|
|
|
|
|
|
|
| |
If bazel runs under emacs, it emits messages about changing
of directories. In those messages, fix the product name.
Change-Id: I233a46db741dc4cd0dc5bfbaadbf2ad09c04952e
PiperOrigin-RevId: 165159721
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 165159163
|
|
|
|
|
|
|
|
| |
This allows more complex expressions to be called, not just identifiers.
For example, "x[0]()" is not a syntax error anymore.
RELNOTES: None
PiperOrigin-RevId: 165157981
|
|
|
|
|
|
|
| |
new blaze Java implementation sends the runtime jars encapsulated in a metadata
txt file, instead of listing them in the environment variable. The previous approach led to blaze crashing with an "Argument list too long" error.
PiperOrigin-RevId: 165155269
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165116857
|
|
|
|
|
|
| |
have equality.
PiperOrigin-RevId: 165039514
|
|
|
|
|
|
|
|
|
|
| |
AbstractSpawnRunner now uses a SpawnCache if one is registered, this allows
adding caching to any spawn runner without having to be aware of the
implementations.
I will delete the old CachedLocalSpawnRunner in a follow-up CL.
PiperOrigin-RevId: 165024382
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165015884
|
|
|
|
|
| |
RELNOTES:
PiperOrigin-RevId: 165012363
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 165012084
|