| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
reference to Constants.TOOLS_REPOSITORY
--
MOS_MIGRATED_REVID=120909538
|
|
|
|
|
|
|
| |
and produces a potentially multi-architecture binary, controlled by the --ios_multi_cpus flag
--
MOS_MIGRATED_REVID=120874805
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120865329
|
|
|
|
|
|
|
|
|
|
| |
* Adds a flag to Objective-C copts set.
* Adds a method to get Swift compilation flags, these are slightly different from ObjC clang.
RELNOTES:Generate debug symbols (-g) is enabled for all dbg builds of objc_ rules.
--
MOS_MIGRATED_REVID=120845678
|
|
|
|
|
|
|
| |
already have Label.EXTERNAL_PACKAGE_NAME.
--
MOS_MIGRATED_REVID=120828276
|
|
|
|
|
|
|
|
|
|
|
| |
The new behavior can be disabled by building with -c opt or
--nodevice_debug_entitlements.
RELNOTES: iOS apps are signed with get-task-allow=1 unless building with -c
opt.
--
MOS_MIGRATED_REVID=120827024
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NativeAspectClass.
This a large refactoring of the aspects, currently we have the following:
- AspectClasses: The interface AspectClass is a implemented by either
SkylarkAspectClass or NativeAspectClass<NativeAspectFactory>.
They are wrappers for the AspectFactories and they hold the information about
the Class<> of the factory.
- AspectFactories (FooAspect.java): Represented by the interfaces
ConfiguredAspectFactory and NativeAspectFactory, also by
the interface ConfiguredNativeAspectFactory which is the union of the two
aforementioned interfaces.
All aspects implement ConfiguredNativeAspectFactory except Skylark aspects
which implement only ConfiguredAspectFactory.
After this CL the distinction between NativeAspectFactories and NativeAspectClasses
dissappear, namely aspect that extends NativeAspectClass is considered native
and if it implements ConfiguredAspectFactory it is configured.
Therefore the interfaces NativeAspectFactory and ConfiguredNativeAspectFactory
both disappear.
With this refactoring the aspectFactoryMap in the ConfiguredRuleClassProvider
changes its type from (String -> Class<? extends NativeAspectClass>)
to (String -> NativeAspectClass) which means it is now able to have an instance
of the aspect instead of its Class only.
By doing this, it is now possible to pass parameters when creating an
aspect in the ConfiguredRuleClassProvider.
--
MOS_MIGRATED_REVID=120819647
|
|
|
|
|
|
|
|
|
| |
Constants.ANDROID_DEFAULT_SDK.
This CL also updates the test infrastructure to include a mock of @bazel_tools//tools/android:sdk.
--
MOS_MIGRATED_REVID=120815577
|
|
|
|
|
|
|
|
|
|
|
| |
Profiles with a root 'blaze-fdo' didn't get correctly symlinked to execRoot/_fdo in bazel.
TESTED=./compile.sh all; +manual FDO builds.
--
Change-Id: I5cd69970523db4de15d5b6ddf7af4a072bbca0f5
Reviewed-on: https://bazel-review.googlesource.com/#/c/3490/
MOS_MIGRATED_REVID=120811529
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2009!).
If a "blaze clean --expunge" was run concurrently with another command (that was waiting for the lock), it's possible that the clean command deletes the lock file, the new server starts up, then the JVM shutdown hooks delete the PID files from the *new* server.
There is still a slight possibility of a race condition if the lock is deleted then IOException occurs which prevents the BlazeShutdownException from being raised, but I'd rather not introduce another channel from command implementations to RPCServer to close that loophole.
This issue was triggered by commit 5a78166ee4edbd295f5d5fdb94785025285e764b, after which the PID files for the new server are written a bit more early, thus increasing the time window in which the race condition can happen.
--
MOS_MIGRATED_REVID=120805163
|
|
|
|
|
|
|
| |
--
Change-Id: I4c7cc2083cf0f886875b662440ed406e52dffae5
Reviewed-on: https://bazel-review.googlesource.com/#/c/3491/
MOS_MIGRATED_REVID=120804156
|
|
|
|
|
|
|
|
|
| |
new ones.
Add server.pid.txt that contains the same information in text form. ExecuteDaemon() on Windows will simply not write server.pid .
--
MOS_MIGRATED_REVID=120802055
|
|
|
|
|
|
|
| |
classes.
--
MOS_MIGRATED_REVID=120794657
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120708846
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
| |
I wonder why it was implemented like this in the first place. Unsurprisingly, it doesn't work on Windows.
--
MOS_MIGRATED_REVID=120682316
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Breaking up the runfiles tree change into some smaller changes this time around.
First step of rolling forward #848.
--
MOS_MIGRATED_REVID=120553288
|
|
|
|
|
|
|
|
|
|
|
| |
bind() is assumed to be able to provide any provider. This is suboptimal, but beats the alternative of traversing the dependency graph to an arbitrary depth.
The reason for the removal of the iteration ability in TransitiveInfoCollection is that now aspects can be attached to BindConfiguredTarget, too, which is not a RuleConfiguredTarget. Whereas I could have implemented the iterator, it was used only in BindConfiguredTarget anyway, so there didn't seem to be much reason to.
Some work towards #952.
--
MOS_MIGRATED_REVID=120549877
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120540937
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120539626
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120539216
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120538736
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 790d2f6009d47fe92cf0cd92a1473bbf0141f32e.
*** Reason for rollback ***
Broke non-Bazel projects on ci.bazel.io
Fixes #1168
*** Original change description ***
Move the runfiles for external repositories to under the x.runfiles/ directory
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....
***
--
MOS_MIGRATED_REVID=120535721
|
|
|
|
|
|
|
|
| |
The method will be removed in a subsequent change to facilitate reverting the
change in case it goes bad.
--
MOS_MIGRATED_REVID=120526894
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each android binary build operation will output a deploy info
proto providing information about how to deploy and launch the
APK. The information will vary between build mode (normal,
mobile-install, split-apk) and is configuration-dependent.
NO_SQ: Presubmit broken
--
MOS_MIGRATED_REVID=120494036
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120480051
|
|
|
|
|
|
|
| |
header modules as inputs.
--
MOS_MIGRATED_REVID=120473286
|
|
|
|
|
|
|
|
|
| |
If a target uses its launcher attribute to override --java_launcher, that
should also override the value of :java_launcher. The default value of
--java_launcher may not be compatible with the target architecture.
--
MOS_MIGRATED_REVID=120473209
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements most of a design proposal that splits constraint checking
into two pieces: *static* checks, which apply the standard constraint checking
done today, and *refined* checks, which selectively prune environments based
on select paths and check that not every environment gets pruned out.
As a result of this change, dependencies like:
java_library(
name = "lib",
restricted_to = [":A", ":B"],
deps = select({
":config_a": [":depA"],
":config_b": [":depB"],
}))
java_library(
name = "depA",
restricted_to = [":A"])
java_library(
name = "depB",
restricted_to = [":B"])
are allowed.
Specifically, even though neither "depA" nor "depB" supports [":A", ":B"], the combination of the two does. So the select as a whole supports all environments declared in lib, even though only one of those environments actually gets chosen for a given build.
Refinement makes lib "match" the chosen path. So for "config_a" builds, lib's environment set is "refined" down to [":A"], meaning [":B"]-restricted rules cannot depend on it. Likewise, for "config_b" builds, lib's environment set is "refined" down to [":B"], meaning [":A"]-restricted rules cannot depend on it. This guarantees that the restrictions imposed by the chosen select path propagate faithfully up the dependency chain.
See new documentation in ConstraintSemantics.java for more details.
--
MOS_MIGRATED_REVID=120464241
|