| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 202483718
|
|
|
|
|
|
|
| |
Closes #5478.
Change-Id: I3ac44605ef16a7c2e6bdc63d26fdf968bef651aa
PiperOrigin-RevId: 202482493
|
|
|
|
|
|
|
|
| |
Make ObjcRuleClasses uses CppRuleClasses.ccToolchainAttribute label resolver.
Mark CppRuleClasses.ccToolchainAttribute with @AutoCodec annotation.
RELNOTES:none
PiperOrigin-RevId: 202479836
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an implementation of the design at
https://docs.google.com/document/d/1g91BWJITcYw_X-VxsDC0VgUn5E9g0kRBGoBSpoO41gA/edit>.
More thorough documentation will be sent in a separate cl. The api was approved
at
https://docs.google.com/document/d/1M8JA7kzZnWpLZ3WEX9rp6k2u_nlwE8smsHYgVTSSJ9k/edit?ts=5b292400#.
Work towards #4571 (only the docs are missing).
RELNOTES: None.
PiperOrigin-RevId: 202464331
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
fix forward
*** Original change description ***
PiperOrigin-RevId: 202441346
|
|
|
|
| |
PiperOrigin-RevId: 202400312
|
|
|
|
| |
PiperOrigin-RevId: 202389874
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202386363
|
|
|
|
|
|
|
|
|
| |
This is a much cleaner, more elegant approach than previous regex matching.
This still leaves room for unknown-name rule definitions, in case, for example, a user namespaces their rule definition not at the top level.
For example: "foo.bar = rule(...)"
RELNOTES: None.
PiperOrigin-RevId: 202380975
|
|
|
|
|
|
| |
FeatureConfiguration.
PiperOrigin-RevId: 202363333
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202360925
|
|
|
|
|
|
|
|
|
|
| |
If there are multiple modules with the same name:
- If only one is marked 'documented', that one takes precedence.
- If one is a subclass of the others, the subclass takes precedence.
- Otherwise, an exception is thrown.
RELNOTES: None.
PiperOrigin-RevId: 202359443
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202325860
|
|
|
|
|
|
| |
unless necessary.
PiperOrigin-RevId: 202317115
|
|
|
|
| |
PiperOrigin-RevId: 202311773
|
|
|
|
|
|
|
|
|
| |
The Skylark constructor of CcCompilationInfo now accepts headers. This may be
the last piece needed to get a working prototype of foreign C++ libraries. Next
step would be open sourcing the sandwich.
RELNOTES:none
PiperOrigin-RevId: 202306252
|
| |
|
| |
|
|
|
|
|
|
|
| |
of DefaultInfo() was used.
RELNOTES: None.
PiperOrigin-RevId: 202192091
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This skydoc rewrite uses an actual skylark interpreter with a faked build API (implementing the actual build API that Bazel uses).
There's a lot left to do here, this is a barebones start.
For example, this does not yet handle:
- load() statements
- non-global build API elements (e.g. apple_common)
- output of any rule information other than attribute names
- markdown output format
RELNOTES: None.
PiperOrigin-RevId: 202187207
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202167782
|
|
|
|
|
|
|
|
| |
Logger messages aren't printed to the console, they're written to /usr/local/google/tmp, and can be prohibitively large for these debug server logs.
Instead I'm going with your original suggestion in https://github.com/bazelbuild/bazel/commit/b74922932b25a71c626b47ea9a9afb7dbc506cec, and selectively suppressing debug events by wrapping the EventHandler on the way in to SkylarkDebugServer.
PiperOrigin-RevId: 202166571
|
|
|
|
|
|
|
|
|
| |
Consolidate the creation of JavaCompilationArgsProviders, and avoid explicit
handling of the 'direct' and 'recursive' cases in clients. Also add some
higher-level methods to the builder API to support adding dependencies
with dep/export/runtime_dep-like semantics.
PiperOrigin-RevId: 202166383
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202162804
|
|
|
|
|
|
|
|
|
| |
CppCompileAction.discoverInputsStage2 retrieves values of discovered modules
from ActionExecutionValue.
This addresses a possible a correctness issue.
PiperOrigin-RevId: 202162180
|
|
|
|
| |
PiperOrigin-RevId: 202151257
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202150316
|
|
|
|
|
|
|
| |
This was never used. We thought it will be useful, but it's not.
RELNOTES: None.
PiperOrigin-RevId: 202143524
|
|
|
|
|
|
|
| |
Makes it non-instantiable so that it's easier to migrate SWIG rules to Skylark.
RELNOTES:none
PiperOrigin-RevId: 202136054
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also handle statements in conditional breakpoints.
This is more consistent with other common debuggers (e.g. java, python).
Calls Parser#parseStatement with local parsing level, so some statement types aren't handled (e.g. load statements), which is broadly consistent with other debuggers.
Assignment, augmented assignment, and return statements return a non-None value,
and simple expression statements still return the result of evaluating the expression.
TAG_CHANGE_OK=This proto has never yet been used
TYPE_CHANGE_OK=This proto has never yet been used
PiperOrigin-RevId: 202135678
|
|
|
|
|
|
|
| |
they are used on the phone.
RELNOTES: None.
PiperOrigin-RevId: 202117007
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, Bazel expected that it can compile whatever appeared in cc_library.srcs
directory artifacts. That is true for C/C++ source files, and for headers when
the C++ toolchain supported header parsing/processing (which used
CppCompileAction). When the toolchain doesn't support header parsing/processing,
Bazel would crash.
Addresses issue #5092. One part of it.
Fixes #5372.
RELNOTES: None.
PiperOrigin-RevId: 202114286
|
|
|
|
|
|
|
|
|
| |
To get a CcCompilationInfo instance from Skylark it will either have to be
through its constructor (not yet fully implemented) which will not schedule any
actions or through a call to compile() which does schedule actions.
RELNOTES:none
PiperOrigin-RevId: 202099841
|
|
|
|
| |
PiperOrigin-RevId: 202092962
|
|
|
|
| |
PiperOrigin-RevId: 202023187
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202015490
|
|
|
|
|
|
|
| |
interfaces.
RELNOTES: None.
PiperOrigin-RevId: 201972439
|
|
|
|
| |
PiperOrigin-RevId: 201969238
|
|
|
|
|
|
|
|
| |
I should have left it as it was -- doing it client-side is just too
slow.
ENUM_VALUE_OK=This proto has never yet been used
PiperOrigin-RevId: 201957138
|
|
|
|
|
|
|
| |
interfaces.
RELNOTES: None.
PiperOrigin-RevId: 201956915
|
|
|
|
|
|
|
|
|
|
| |
I will remove the CcLinkParamsStore class in a separate CL. For now, make sure
the API doesn't expose this class.
The only Skylark use was in cc_import which is migrated in this CL.
RELNOTES:none
PiperOrigin-RevId: 201948058
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 201748802
|
|
|
|
|
| |
Change-Id: I355b138e143771fd826ab03951df821ea7d58ac5
PiperOrigin-RevId: 201740564
|
|
|
|
|
|
|
| |
interfaces.
RELNOTES: None.
PiperOrigin-RevId: 201735466
|
|
|
|
| |
PiperOrigin-RevId: 201723154
|
|
|
|
|
|
|
| |
label methods that don't explicitly pass a repository mapping.
RELNOTES: None
PiperOrigin-RevId: 201717665
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
see b/109887056
*** Original change description ***
Stop objc_proto_library from returning the generated sources.
PiperOrigin-RevId: 201709908
|
|
|
|
|
|
| |
ArtifactResolverSupplier in SkyframeExecutor.
PiperOrigin-RevId: 201705857
|
|
|
|
|
|
|
|
|
|
|
| |
Like with providers, consumers get a merged view of all actions from the merged configured target (all other aspects + the base target).
I had to rejig the aspect value / configured aspect to be symmetric with rule configured targets.
I do not expect significant memory bloat from this. All lists / maps already existed, only extra fields have been added.
RELNOTES: Expose aspect actions provider to Skylark.
PiperOrigin-RevId: 201697923
|
|
|
|
|
|
|
|
| |
RELNOTES: None
*** Reason for rollback ***
PiperOrigin-RevId: 201686843
|