| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
All options need to explicitly list their category and effect. If they are uncategorized, this makes the lack of information obvious. Remove defaults from the annotation to enforce this.
Also enforce the sanity check that no option should have UNKNOWN or NO_OP effects listed with other effect tags.
Includes some last default sets for options I missed in the previous mass-setting change, and some that were added since.
PiperOrigin-RevId: 160641861
|
|
|
|
|
|
|
|
| |
* move Compile requirement and instructions to the "compile from source" page
* remove warning for old versions of Bazel
RELNOTES: None
PiperOrigin-RevId: 160641070
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Dynamically Configured Resource Filtering change 1/6
To enable dynamically configured resource filtering, we'll need to be able to
pass filtered resources into resource processing code used by android_library
targets. The resource parsing action, used only in android_library targets,
takes the LocalResourceContainer as an input, unlike android_binary processing
code which never used it directly.
Abstract the code for actually building the collection of resource roots out of the withResources method, and create an additional method for calling it from resource filtering.
Also, split some common test code out of ResourceFilterTestBase to make a ResourceTestBase class for testing changes to this (and eventually, other) resource-oriented classes, and create LocalResourceContainerTest for this class in particular.
RELNOTES: none
PiperOrigin-RevId: 160640192
|
|
|
|
|
|
|
| |
It's now easier to customize Printer if in different situations objects should
be printed differently. Also its API is cleaner now. Names of methods of SkylarkValue objects now reflect names of Skylark functions: SkylarkValue#repr and SkylarkPrintableValue#str.
PiperOrigin-RevId: 160635154
|
|
|
|
|
|
|
|
|
|
| |
The genrule //src:derived_java_srcs so far assumed to find the
needed tool jar(1) on PATH. This, however, is not true in all
setups. Instead, use jar from JAVABASE, which should be the correct
toolchain to be used on the execution platform. Fixes #3284.
Change-Id: I1f972f819786b511237c448a6c57484a76f4118b
PiperOrigin-RevId: 160634222
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cl promotes //tools/osx/crosstool to be fully specified on its own, without
any blaze patches needed. While at it, I (think I) unified objc and c++ coverage
features. Other than coverage, this cl only adds features that bazel would add
otherwise.
Ping #2420
RELNOTES: ObjC and C++ coverage feature is unified under name 'coverage'
PiperOrigin-RevId: 160633192
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160630261
|
|
|
|
|
|
|
| |
Fixes fallout from https://github.com/bazelbuild/bazel/commit/fda985b069ed4cc1966a6ced5743c396f91ac688.
RELNOTES: none
PiperOrigin-RevId: 160626838
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160621674
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160619371
|
|
|
|
|
|
|
|
| |
retry strategy may need tuning.
Other behavior changes: swallowing gRPC CANCELLED errors when the thread is interrupted, as these are expected and just make debugging difficult. Also, distinguishing between the gRPC DEADLINE_EXCEEDED caused by the actual command timing out on the server vs. other causes (the former should not be retriable, while the latter should retry).
TESTED=unit tests, remote worker on Bazel
PiperOrigin-RevId: 160605830
|
|
|
|
|
|
|
| |
Chunker.Builder in my next change, so all the from factory methods are removed.
TESTED=unit test
PiperOrigin-RevId: 160594730
|
|
|
|
|
|
| |
Automated formatting fixes standardize the @Option annotation.
PiperOrigin-RevId: 160582653
|
|
|
|
|
|
|
| |
With a few manual fixes for readability.
RELNOTES: None.
PiperOrigin-RevId: 160582556
|
|
|
|
|
|
|
|
|
| |
--experimental_use_absolute_paths_for_actions.
These flags are old and unused -- with the deletion of xcodegen, addition of Tulsi, and near-migration to crosstool objc compilation, these flags are long-deprecated and are now cleaned up.
RELNOTES: None.
PiperOrigin-RevId: 160578161
|
|
|
|
|
|
|
|
| |
desugaring Long.compare(long, long) is only enabled if either --min_sdk_version
< 19 or --rewrite_calls_to_long_compare is specified.
RELNOTES: set --rewrite_calls_to_long_compare to false by default.
PiperOrigin-RevId: 160578028
|
|
|
|
|
|
| |
Automated formatting fixes standardize the @Option annotation.
PiperOrigin-RevId: 160567787
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160566592
|
|
|
|
|
|
| |
The previous implementation stores a copy of the param file's path fragment with an '@' prepended. This can add up if you have a lot of params files, but can be avoided by deferring that string expansion.
PiperOrigin-RevId: 160559793
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160553181
|
|
|
|
|
|
|
|
| |
By default it just delegates to the existing #writeOutputFile, but implementations may choose to override if they have easy access to a ByteString.
Also change some DeterministicWriter implementations that do have easy access to the ByteString.
PiperOrigin-RevId: 160550028
|
|
|
|
|
|
|
|
| |
Additionally, add a warning note for developers who wish to delete startup
options: they first need to deprecate the flag and once it's a no-op
for a sufficient amount of time then they can delete it from the list
of valid options.
PiperOrigin-RevId: 160546248
|
|
|
|
|
|
|
|
| |
contents.
This change was verified with a local build.
PiperOrigin-RevId: 160533900
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce host and target path separation in the
Android incremental_install.py. This will allow
running this script (and use bazel mobile-install)
on platforms with non-POSIX path semantics
(e.g. Windows).
See https://github.com/bazelbuild/bazel/issues/3264
Change-Id: If6ec09f100dd2e0be3389dce25cb1a13305226e9
PiperOrigin-RevId: 160531950
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3292
Change-Id: I67db893c36067b950303d2b131b925dce974d7d1
PiperOrigin-RevId: 160529960
|
|
|
|
|
|
|
|
|
|
| |
Add a test for the java_binary launcher script.
Later we can add similar test cases for py_binary
and sh_binary, especially after we fix them to
create a .cmd file on Windows.
Change-Id: Ida9b613a5908020218ce0565e33d9cd048adb022
PiperOrigin-RevId: 160529644
|
|
|
|
|
|
|
|
| |
testing.
Unlike in the production flags, these flags are only used for internal testing. Tagged them as NO_OP instead of the default UNKNOWN to make it clear that we do not need these to become properly tagged.
PiperOrigin-RevId: 160526472
|
|
|
|
|
|
|
|
|
| |
When computing completion options, bazel has to be called. For those
calls, discard the progress output (on stderr) to avoid them messing
up the terminial. Fixes #2279.
Change-Id: Ic1536058a44dac687ad59042ec56af50a4125f3b
PiperOrigin-RevId: 160525601
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160516183
|
|
|
|
|
|
|
|
| |
This is a step forward to having the same semantics for java_library and custom Skylark rules that use java_common.compile, facilitating the migration from native Java rules to Skylark.
Progress on #2614
PiperOrigin-RevId: 160513771
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160510979
|
|
|
|
|
|
|
| |
A workaround for https://github.com/bazelbuild/bazel/issues/3273
RELNOTES: None
PiperOrigin-RevId: 160509802
|
|
|
|
| |
PiperOrigin-RevId: 160506627
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes to test_base.py:
- use tempfile.TemporaryFile to create Bazel's
stdout/stderr files
- added a new RunProgram method
- setUp now creates a unique temp directory for
each test case
Change-Id: I5b851fee826e73044fa3992a5981855982527ae3
PiperOrigin-RevId: 160505154
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160504704
|
|
|
|
|
|
|
|
| |
Fix the failure at
http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/PLATFORM_NAME=windows-msvc-x86_64/1620/console
RELNOTES: None.
PiperOrigin-RevId: 160504102
|
|
|
|
|
|
|
|
|
| |
Issue #3265 went unnoticed for a long time, till it was fixed as
a sideeffect of d1c5329ba622b29afd3ab9f670fa17064d493bc0. To avoid
that happing in the future, add a test. Closes #3265.
Change-Id: Ie22a1d4a2f09fd3dcadcbd900795b3e12b7dc461
PiperOrigin-RevId: 160502516
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160498120
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160482939
|
|
|
|
|
|
|
|
|
|
| |
resource_extractor has nothing to do with the Android SDK. Once upon a time, it
was needed for jack support, so it was colocated with the jack attributes in
android_sdk. Nowadays, it is used as a necessary step before singlejar can run
to build the APK.
RELNOTES: None
PiperOrigin-RevId: 160479247
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 160467549
|
|
|
|
|
|
|
|
|
|
|
| |
This rule works with the android_instrumentation, android_device_script_fixture and android_host_service_fixture rules to support testing Android applications.
None of these rules are installed yet, because the forthcoming Android test runner is not yet open sourced.
https://github.com/bazelbuild/bazel/issues/903.
RELNOTES: None
PiperOrigin-RevId: 160465920
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 160461708
|
|
|
|
|
|
|
|
|
|
| |
A common need is to limit access to a rule or feature - restricting
a feature which is being deprecated or controlling the rollout of a new
feature. This change adds the feature_control_policy flag, which allows
developers to easily manage this process.
RELNOTES: None.
PiperOrigin-RevId: 160454166
|
|
|
|
|
|
|
| |
then we use pop2 to pop the value out of the stack.
RELNOTES: None
PiperOrigin-RevId: 160453904
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 160445869
|
|
|
|
|
|
|
| |
parity with the cc_ rules.
RELNOTES:None.
PiperOrigin-RevId: 160438691
|
|
|
|
|
|
|
|
|
| |
*) Changed the GenerateRobolectricResourceSymbolsAction to merge duplicate namespaces from the dependency list input.
*) RClassGenerator throws if an existing R.class file exists for that package.
*) New test for duplicate package dependencies
RELNOTES: none
PiperOrigin-RevId: 160436937
|
|
|
|
| |
PiperOrigin-RevId: 160427360
|
|
|
|
|
|
|
|
|
| |
The correct dependency is on @bazel_tools//tools/objc:header_scanner, and this is determined by configuration value.
I have manually verified this fixes https://github.com/bazelbuild/bazel/issues/2723 . Ultimately we will want to follow up and write a regression test for rdeps functioning, but that is significantly harder than this quick fix.
RELNOTES: None.
PiperOrigin-RevId: 160424016
|