| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120325869
|
|
|
|
|
|
|
| |
This is apparently unused.
--
MOS_MIGRATED_REVID=120317405
|
|
|
|
|
|
|
| |
attribute based on the Rule itself (the transition may thus be determined based on the values of other attributes of the rule)
--
MOS_MIGRATED_REVID=120275649
|
|
|
|
|
|
|
| |
BuildConfiguration that is not the current rule context's configuration.
--
MOS_MIGRATED_REVID=120271518
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This prevents an ugly warning when you do something like:
new_local_repository(
name = "bazel_tools",
path = ".",
build_file = "BUILD",
)
--
MOS_MIGRATED_REVID=120271366
|
|
|
|
|
|
|
|
|
|
|
|
| |
With remote repositories, it is useful to do this to execute an input
file which isn't actually part of the source tree.
Closes #984
--
Change-Id: Ic986ea9bbe88e0edb933939ce1d7a8b6ea9d6e88
Reviewed-on: https://bazel-review.googlesource.com/#/c/3030/
MOS_MIGRATED_REVID=120248102
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
getTransitiveCompilationPrerequisites. The missing 'transitive' in the name is
misleading.
This change is a preparation for further refactorings that will in the end
introduce a getCompilationPrerequisites method that actually returns the
compilation prerequisites for a rule - as that will be require some more things
to be shuffled around in CppCompilationContext, this change gets the purely
syntactical change in first.
--
MOS_MIGRATED_REVID=120247461
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120241405
|
|
|
|
|
|
|
| |
when in gRPC mode.
--
MOS_MIGRATED_REVID=120233121
|
|
|
|
|
|
|
| |
Fixes #1066.
--
MOS_MIGRATED_REVID=120232176
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
|
|
|
|
| |
packages not in third_party. We don't need to police users' external repositories.
Fixes #1151
--
MOS_MIGRATED_REVID=120222222
|
|
|
|
|
|
|
|
| |
Consists of adding @Immutable annotations, adding final modifiers, and changing
the types of fields to immutable types.
--
MOS_MIGRATED_REVID=120221067
|
|
|
|
|
|
|
| |
requirements. Uses this mechanism to configure c/c++ compilation and linking for darwin execution from the crosstool.
--
MOS_MIGRATED_REVID=120218079
|
|
|
|
|
|
|
|
|
|
| |
Second pass.
Consists of adding @Immutable annotations, adding final modifiers, and changing
the types of fields to immutable types.
--
MOS_MIGRATED_REVID=120216592
|
|
|
|
|
|
|
| |
Its old name was confusing because resolve() and getDefault() do radically different things: getDefault() returns a good enough lie for when BuildConfiguration is not available, and resolve() resolves the dependency when we do have a BuildConfiguration.
--
MOS_MIGRATED_REVID=120212630
|
|
|
|
|
|
|
| |
Work towards #930.
--
MOS_MIGRATED_REVID=120205147
|
|
|
|
|
|
|
|
|
|
|
|
| |
The version command is not expected to every run any actions.
Hence any messages about progress of the build process or running
actions would be confusing. Therefore, signal this fact to allow
the experimental UI to present information accordingly.
--
Change-Id: I8a75704a39e161f52c4d008677f62e4b36097647
Reviewed-on: https://bazel-review.googlesource.com/#/c/3387
MOS_MIGRATED_REVID=120203058
|
|
|
|
|
|
|
|
|
|
|
| |
Drive-by fix: eliminate the GRPC messages from the console by passing a null logging function.
This also prepares us for the time when multiple commands will be running, because then we'll need to tell which command exactly we want to interrupt.
Work towards #930.
--
MOS_MIGRATED_REVID=120203008
|
|
|
|
|
|
|
| |
Work towards #930. With this, it's conceivable that server mode works on Windows to some degree (I haven't tried, though, because there are many issues that need to be fixed)
--
MOS_MIGRATED_REVID=120202037
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|
|
|
|
|
|
|
|
|
| |
If no AndroidSdkProvider is present, JackAspect exits with an error
instead of throwing and thus crashing Bazel. This is acceptable; the
Android rules which JackAspect is attached to will do the same.
--
MOS_MIGRATED_REVID=120150996
|
|
|
|
|
|
|
| |
For consistency with java_library.javacopts and the top-level --javacopts flag.
--
MOS_MIGRATED_REVID=120145920
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120145833
|
|
|
|
|
|
|
| |
target. We also no longer say that the target will not be built because it may well happen during a query, when no building is happening anyway.
--
MOS_MIGRATED_REVID=120130554
|
|
|
|
|
|
|
|
| |
builds with C++ modules as modules can be built without waiting on dependencies
that are only required for the module's implementation.
--
MOS_MIGRATED_REVID=120119435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120117310
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120115843
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120114796
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120112783
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120111522
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When reporting a multi-line test-failure message (the test that failed,
plus the paths to the log files) to the scrollback buffer, it makes sense
to end this whole block by an empty line. If, however, the test failure
does not report any logs (e.g., if the build was interrupted), the next
scroll-back buffer line can follow immediately to keep the scroll-back
buffer more compact.
--
Change-Id: I59d8ba9416d0a9bcbc8d959fee21cc94fa89018e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3386
MOS_MIGRATED_REVID=120108504
|
|
|
|
|
|
|
|
|
| |
C symbols.
Fixed #1155.
--
MOS_MIGRATED_REVID=120107746
|
|
|
|
|
|
|
|
|
|
|
| |
In RecursiveDirectoryTraversalFunction, we must tolerate
NoSuchPackageException being thrown by subdirectories' nodes, since
that can happen in a nokeep_going build.
--
Change-Id: Id9a48256aa209775f27130186c58e03c788d20a9
Reviewed-on: https://bazel-review.googlesource.com/#/c/3392/5
MOS_MIGRATED_REVID=120081575
|
|
|
|
|
|
|
|
|
| |
this by changing both the relevant Skyframe and the SkyQuery code to propagate (minimal!) blacklist information in the SkyKeys themselves.
There are other approaches to solving this problem, but I like how this solution doesn't involve duplication of logic. Also, it has the following nice benefit: previously, RecursiveDirectoryTraversalFunction would declare a dep on the blacklist for every directory traversed which adds an edge for each directory traversed.
--
MOS_MIGRATED_REVID=120049635
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119999213
|
|
|
|
|
|
|
|
|
|
|
| |
This allows a user to turn off png crunching during
the final merge (with crunch_png = 0), but it does
not skip nine-patch processing.
RELNOTES: adds crunch_png attribute to android_binary
--
MOS_MIGRATED_REVID=119986498
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119980586
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119960754
|
|
|
|
|
|
|
| |
c++ rule implementation backend and an OSX crosstool.
--
MOS_MIGRATED_REVID=119954578
|
|
|
|
|
|
|
|
|
|
|
|
| |
Optionally support a target width for the experimental state tracker;
if given, it will try to produce a status bar with lines shorter than
that limit, if possible, so that the status bar does not have to be
broken.
--
Change-Id: Ic5843285300ec10cf3e21b9b7402a6557f6bdb5e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3374
MOS_MIGRATED_REVID=119954289
|
|
|
|
|
|
|
|
|
|
| |
After this fix, we can run shell test, python test and cpp
test with msvc toolchain on Windows using bazel test command
--
Change-Id: I61e3984b6df2c4aef8762037a91a0f3a29d01691
Reviewed-on: https://bazel-review.googlesource.com/#/c/3385
MOS_MIGRATED_REVID=119950353
|
|
|
|
|
|
|
|
|
|
| |
...by only starting the new line, if needed and not already if the last
usable character of the line is written.
--
Change-Id: I86519389fe64fe74ba9045be07483ce5f55d5e9a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3384
MOS_MIGRATED_REVID=119949042
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This still has a number of issues, including, but not limited to:
- When switching between gRPC and AF_UNIX mode, you need to do a manual shutdown
- The console is spammed with "connection refused" messages on server startup
- When in gRPC mode, server also starts up an AF_UNIX server even though it's not necessary and concurrent requests probably make Bazel crash and burn
- I have no idea how concurrent gRPC requests are handled and now many threads gRPC creates
- Not tested except under Linux
- The request/response cookies are written in an odd format (negative bytes are not handled correctly). This is only a cosmetic issue, since the data content of the string is the same either way.
Can be tested with the --grpc_port=0 (or a valid port number) startup option.
--
MOS_MIGRATED_REVID=119948959
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When generating output targeted for a specific terminal width, it is
important to know the current position in order to appropriately shorten
the message still to be added to the current line. So make it possible to
add this functionality to the terminal writer itself, to avoid too many
lengthy position computations at call site.
--
Change-Id: I03400b9544c32567fc6ea7ab35e742c4ccd7b610
Reviewed-on: https://bazel-review.googlesource.com/#/c/3373
MOS_MIGRATED_REVID=119946982
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is important for packaging Python code in a way which is compatible
with the way Bazel builds its standard runfiles directory.
Refs #671
--
Change-Id: Ica2adab481cfecabb84b608cd952b0cae5a8653c
Reviewed-on: https://bazel-review.googlesource.com/#/c/2900/
MOS_MIGRATED_REVID=119945845
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119942803
|
|
|
|
|
|
|
|
|
| |
LabelVisitor is only used in BlazeQueryEnvironment#buildTransitiveClosure(), which takes care of this.
Very preliminary work for #1140.
--
MOS_MIGRATED_REVID=119933021
|
|
|
|
|
|
|
|
|
| |
The BlazeDirectories are also needed for loading the WORKSPACE file, so inject
them as part of preparePackageLoading rather than in createConfigurations,
which is too late.
--
MOS_MIGRATED_REVID=119931633
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old implementation cached the timestamp when the workspace status
action is created, which may be much earlier then the action gets
executed and end up leaving stale timestamp in volatile-status.
Close #1103
--
Change-Id: I0f09ac66681a134aeb10daf2455f3c3f98d8cd8f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3221/
MOS_MIGRATED_REVID=119930493
|