| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Since we no longer release the Bazel version without an embedded JDK.
RELNOTES: None
PiperOrigin-RevId: 205356986
|
|
|
|
|
|
| |
generation action, track all the sources that will be generated by the proto generator.
PiperOrigin-RevId: 205309842
|
| |
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 205288166
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 205281433
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Working towards #4570.
RELNOTES:none
PiperOrigin-RevId: 205274676
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previous behavior was to put flags coming from Bazel option --linkopt into
legacy_link_flags. They should be in user_link_flags instead (together with
flags coming from linkopts rule attribute). This cl introduces
--experimental_linkopts_in_user_link_flags option that flips the behavior.
There is another incompatible change. Previously cc_common.create_link_variables() included flags from --linkopt, with the flag flipped it doesn't anymore. I believe
--linkopt flags shouldn't be there by default because:
* We don't tie the API with the specifics of C++ rules/options, enabling theoretical use with other languages (objc)
* Users are free to use ctx.fragments.cpp to access C++ options and add them explicitly (https://github.com/bazelbuild/bazel/issues/5602)
* New behavior maintains the symmetry with --copt and user_compile_flags
RELNOTES: None.
PiperOrigin-RevId: 205274272
|
|/
|
|
|
|
| |
Expose methods to enable shrinking resources via aapt2 proto.
Change-Id: I2379c81ea3573ac2314f0d3e8d638b53028f7949
|
|
|
|
|
|
|
| |
type.
RELNOTES: None.
PiperOrigin-RevId: 205237848
|
|
|
|
| |
PiperOrigin-RevId: 205236169
|
|
|
|
|
|
|
| |
Also add an execution requirement that allows disabling reporting to the CLI;
this will be used in a future change.
PiperOrigin-RevId: 205216096
|
|
|
|
|
|
|
|
|
| |
being executed if the action requires input discovery. Input discovery might
actually change the action's command line, which in turn can become part of the
file being written.
RELNOTES: None.
PiperOrigin-RevId: 205207109
|
|
|
|
|
|
|
| |
...mentioning that a drop-in replacement can be loaded from @bazel_tools.
Change-Id: I0197d65359664e6fed84dc1fe5d5b6ddad48520e
PiperOrigin-RevId: 205204800
|
|
|
|
|
|
| |
encountered in a Fileset as a regular file.
PiperOrigin-RevId: 205152271
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
AndroidSdkInfo is already being used by the Flutter rules.
*** Original change description ***
Expose AndroidSdkProvider to Skylark (as AndroidSdkInfo).
RELNOTES: None.
PiperOrigin-RevId: 205142459
|
|
|
|
|
| |
RELNOTES: Fixed compatibility with aar_import when using aapt2. AAPT2 is now supported for Android app builds without resource shrinking. To use it, pass the `--android_aapt=aapt2` flag or define android_binary.aapt_version=aapt2.
PiperOrigin-RevId: 205136160
|
|
|
|
|
|
| |
Also replaced ```` with ``` in other document where it didn't cause a visible change.
PiperOrigin-RevId: 205112255
|
|
|
|
|
| |
RELNOTES: none.
PiperOrigin-RevId: 205100703
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 205079775
|
|
|
|
|
|
|
|
| |
FilesetEntryMap for the aspect's RuleContext.
The current logic in createFilesetEntryMap() uses the rule of the RuleContext.Builder to determine whether to create a filesetEntryMap or not, because of this, applying an aspect to a generated file of a fileset (e.g. 'out' attribute of a Fileset) causes createFilesetEntryMap to create the map even though the associated target is, for instance, a generated file. As a consequence, applying any aspect to a generated file of a fileset causes a NullPointerException.
PiperOrigin-RevId: 205065778
|
|
|
|
|
| |
RELNOTES: Add aquery command to get analysis time information about the action graph.
PiperOrigin-RevId: 205064145
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 205060182
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The C++ Skylark API is protected by a flag and whitelist. The flag's value
should be true by default for non-Bazel. This is set with an invocation policy. In
Bazel the default value is false. When this was checked in I couldn't find a
way to use the default value in the host configuration, so when checking the
flag we ignored the value for these cases.
In this CL we copy the target config value to the host config.
RELNOTES:none
PiperOrigin-RevId: 205059612
|
|
|
|
|
|
|
|
|
|
| |
`True` instead of `None`.
dict has a get() method that defaults to `None`.
Checking for a key in the dictionary with get() will always return `None` in the given example. Using `True` is better.
RELNOTES: None.
PiperOrigin-RevId: 205052981
|
|
|
|
| |
PiperOrigin-RevId: 205047383
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 205046100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow the `$TMPDIR` to be empty in
//src/test/shell/bazel:bazel_rules_test.
This used to be the case before commit
https://github.com/bazelbuild/bazel/commit/f814454ff5477418ca44696efb5c71339368efa4
Bazel only guarantees to set TMPDIR for locally
executed tests, but not (to my knowledge) for
remote execution.
Fixes https://github.com/bazelbuild/bazel/issues/5607
Change-Id: I2e97c13d137f94c7f668b7a6c7fc5020a19e4a0b
Closes #5610.
Change-Id: I2e97c13d137f94c7f668b7a6c7fc5020a19e4a0b
PiperOrigin-RevId: 205039105
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MSVC does not have `ssize_t` type. MSVC does have `off_t`, but is defined as 32-bit `long` due to legacy reason, this will prevent us from handling large file.
Changing `off_t` and `ssize_t` to C standard `ptrdiff_t` for portability and consistency.
Changing one instance of `S_ISDIR(st.st_mode)` to `(st.st_mode & S_IFDIR) == S_IFDIR` as MSVC does not have `S_ISDIR` macro.
/cc @laszlocsomor
Closes #5538.
PiperOrigin-RevId: 205038203
|
|
|
|
|
|
|
|
|
| |
Instead of copying files found in a cache hit, support adding
a hard link. This should save disk space if the same files from
cache are used in many workspaces. Fixes #5568.
Change-Id: Ie8192f9669d8420283e18e0813f3160a515ba8fe
PiperOrigin-RevId: 205034815
|
|
|
|
|
| |
RELNOTES: none.
PiperOrigin-RevId: 205032841
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Full NDK changelog](https://github.com/android-ndk/ndk/wiki/Changelog-r17)
Changes related to Bazel's NDK toolchain/CROSSTOOL generation:
- Removed support for targeting mips, mips64, armeabi.
- Bumped bundled clang version to 6.0.2.
- The default STL is now libc++. If Bazel detects that r17 is being used, it
aliases `@androidndk//:default_toolchain` to `@androidndk//:toolchain-libcpp`,
instead of `@androidndk//:toolchain-gnu-libstdcpp`.
- Removed tests that build against armeabi, mips, mips64.
- Stop passing `-fno-integrated-as` into the compiler by default.
TODO:
- [x] Java tests
- [x] ~Support for wrap.sh to use with ASANs~ Implementing in follow up PR.
- [ ] Fix or disable remote caching with android_ndk_integration_test https://github.com/bazelbuild/bazel/issues/4663
Fixes https://github.com/bazelbuild/bazel/issues/4742
RELNOTES: Added support for Android NDK r17. The default STL is now `libc++`, and support for targeting `mips`, `mips64` and `ARMv5` (`armeabi`) has been removed.
Closes #5371.
Change-Id: Id1ded004c3a80ea62f307746dc3ad6f633f2df2e
PiperOrigin-RevId: 205013758
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 205011761
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Still bugs lurking. See linked bug.
*** Original change description ***
Automated rollback of commit eb587075b0d6ffab1cf9e69ede1b7e547905e547.
*** Reason for rollback ***
Depot has been fixed.
RELNOTES[INC]: If the same artifact is generated by two distinct but identical actions, and a downstream action has both those actions' outputs in its inputs, the artifact will now appear twice in the downstream action's inputs. If this causes problems in Skylark actions, you can use the uniquify=True argument in Args.add_args.
PiperOrigin-RevId: 204997569
|
|
|
|
|
| |
Change-Id: Ib1a29a927fa6fd3f49e03efa3b73e1547df6cacd
PiperOrigin-RevId: 204993474
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 202658759, which does
not correctly propagate Clang error codes.
PiperOrigin-RevId: 204991287
Notes:
The commit message should begin "This reverts commit
f24958a11e3a54f563429aadc12bce033be047fa ...".
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 204983634
|
|
|
|
|
| |
RELNOTES: none.
PiperOrigin-RevId: 204976789
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 204974291
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 204969740
|
|
|
|
|
| |
Change-Id: I13645199a21991b1458264f9d9ac2db2736066b2
PiperOrigin-RevId: 204963740
|
|
|
|
|
|
|
|
| |
idempotency.
RELNOTES: None.
PiperOrigin-RevId: 204957400
|
|
|
|
|
| |
Change-Id: I2195a3f7d60e9835bc00d6f151ea91271fdccf6f
PiperOrigin-RevId: 204954233
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 204953629
|
|
|
|
|
|
|
|
|
|
| |
The cpusupport code uses functions like dlopen, dlclose that
require linking with libdl. Adding that library to the
linkopts makes cpusupport self-contained.
Closes #5559.
PiperOrigin-RevId: 204948982
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 204948309
|
|
|
|
|
|
|
|
| |
Also, fix a few NPEs this apparently exposes by having android_test and
android_binary mobile_install explicitly specify merged resources.
RELNOTES: none
PiperOrigin-RevId: 204933164
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 204927047
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cl adds following flags:
* --experimental_disable_legacy_cc_compilation_api
* --experimental_disable_legacy_cc_linking_api
* --experimental_disable_linking_mode_flags
* --experimental_disable_compilation_mode_flags
* --experimental_disable_legacy_crosstool_fields
RELNOTES: None
PiperOrigin-RevId: 204924599
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add instructions for community maintained packages.
Ref : Github issue #5332
@jin Is this how you want it?
Closes #5582.
PiperOrigin-RevId: 204919383
|