| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Explicitly close the PrintWriter before exiting, calling write(String) on an
auto-flushing PrintWriter doesn't flush the output.
--
MOS_MIGRATED_REVID=120473105
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
to actual instances.
This allows global namespaces registered in the RuleClassProvider to have structField SkylarkCallables.
TESTED: Using the new functionality for AppleSkylarkCommon.getKeys()
--
MOS_MIGRATED_REVID=120455804
|
|
|
|
|
|
|
|
|
| |
The [task / total] display when cloning a Git repository using the
git_repository rules isn't very helpful, especially since jgit doesn't update
totalTasks in a useful way.
--
MOS_MIGRATED_REVID=120450834
|
|
|
|
|
|
|
|
|
| |
This broke tools/cpp/test/... due to missing files. Unfortunately
those tests uses docker and until we can run docker in userland, we
cannot run those on Jenkins.
--
MOS_MIGRATED_REVID=120445118
|
|
|
|
|
|
|
|
| |
When java_binary.create_executable=0, omit the Main-Class entry in the deploy
jar's manifest instead of writing an empty main class name.
--
MOS_MIGRATED_REVID=120443936
|
|
|
|
|
|
|
| |
The TransitiveInfoProvider already contains a label, use that instead.
--
MOS_MIGRATED_REVID=120443298
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120442698
|
|
|
|
|
|
|
|
|
|
|
| |
In particular:
- Make a SIGINT to the server interrupt every command
- Parse negative numbers on the command line correctly (std::stoi throws an exception, and I'd rather not start using C++ exceptions)
- Use "bytes" for command line arguments instead of "string" in the client/server proto . This is more principled, although we pretend all arguments are strings all over the place and it works for "blaze run" mostly by accident.
--
MOS_MIGRATED_REVID=120434432
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120433463
|
|
|
|
|
|
|
| |
When collecting LIPO context, do not create module actions.
--
MOS_MIGRATED_REVID=120432142
|
|
|
|
|
|
|
|
| |
In this way, we avoid individual shards occassionally exceeding
the time limit for medium tests.
--
MOS_MIGRATED_REVID=120428952
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: 759bbfe
+ 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.
New features:
- --extra_entitlements allows passing additional entitlements for
iOS signing
- The output of -printconfiguration of proguard is available
through an implicit "[target_name]_proguard.confg" output of
android_binary (and
java_binary).
- Objective-C compiler information is now available to Skylark.
Important changes:
- ProGuard relies on bazel to check to see if the inputs have
changed.
- Build the jsonnet tool for the host when cross-compiling.
- Add ProductType for watch OS 1 extension and application.
- Restrict file types used for "entitlements" attribute to
[".entitlements", ".plist"]
- Restrict file types allowed for "strings" attribute to ".strings".
- local_repository can take a relative path.
- Support apple_watch1_extension and apple_watch_extension_binary
rules for creating watch OS 1 extensions.
- implement list.insert for skylark rule
- Enable overriding attributes for Rust binaries.
- ios_device attribute "xcode", for declaring a specific xcode to
use when selecting iOS simulators.
|
|
|
|
|
|
|
|
|
| |
- Actually make it work again (commit 00cfb7df61b1f3d9fac8ee29d92b315cbfe6d28f broke it, maybe I shouldn't send out changes in a hurry next time)
- Rename --grpc_port to --command_port (it's a bit better name)
- Do not send a kill signal to the server that can't be connected if we only connect to it to verify its presence
--
MOS_MIGRATED_REVID=120418784
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120418505
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120416303
|
|
|
|
|
|
|
|
| |
Once and for all, I tested it and re-tested should
be good.
--
MOS_MIGRATED_REVID=120381352
|
|
|
|
|
|
|
| |
Optimize .equals() by using the hashcode calculated in the constructor to determine if we can short-circuit equals and avoid traversing the parents if the two paths can't be equal.
--
MOS_MIGRATED_REVID=120363376
|
|
|
|
|
|
|
| |
Replacement will occur in a followup cl. New action uses the Gradle manifest merger through AndroidResourceProcessor.
--
MOS_MIGRATED_REVID=120359118
|
|
|
|
| |
MOS_MIGRATED_REVID=120353718
|
|
|
|
|
|
|
|
|
| |
This prevents an ugly error when the main repository name is set.
Fixes #1166.
--
MOS_MIGRATED_REVID=120352395
|
|
|
|
|
|
|
| |
standard annotations.
--
MOS_MIGRATED_REVID=120351013
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120349322
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120339643
|
|
|
|
|
|
|
| |
I properly tested it this time.
--
MOS_MIGRATED_REVID=120339101
|
|
|
|
|
|
|
| |
with the .gcno files for the actual .cc files.
--
MOS_MIGRATED_REVID=120338906
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The client provides information about whether the terminal is a tty, and
which width the output should be formatted for. Passing this information
as explicit command-line arguments has the disadvantage that it overrides
any setting in configuration files. While usually there is no one-size-fits-all
value for terminal width, it doesn't make sense either to have an option
where the user cannot set a default. Fix this by providing the client options
as least imported rc-source.
This is a roll-forward of commit 044adedc70de040475443e52eb1a3c692159790e
--
MOS_MIGRATED_REVID=120338148
|
|
|
|
|
|
|
| |
removing application_id, version_code and version_name attributes and switching to the Gradle manifest merger.
--
MOS_MIGRATED_REVID=120335565
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Along the path, fix the build for JDK 7 and get rid of
most ugliness in the JDK 7 build. Now simply setting
JAVA_VERSION to 1.7 will build a JDK 7 compatible version.
Fixes #1159.
--
Change-Id: I9599283844a57d9e053f12d37445907f22a9232e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3452
MOS_MIGRATED_REVID=120332747
|
|
|
|
|
|
|
|
| |
Otherwise, we have to clean it every time and it will affect the linking in
cc_configure.bzl
--
MOS_MIGRATED_REVID=120329223
|
|
|
|
|
|
|
| |
This test is now failing on ci.bazel.io
--
MOS_MIGRATED_REVID=120328587
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120325869
|
|
|
|
| |
Change-Id: Id46910de46264b5824793ba75439c31ae331718f
|
|
|
|
|
|
|
| |
--
Change-Id: I5377f694bd6dc426d41feef75cd35145c3b47c2f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3450/
MOS_MIGRATED_REVID=120323262
|
|
|
|
|
|
|
| |
This is apparently unused.
--
MOS_MIGRATED_REVID=120317405
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for retrieving
the default values of options.
The field defaultMultipleValue was introduced in commit 51a491b89a9cd5f15c9a093a5693bc37e696e6e1 to allow defining a
default value for options that set allowMultiple. However due to the limitations of
the optionsParser end up being not useful since we cannot guarantee that an option
that allows multiple has a converter that returns a list of values.
Thus this CL deletes code that may confuse even more and clarifies the mechanism
that the options currently use to obtain their default values.
--
MOS_MIGRATED_REVID=120317261
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120315714
|
|
|
|
|
|
|
| |
As noticed in #1122.
--
MOS_MIGRATED_REVID=120315240
|
|
|
|
|
|
|
| |
Fixes #1156.
--
MOS_MIGRATED_REVID=120312138
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120309611
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120282869
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
Adding AndroidDataSerializer, the serialize_format proto, and KeyValueConsumers (utility class for keeping consumers straight).
The serializtion is a bit more manual as previous experience has proven to me that simply writing all the resources into a proto map and pulling them out is not performant in the least. So, the serializer stores each message independent, the keys and then the values allowing for potential lazy loading and other optimizations in the future.
Also adds tests for parsing and writing style resources.
--
MOS_MIGRATED_REVID=120274904
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120262286
|