| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
Also some apple binary test cleanup along the way.
--
PiperOrigin-RevId: 145123804
MOS_MIGRATED_REVID=145123804
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145122327
MOS_MIGRATED_REVID=145122327
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145119990
MOS_MIGRATED_REVID=145119990
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145091484
MOS_MIGRATED_REVID=145091484
|
|
|
|
|
|
|
|
| |
with the internal GenRule implementation.
--
PiperOrigin-RevId: 145087704
MOS_MIGRATED_REVID=145087704
|
|
|
|
|
|
|
|
|
| |
The code has been untouched and unused for over a year (it's very likely
broken) and we have other priorities for now.
--
PiperOrigin-RevId: 145087310
MOS_MIGRATED_REVID=145087310
|
|
|
|
|
|
|
|
| |
ExecutionInfoProvider.
--
PiperOrigin-RevId: 145084927
MOS_MIGRATED_REVID=145084927
|
|
|
|
|
|
|
|
|
| |
This functionality is never used, have never been exposed to Skylark
and is a continuous pain to maintain and test.
--
PiperOrigin-RevId: 145079832
MOS_MIGRATED_REVID=145079832
|
|
|
|
|
|
|
|
|
|
| |
Specifying both options can cause OOM on OSX.
--
Change-Id: I52daf194a8840f9e63f1d537f13152e53f8436a7
Reviewed-on: https://cr.bazel.build/8220
PiperOrigin-RevId: 145079331
MOS_MIGRATED_REVID=145079331
|
|
|
|
|
|
|
|
|
|
| |
This seems like an obvious cleanup, and I also want to move most of the
test-specific environment setup to TestRunnerAction, which is simpler after
this change.
--
PiperOrigin-RevId: 145076829
MOS_MIGRATED_REVID=145076829
|
|
|
|
|
|
|
|
|
|
|
| |
For example, on FreeBSD, ${PREFIX}/bin/python is a symlink
to the correct python version.
--
Change-Id: Iae79caae8d98530a6d8656b1915a8d5de9c132ea
Reviewed-on: https://cr.bazel.build/8396
PiperOrigin-RevId: 145068920
MOS_MIGRATED_REVID=145068920
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Unwrapping JavaCompilationArgsProvider from JavaProvider when collecting compile time dependencies artifacts (in addition to JavaCompilationArgsProvider), so that java_library could depend on Skylark rules that return java_common.provider. (this makes java sandwich complete \o/)
* Added a new param (source_files) to java_common.compile to allow compilation of source files in addition to source jars.
* Added a new sourceFiles field to JavaLibraryHelper in order to pass them to JavaCompilationHelper.
* Added a new method (java_common.default_javac_opts) for default Java compilation.
* Added a test for a basic java sandwich.
--
PiperOrigin-RevId: 145064700
MOS_MIGRATED_REVID=145064700
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not intended to be a user-visible semantic change, aside from error messages.
This is to help avoid unintentional flattening of depsets, and to narrow down the number of call sites where this can occur, to help us print warning/deprecation messages.
EvalUtils#toIterable will now return an ImmutableList in place of SkylarkNestedSet. This should be ok since the caller shouldn't be relying on the result being a Skylark-safe type. Code that takes Iterable because it accepts either a list or set, can instead be changed to take Object and use EvalUtils#toIterableStrict for validation.
Note that NestedSet still implements Iterable, so native code can still easily and accidentally flatten sets.
--
PiperOrigin-RevId: 145044023
MOS_MIGRATED_REVID=145044023
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145030082
MOS_MIGRATED_REVID=145030082
|
|
|
|
|
|
|
|
| |
the AppleCrosstoolTransition.
--
PiperOrigin-RevId: 145006581
MOS_MIGRATED_REVID=145006581
|
|
|
|
|
|
|
|
|
|
| |
The old names are deprecated but still supported for now. A flag for enforcing the deprecation will come in a later change.
RELNOTES[INC]: The traversal orders for depsets have been renamed. The old names are deprecated and will be removed in the future. New names: "stable" -> "default", "compile" -> "postorder", "link" -> "topological", "naive_link" -> "preorder".
--
PiperOrigin-RevId: 145004718
MOS_MIGRATED_REVID=145004718
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144992642
MOS_MIGRATED_REVID=144992642
|
|
|
|
|
|
|
|
|
|
|
| |
As pointed out in the new review comments on commit df726eae7b6ef11df3b962d720df36f63d5cd3a3, the
SpawnAction members did not need to be changed from private to
protected, they just needed to be accessed via accessor methods
in the derived LTOBackendAction class.
--
PiperOrigin-RevId: 144989490
MOS_MIGRATED_REVID=144989490
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144983864
MOS_MIGRATED_REVID=144983864
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144965845
MOS_MIGRATED_REVID=144965845
|
|
|
|
|
|
|
|
|
|
|
| |
This digest make sure that we produce a different RepositoryDirectoryValue
for different marker data, thus invalidating the node.
--
Change-Id: Ibc6286c76de7a8d07ece2bb8125bfb75095f7784
Reviewed-on: https://cr.bazel.build/8136
PiperOrigin-RevId: 144948233
MOS_MIGRATED_REVID=144948233
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144890965
MOS_MIGRATED_REVID=144890965
|
|
|
|
|
|
|
|
|
| |
This matters when the same rule (or other exportable) is bound to multiple
variables, since the identifier of the first variable will become its name.
--
PiperOrigin-RevId: 144881310
MOS_MIGRATED_REVID=144881310
|
|
|
|
|
|
|
|
| |
* This allows xcrunwrapper to set the correct SDKROOT when building darwin targets.
--
PiperOrigin-RevId: 144874291
MOS_MIGRATED_REVID=144874291
|
|
|
|
|
|
|
|
|
|
| |
--experimental_objc_library and --experimental_objc_use_crosstool_for_binary.
This flag will allow testing of the complete (compilation and linking) rollout
of the objc crosstool.
--
PiperOrigin-RevId: 144864301
MOS_MIGRATED_REVID=144864301
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the code below was first written, the default value for @Option cpu was null. This value was then overwritten with whatever target_cpu got loaded from the CROSSTOOL, which became the basis for all code queries of the value "cpu".
This behavior was deprecated some months ago after the default @Option cpu was changed to auto-read from the host machine. So the CROSSTOOL "override" no longer ever happens.
Also made the relevant test more hermetic.
--
PiperOrigin-RevId: 144850329
MOS_MIGRATED_REVID=144850329
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144849686
MOS_MIGRATED_REVID=144849686
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel-created files (like log files of test runs) are internally reported
as Paths. However, this is not always the most useful representation of the
location of that artifact for a consumer of build events. Therefore, support
a mapping of paths to more useful URIs.
--
PiperOrigin-RevId: 144843525
MOS_MIGRATED_REVID=144843525
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144841772
MOS_MIGRATED_REVID=144841772
|
|
|
|
|
| |
PiperOrigin-RevId: 144839489
MOS_MIGRATED_REVID=144839489
|
|
|
|
|
|
|
|
| |
strict_proto_deps, then strictness is enforced.
--
PiperOrigin-RevId: 144836042
MOS_MIGRATED_REVID=144836042
|
|
|
|
|
|
|
|
|
|
| |
This interface is part of the module API, and this makes more sense than the
previous per-file API, IMO, and is more future proof, even if there's no
immediate benefit to the change.
--
PiperOrigin-RevId: 144827566
MOS_MIGRATED_REVID=144827566
|
|
|
|
|
|
|
|
|
|
| |
config1.equals(c2).
This fixes an obscure bug between dynamic configurations, host configuration caching, and Skyframe skyKey interning that makes Bazel crash under certain sequences of builds. See changes for details.
--
PiperOrigin-RevId: 144766296
MOS_MIGRATED_REVID=144766296
|
|
|
|
|
|
|
|
| |
ObjcProvider subtrees
--
PiperOrigin-RevId: 144747299
MOS_MIGRATED_REVID=144747299
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144741831
MOS_MIGRATED_REVID=144741831
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144739068
MOS_MIGRATED_REVID=144739068
|
|
|
|
|
|
|
|
|
|
| |
The attribute overrides the value of --java_header_compilation so we can enable
it by default without breaking platforms that don't support it (currently only
JDK 7 Bazel).
--
PiperOrigin-RevId: 144737908
MOS_MIGRATED_REVID=144737908
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144733615
MOS_MIGRATED_REVID=144733615
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This add a markerData map to the RepositoryFunction#fetch function so RepositoryFunction-s
can declare extraneous data to add to the marker file. The RepositoryFunction#verifyMarkerData
is called to verify those data in order to know if the repository is up to date
and need re-fetching.
Design doc: https://bazel.build/designs/2016/10/18/repository-invalidation.html [step 2]
--
Change-Id: I9083fb72a0142f418a7296f889cd3eaf32e92498
Reviewed-on: https://cr.bazel.build/7973
PiperOrigin-RevId: 144728497
MOS_MIGRATED_REVID=144728497
|
|
|
|
|
|
|
|
|
|
|
| |
This cl exposes param files that were hard-coded before. This enables more
precise placement on the link command line.
This is a roll-forward of commit db7a9ea7f6b2af3c4c1f43ad4aa50cd4eca02921
--
PiperOrigin-RevId: 144708270
MOS_MIGRATED_REVID=144708270
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]:
Tuples that end with a trailing comma must now be inside parens,
e.g. (1,) instead of 1,
--
PiperOrigin-RevId: 144690953
MOS_MIGRATED_REVID=144690953
|
|
|
|
|
|
|
|
| |
It is just a specification yet, it does nothing.
--
PiperOrigin-RevId: 144687428
MOS_MIGRATED_REVID=144687428
|
|
|
|
|
|
|
|
|
|
|
| |
The mobile_install command has a hard dependency on the Android rules. For
mu-Bazel, we're trying to build a minimally useful Bazel binary, and that
should not contain the Android rules. Moving the mobile install command
implementation to a separate package is one step towards that.
--
PiperOrigin-RevId: 144680452
MOS_MIGRATED_REVID=144680452
|
|
|
|
|
|
|
|
|
| |
These rules can be used to configure JDKs, as an alternative to
the filegroups and filegroups-of-filegroups used currently.
--
PiperOrigin-RevId: 144655277
MOS_MIGRATED_REVID=144655277
|
|
|
|
|
|
|
|
|
|
| |
Resolves #2363
RELNOTES: Remove support for --javawarn; use e.g. --javacopt=-Xlint:all instead
--
PiperOrigin-RevId: 144652008
MOS_MIGRATED_REVID=144652008
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the argv (including argv[0]).
This is necessary because Bazel 0.4.3 can have $ in its output base (fixed in commit b64349e91debe8abb8a218c6e8888dc9b42fdea3), and if that happens, built Java binaries won't be executable because bash will understand that as a variable to be interpolated.
laszlocsomor says that the quoting is otherwise alright. I'm not sure what happens with other special characters (e.g. @!{}%#'"), but at least we don't put those in the output base ourselves.
See: https://github.com/bazelbuild/bazel/issues/2306 .
--
PiperOrigin-RevId: 144640441
MOS_MIGRATED_REVID=144640441
|
|
|
|
|
|
|
|
| |
when it's reached through a :java_toolchain attribute.
--
PiperOrigin-RevId: 144638966
MOS_MIGRATED_REVID=144638966
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cmd_helper is deprecated and planned for deletion.
RELNOTES[INC]:
Removed the cmd_helper.template function.
The function was equivalent to:
def template(items, template):
return [template.format(path = i.path, short_path = i.short_path)
for i in items]
--
PiperOrigin-RevId: 144628429
MOS_MIGRATED_REVID=144628429
|
|
|
|
|
|
|
|
| |
Fixes #2286.
--
PiperOrigin-RevId: 144627152
MOS_MIGRATED_REVID=144627152
|
|
|
|
|
|
|
|
|
| |
implementation has never been fully complete and it turns out that this isn't
necessary. We can re-add if it becomes useful at some point.
--
PiperOrigin-RevId: 144618513
MOS_MIGRATED_REVID=144618513
|