| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cl introduces new action_config type for Crosstool named 'generic'. This
can be used to set the value of CC_FLAGS make variable using much more
expressive mechanism (action_configs + features) than previous make_variable
Crosstool messages. This has been requested by the C++ LPT.
However, as FeatureConfiguration needs RuleContext, CC_FLAGS cannot be
computed using configuration only anymore. Also, FeatureConfiguration is C++
rules specific class, and Bazel build-base cannot depend on it. Therefore we
cannot use FeatureConfiguration for ExtraActions, for example. Because it cannot
be made perfect, this cl is not updating all the possible places that expand
make variables but limits the scope to:
* genrule (the only widely used rule that often expands make variables)
* *_test (CC_FLAGS is used by Tensorflow in the 'args' attribute)
* cc_rules (people sometimes set 'copts' to something like:
"-DCC_STRING=\\\"$(CC)\\\" -DCC_FLAGS_STRING=\"$(CC_FLAGS)\""
The long term plan is to use Skylark C++ API to get C++ command lines, so
CC_FLAGS together with this inconsistent solution will be removed.
RELNOTES: CC_FLAGS can be defined using 'generic' action_config in CROSSTOOL
PiperOrigin-RevId: 157202883
|
|
|
|
|
|
|
| |
The previous copt was in error, and was not caught due to only causing warnings to be omitted. Tests are now updated to throw an error in such cases of warning.
RELNOTES: None.
PiperOrigin-RevId: 157150798
|
|
|
|
|
|
|
| |
This will allow custom rules to interact more fully with the platform system.
Change-Id: I22dd2efab55b1c6e6129b1ba99fb5f0aa9c2d6b2
PiperOrigin-RevId: 157145828
|
|
|
|
|
|
| |
Actual fix for #2819.
PiperOrigin-RevId: 157142420
|
|
|
|
|
|
|
| |
from global .blazerc in unknown commit
RELNOTES: n/a
PiperOrigin-RevId: 157133716
|
|
|
|
|
| |
RELNOTES: Skylark support (apple_common.dotted_version(string)) for building DottedVersion objects to interface with native apple rules
PiperOrigin-RevId: 157131109
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 157124371
|
|
|
|
|
| |
Change-Id: I0604355801bd7e4f77a93bfc38e970713a1392c5
PiperOrigin-RevId: 157116222
|
|
|
|
|
|
| |
This implicit output is similar to objc_library's fully linked static library. For j2objc_library targets, we can use this output to trigger transpilation and generate a fully linked static library.
PiperOrigin-RevId: 157062831
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fix.
*** Original change description ***
Automated g4 rollback of commit c78c947e6a8cbb323304f872a3dcabb989a3d76b.
*** Reason for rollback ***
Breaks android targets in the nightly - see []
*** Original change description ***
Do not retain transitive data in AndroidLocalTestBase...
***
ROLLBACK_OF=156745610
RELNOTES: None
PiperOrigin-RevId: 157028029
|
|
|
|
|
|
|
| |
configuration
RELNOTES: None.
PiperOrigin-RevId: 157017608
|
|
|
|
|
| |
RELNOTES: add one-version enforcement to android_local_test
PiperOrigin-RevId: 157014802
|
|
|
|
|
|
|
| |
Part of #2219.
Change-Id: I39ced1f3e2605154771df9424d6ed2f971820baf
PiperOrigin-RevId: 157002268
|
|
|
|
|
|
| |
already done, we should leave the thread in an interrupted state and proceed. This fixes a blaze crash when a 'genquery' execution is interrupted at the right time.
PiperOrigin-RevId: 157000269
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if the user has an SDK/NDK that is missing required directories, we
print out an InconsistentFileSystemException. This CL will give a better error,
indicating which directory is missing (or is not a directory).
Implementation is roughly taken from NewLocalRepositoryFunction.
Followup to https://github.com/bazelbuild/bazel/issues/2739.
RELNOTES: None
PiperOrigin-RevId: 156913532
|
|
|
|
|
|
|
| |
The documentation for the current iteration of this feature is under android_sdk_repository.
RELNOTES: None
PiperOrigin-RevId: 156909364
|
|
|
|
|
|
|
| |
SkylarkType.Simple.
Change-Id: I7d6898bcba1689fee9e730b6134b659948501dae
PiperOrigin-RevId: 156903849
|
|
|
|
| |
PiperOrigin-RevId: 156896360
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward of directory name change
*** Original change description ***
Automated g4 rollback of commit 1d9e1ac90197b1d3d7b137ba3c1ada67bb9ba31b.
*** Reason for rollback ***
Breaks //src/test/shell/integration:force_delete_output_test
*** Original change description ***
Symlink output directories to the correct directory name
If the workspace directory is /path/to/my/proj and the name in the WORKSPACE
file is "floop", this will symlink the output directories to
output_base/execroot/floop instead of output_base/execroot/proj.
More prep for #1262, fixes #1681.
PiperOrigin-RevId: 156892980
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156876531
|
|
|
|
|
|
| |
Progress on #904.
PiperOrigin-RevId: 156862823
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an option allowing to set a hard limit on the number of characters
bazel will write to stdout/stderr (combined). In this way, it can be
avoided to overwhelm the user with information (especially, if the
invocation of bazel is wrapped in some way). Once the limit is approaching,
bazel will try hard to meaningfully reduce the output, but will ultimately
resort to just dropping output completely.
Change-Id: I49cce96cc6a025c9753632dd489021766df81077
PiperOrigin-RevId: 156849105
|
|
|
|
|
|
|
|
| |
While the fact that they are only added temporarily is obvious
from the comment, a machine-readable deprecation annotation is
more likely to be honored. So add it.
PiperOrigin-RevId: 156846712
|
|
|
|
|
|
|
| |
the same value.
RELNOTES: None.
PiperOrigin-RevId: 156837699
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156827893
|
|
|
|
|
| |
RELNOTES: Using $(CC_FLAGS) in a GenRule adds a dependency to the c++ toolchain
PiperOrigin-RevId: 156770639
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156770067
|
|
|
|
|
|
|
| |
the default has been switched to "android".
RELNOTES: The 'legacy' Android manifest merger is deprecated. Please upgrade to the 'android' manifest merger, which is the same merger used by Gradle. https://developer.android.com/studio/build/manifest-merge.html
PiperOrigin-RevId: 156765307
|
|
|
|
|
|
| |
@loader_path/Frameworks rpath flag to the linker.
PiperOrigin-RevId: 156759162
|
|
|
|
|
|
|
|
|
|
| |
For compiles that the CppConfiguration flags as needing PIC, the -fPIC
option needs to be added after the other compile options so that it cannot
be overridden (e.g. with a --copt). This is consistent with the way the
CppCompileAction compile options are ordered.
RELNOTES: None.
PiperOrigin-RevId: 156746218
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks android targets in the nightly - see []
*** Original change description ***
Do not retain transitive data in AndroidLocalTestBase.
The argument strings and artifacts were both transitive and flattened, causing O(N^2) memory consumption.
PiperOrigin-RevId: 156745610
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
java_library.exports and java_import.runtime_deps|exports|deps will now
accept any label from a rule that has a JavaProvider declared provider.
Note that java_library.deps|runtime_deps already had this feature and
this simply extends that privilege.
This relies on the fact that both those targets (via JavaCommon) are
simply searching for jars via JavaProvider anyway.
Added test for passing a custom Skylark rule (that provides a
JavaProvider) can successfully be added to the deps, runtime_deps, and
exports of java_library, java_import, and java_binary (where
appropriate).
Added integration tests for java_library.exports|runtime_deps (the basic
sandwich already tests deps) and java_import.exports|runtime_deps.
Note that custom Skylark rules are still unable to provide or propagate
a JavaNativeLibraryProvider, which results from a cc dependency. Also,
the deps argument for java_import is somewhat odd.
Change-Id: I7b2c19c6b99516ce524e8c82193d0c73e2d66530
PiperOrigin-RevId: 156740729
|
|
|
|
|
|
|
| |
separate method. This is so that android_local_test won't need access to the AndroidConfiguration fragment.
RELNOTES: None
PiperOrigin-RevId: 156740056
|
|
|
|
|
|
| |
If a target appeared in 2 different attributes, it is not processed twice, even if different aspects were applied to the different attributes. In that case, only one of the aspects is applied. This commit fixes this by checking which aspects have been applied to the target, instead of checking if the target was already processed.
PiperOrigin-RevId: 156738275
|
|
|
|
|
|
|
|
| |
And while at it cleanup all the calls of CppHelper.getToolchain and
CppHelper.getFdoSupport.
RELNOTES: None.
PiperOrigin-RevId: 156716291
|
|
|
|
|
|
|
|
|
| |
using multiple threads.
The immediate upside is that if multiple packages load the same bzl file, that file will only be read once when using loadPackages().
RELNOTES: None
PiperOrigin-RevId: 156621988
|
|
|
|
| |
PiperOrigin-RevId: 156589908
|
|
|
|
|
|
|
|
| |
In both Python 2 and Python 3, the operator // is used for int division.
With Python 3, operator / is for float division.
RELNOTES: None.
PiperOrigin-RevId: 156582262
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156578239
|
|
|
|
| |
PiperOrigin-RevId: 156571671
|
|
|
|
|
|
| |
RELNOTES: Flag --explicit_jre_deps is now a noop.
PiperOrigin-RevId: 156570342
|
|
|
|
| |
PiperOrigin-RevId: 156558693
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the command line flags used by remote execution/caching as well as the
build event service (BES).
Major changes:
- Remote execution/caching and BES share flags for authentication and TLS.
- Removed API Key authentication from BES, as it's not being used.
- Add TLS support to BES upload.
- Add --bes_project_id flag. If set, the value is propagated as part of BES
lifecycle events.
For reviewers:
Start your review at CommonRemoteAndBesOptions, BuildEventServiceOptions and
RemoteOptions. The other changes are mostly automatic IDE renames of fields and
flag updates in shell script tests.
RELNOTES: None.
PiperOrigin-RevId: 156553857
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156553687
|
|
|
|
|
|
|
|
|
|
|
| |
This rule specifies a host binary that is run as part of an android_instrumentation_test. It merely collects options, support APKs and the runfiles for the host binary and passes them along to the upcoming android_instrumentation_test rule.
Note that this CL does _not_ install the rule, so this CL does not make it usable by anyone. Once the other android testing rules are ready, we will install them all.
One small step towards https://github.com/bazelbuild/bazel/issues/903.
RELNOTES: None
PiperOrigin-RevId: 156553198
|
|
|
|
|
|
|
| |
This value is unlikely to change in the near future, and we don't feel comfortable exposing it. You can force the size to be whatever you want, so the default value isn't really relevant.
RELNOTES: n/a
PiperOrigin-RevId: 156543600
|
|
|
|
|
|
|
| |
This avoids some string unnecessary string operations,
and keeps command lines below the per-arg limit.
PiperOrigin-RevId: 156514047
|
|
|
|
|
|
|
| |
hardcoded default of 100 isn't a good choice for all PackageLoader users.
RELNOTES: None
PiperOrigin-RevId: 156468439
|
|
|
|
|
|
|
|
| |
This doesn't really expose new information, because one can iterate over the existing getTargets() and recreate the map.
Moreover, the map is immutable, so there's no risk in returning it to the user.
RELNOTES: None
PiperOrigin-RevId: 156349797
|
|
|
|
|
|
|
|
| |
Also expose both sides to Skylark.
Part of #2219.
Change-Id: I4d749dd9981fe33f75310acb0ec3927cff6f28fe
PiperOrigin-RevId: 156340638
|