| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
There is no |lock_file| in GlobalVariables structure. Actually,
it was referring to |lockfile| variable.
--
Change-Id: Ic27bd4fad79c2e8b98ae8fa701d0b81fbdd98aa2
Reviewed-on: https://bazel-review.googlesource.com/#/c/3360/
MOS_MIGRATED_REVID=120792865
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120791766
|
|
|
|
|
|
|
| |
public Bazel tree.
--
MOS_MIGRATED_REVID=120787331
|
|
|
|
|
|
|
|
|
| |
Prefer Writer to OutputStream to reduce the number of char/byte conversions,
and pass in a Writer for the persistent worker entry point instead of
redirecting stdout and stderr.
--
MOS_MIGRATED_REVID=120771072
|
|
|
|
|
|
|
|
|
|
| |
responsibility of the caller to invoke, instead of creating the fully linked artifact by default
It makes more sense for the caller rule to opt-in to creating its own implicit output.
This also makes it easier for classes to use CompilationSupport without generating this artifact.
--
MOS_MIGRATED_REVID=120764517
|
|
|
|
|
|
|
| |
with an ObjcProtoAspect which propagates the proto provider through the dependency chain.
--
MOS_MIGRATED_REVID=120747710
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120742339
|
|
|
|
|
|
|
| |
list of strict deps keys from being propagated more than one level in the dependency graph. Values added to those keys from dependency providers are routed into the non_propagated_items map, preventing them from being propagated again.
--
MOS_MIGRATED_REVID=120724767
|
|
|
|
|
|
|
|
|
| |
This is required to fully fix #611.
--
Change-Id: Iffeab2a80a02f2e1208637fe85195d0c2862e637
Reviewed-on: https://bazel-review.googlesource.com/#/c/3492
MOS_MIGRATED_REVID=120724036
|
|
|
|
|
|
|
| |
Except in action execution logic (ActionExecutionFunction, SkyframeActionExecutor, etc.), switch Action interface references to either ActionAnalysisMetadata if possible or ActionExecutionMetadata.
--
MOS_MIGRATED_REVID=120723431
|
|
|
|
|
|
|
|
|
| |
The major piece of #848.
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.
--
MOS_MIGRATED_REVID=120722312
|
|
|
|
|
|
|
| |
mechanism to add build variables through the CcLibraryHelper API.
--
MOS_MIGRATED_REVID=120710713
|
|
|
|
|
|
|
|
|
| |
Fixes #1187.
--
Change-Id: I36e87d86926a38785dcd98c841db826c518cc575
Reviewed-on: https://bazel-review.googlesource.com/3463
MOS_MIGRATED_REVID=120710112
|
|
|
|
|
|
|
| |
This is so that they can be implemented properly for Windows. For now, though, they are left in blaze_util.cc since the Windows implementations aren't there yet.
--
MOS_MIGRATED_REVID=120709884
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120708846
|
|
|
|
|
|
|
| |
Fixes #1126.
--
MOS_MIGRATED_REVID=120707955
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the android rules work if the workspace name is set.
See https://github.com/bazelbuild/bazel/wiki/Updating-the-runfiles-tree-structure
for more details.
This is required for rolling forward https://github.com/bazelbuild/bazel/issues/848.
--
MOS_MIGRATED_REVID=120705755
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120704733
|
|
|
|
|
|
|
|
|
| |
Also fixed a small bug
--
Change-Id: I22fa16272587471b9652f3b7f7d9cb1341fc6524
Reviewed-on: https://bazel-review.googlesource.com/#/c/3464
MOS_MIGRATED_REVID=120703703
|
|
|
|
|
|
|
|
|
| |
When a file changes its execution root (for example, a previously checked in
file now becoming a generated file), the cache key would be the same, using
a broken module map.
--
MOS_MIGRATED_REVID=120703120
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120702105
|
|
|
|
|
|
|
| |
Fixes #1183.
--
MOS_MIGRATED_REVID=120701344
|
|
|
|
|
|
|
| |
requirements. Uses this mechanism to configure c/c++ compilation and linking for darwin execution from the crosstool.
--
MOS_MIGRATED_REVID=120701108
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120699557
|
|
|
|
|
|
|
| |
server down due to differing startup options.
--
MOS_MIGRATED_REVID=120697380
|
|
|
|
|
|
|
| |
This is just a minor fix because when this call happens, the other thread is not running yet, but better be safe than sorry.
--
MOS_MIGRATED_REVID=120695754
|
|
|
|
|
|
| |
Add the jars in preparation of using the new version.
Change-Id: I5e81f9c30ad0897d69ba7d2a42ff28b07aad9c9a
|
|
|
|
|
|
|
| |
Helps with #1182.
--
MOS_MIGRATED_REVID=120695171
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120695090
|
|
|
|
|
|
|
| |
This is because OsUtils.getpid() cannot work under msys2 since java.exe is not an msys2 binary. We might make it work by including JNI code, but the current plan is to go without JNI on Windows.
--
MOS_MIGRATED_REVID=120694746
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120690977
|
|
|
|
|
|
|
| |
This is necessary because on Windows/msys2, the Java gRPC server listens only on IPv6 but the C++ client only tries to connect over IPv4, resulting in breakage.
--
MOS_MIGRATED_REVID=120689437
|
|
|
|
|
|
|
| |
0dbe07f017d391aba0613b4e6ca1503b62382ccd
--
MOS_MIGRATED_REVID=120687334
|
|
|
|
|
|
|
|
|
|
|
| |
In particular, do not own a lock while waiting for another
thread---especially not the update thread that might be waiting
for the very lock were holding.
--
Change-Id: I46aef3585b712e25cd4317004eacd8b48557a341
Reviewed-on: https://bazel-review.googlesource.com/#/c/3462
MOS_MIGRATED_REVID=120686232
|
|
|
|
|
|
|
| |
Helps with #1182.
--
MOS_MIGRATED_REVID=120686181
|
|
|
|
|
|
|
|
|
|
| |
Instead of default SDK version, use currently installed one.
Fixes #1184.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1186
MOS_MIGRATED_REVID=120685979
|
|
|
|
|
|
|
| |
I wonder why it was implemented like this in the first place. Unsurprisingly, it doesn't work on Windows.
--
MOS_MIGRATED_REVID=120682316
|
|
|
|
|
|
|
|
| |
This is consistent with JavaBuilder. Some actions (e.g. resource compilations)
don't set these flags.
--
MOS_MIGRATED_REVID=120590777
|
|
|
|
|
|
|
| |
Adding --extra_entitlements flag to a build triggers a merge of entitlements files using plmerge tool. Configure build rules to output the resulting plist file in the XML format. Bundles signed with entitlements in the binary format fail to load on device.
--
MOS_MIGRATED_REVID=120588271
|
|
|
|
|
|
|
|
| |
This isn't hooked up to anything yet, but is another piece of getting #848
rolled forward.
--
MOS_MIGRATED_REVID=120582973
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: 759bbfe
Cherry picks:
+ 1250fda: Rollback of commit
351475627b9e94e5afdf472cbf465f49c433a25e.
+ ba8700e: Correctly set up build variables for the correct pic
mode for fake_binary rules.
+ 386f242: Automated [] rollback of commit
525fa71b0d6f096e9bfb180f688a4418c4974eb4.
+ 97e5ab0: Fix cc_configure include path for Frameworks on OS X.
+ a20352e: cc_configure: always add -B/usr/bin to the list of gcc
option
+ 0b26f44: cc_configure: Add piii to the list of supported
cpu_value
+ 3e4e416: cc_configure: uses which on the CC environment variable
+ aa3dbd3: cc_configure.bzl: strip end of line when looking for
the cpu
+ 810d60a: cc_configure: Add -B to compiler flag too
Patch release, only includes fixes to C++ auto-configuration.
|
|
|
|
|
|
|
|
|
| |
On some target platform gcc invokes external tools during compilation, see #1152. Also support absolute path when looking for gcc.
This needs to be cherry-picked to fix #1177.
--
MOS_MIGRATED_REVID=120581887
|
|
|
|
|
|
|
|
| |
* Adds a swift_library rule that produces a (.a, .swiftmodule) pair. It can handle dependencies between modules and can be used as a dependency of objc_binary.
* Does not work with Objective-C yet.
--
MOS_MIGRATED_REVID=120578875
|
|
|
|
|
|
|
|
| |
I was confused about the bulleted list on 0.2.2, so I figured it
would be nice tell people what the commit list is.
--
MOS_MIGRATED_REVID=120577721
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120574676
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120567604
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
incorrectly not being parsed as "//:blah").
Also add tests for parsing absolute labels in the empty package.
The empty package has been a thing in Bazel for a while now.
Note that the old error message in this case "couldn't determine target for filename 'blah'" was almost always misleading and unhelpful since we were (almost certainly incorrectly) assuming the user intended for 'blah' to be an input file in the empty package. Now the error message would be "no such target '//:blah'") which is similarly misleading and unhelpful but probably marginally less so. If we desire to improve this, a future cleanup can introduce smarter error messages.
--
MOS_MIGRATED_REVID=120566819
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 2ad804cef42f: ("Fixed bugs blocking bazel shell test on Windows"),
updated the documentation in blaze_util.cc but forgot to update
the same doc comment in the header file.
To prevent this from happening again, this copies the added sentence
to the header file and deletes the documentation from the source file.
--
Change-Id: I240b3a31d7b457ef4d50558f1ca54619666b8d2c
Reviewed-on: https://bazel-review.googlesource.com/#/c/3470
MOS_MIGRATED_REVID=120561630
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120558192
|
|
|
|
|
|
|
|
|
|
| |
Fixes #806.
RELNOTES: External repository correctness fix: adding a new file/directory as a
child of a new_local_repository is now noticed.
--
MOS_MIGRATED_REVID=120557511
|