| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skylark implicit output callbacks could use any nonconfigurable
attribute of the rule except for "name". (As an implementation detail,
"name" is easy to overlook because it's a special case in rule
attribute map.) In practice, this isn't too much of a problem because
the return value of a skylark implicit output callback has %{}
substitutions applied to it, which do allow the rule name. However, it
is weird and inconsistent to prevent implicit output callbacks from
using the name.
--
Change-Id: I13149b2e9689ef8b8056c612a29df9da32e39bf3
Reviewed-on: https://cr.bazel.build/8251
PiperOrigin-RevId: 146178693
MOS_MIGRATED_REVID=146178693
|
|
|
|
|
|
|
|
|
| |
Aside from making error messaging clearer, this stops Bazel from
crashing on select({None: ...}) (a pretty anti-social error message).
--
PiperOrigin-RevId: 146173043
MOS_MIGRATED_REVID=146173043
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146169742
MOS_MIGRATED_REVID=146169742
|
|
|
|
|
|
|
|
| |
dependencies used in last build
--
PiperOrigin-RevId: 146169454
MOS_MIGRATED_REVID=146169454
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146162705
MOS_MIGRATED_REVID=146162705
|
|
|
|
|
|
|
|
| |
order.
--
PiperOrigin-RevId: 146159313
MOS_MIGRATED_REVID=146159313
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146150539
MOS_MIGRATED_REVID=146150539
|
|
|
|
|
|
|
|
| |
use_testrunner=0
--
PiperOrigin-RevId: 146150454
MOS_MIGRATED_REVID=146150454
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146143641
MOS_MIGRATED_REVID=146143641
|
|
|
|
|
|
|
|
|
| |
Corresponding JavaBuilder change:
https://github.com/bazelbuild/bazel/blo[]fa9b24cb7b1e516f92a200d9087fd3ba561e5/src/java_tools/buildjar/java/com/google/devtools/build/buildjar/JavaLibraryBuildRequest.java#L302
--
PiperOrigin-RevId: 146143519
MOS_MIGRATED_REVID=146143519
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146142811
MOS_MIGRATED_REVID=146142811
|
|
|
|
|
| |
PiperOrigin-RevId: 146138214
MOS_MIGRATED_REVID=146138214
|
|
|
|
|
|
|
|
| |
issues.
--
PiperOrigin-RevId: 146127950
MOS_MIGRATED_REVID=146127950
|
|
|
|
|
|
|
|
| |
Gradle version in that it removes values resources instead of only minifying them.
--
PiperOrigin-RevId: 146124871
MOS_MIGRATED_REVID=146124871
|
|
|
|
|
|
|
|
| |
--
Change-Id: I8c6d5cdbe9e2fc19ca6a626bea26944efa36e4db
Reviewed-on: https://cr.bazel.build/8550
PiperOrigin-RevId: 146120078
MOS_MIGRATED_REVID=146120078
|
|
|
|
|
|
|
|
| |
implementation for integration tests.
--
PiperOrigin-RevId: 146114082
MOS_MIGRATED_REVID=146114082
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove getSpawnInfo and asShellCommand, which are never really
overridden in a useful way. asShellCommand moves to the Spawns class,
and getSpawnInfo is only ever called by SpawnAction, and the
implementation moves there.
I'm considering using Spawn as the general lower-level abstraction for both
local and remote execution. It sort of is that already, except it's not
used consistently - we often pass a tuple of (args, env) plus possibly
input and output files through parameter-heavy method call hierarchies
instead of using this existing abstraction.
However, I'm concerned about the amount of baggage it's carrying as well
as the number of implementations for what is supposed to be a simple
interface (or possibly even a simple value class), and this is an attempt
to slim it down a bit.
This should have no visible effects on builds.
--
PiperOrigin-RevId: 146109838
MOS_MIGRATED_REVID=146109838
|
|
|
|
|
|
|
|
| |
be a saner name.
--
PiperOrigin-RevId: 146109129
MOS_MIGRATED_REVID=146109129
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward commit bbfa9fa5ad1dd66ecedcb136a4ff3d0f8d397b9b with fix
*** Original change description ***
Automated [] rollback of commit bbfa9fa5ad1dd66ecedcb136a4ff3d0f8d397b9b.
*** Reason for rollback ***
Wrong submit with unresolved issues
*** Original change description ***
Java template windows performance
Address issue #2426
Closes #2427.
--
PiperOrigin-RevId: 146108597
MOS_MIGRATED_REVID=146108597
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bazel build //src:bazel --cpu=x64_windows_msvc
now succeeds, hooray!
This change adds empty implementations for
build-runfiles and process-wrapper to make that
possible.
This means we can now build a bazel binary that
doesn't depend on MSYS.
The resulting binary is not yet functional because
many methods are still to be implemented, and they
just write "TODO: implement" or something similar.
But still this is great news, because now we can
add compile tests to the CI for MSVC!
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 146106178
MOS_MIGRATED_REVID=146106178
|
|
|
|
|
|
|
|
|
|
| |
Action#getInputsWhenSkippingInputDiscovery().
This has the side effect of always allowing new inputs to be discovered when Action#discoversInputs() return true, but since those actions are very few and have mostly to do with C++, I think it's an acceptable tradeoff for th ecode being that much simpler.
--
PiperOrigin-RevId: 146098150
MOS_MIGRATED_REVID=146098150
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a missing method definition to (and delete two
dead ones from) file_windows.cc, so we can now
build it with --cpu=x64_windows_msvc.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 146095459
MOS_MIGRATED_REVID=146095459
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a list of known issues (currently only on
Windows) when trying to build from source.
Also update the Windows run/compile requirements.
Motivated by:
https://github.com/bazelbuild/bazel/issues/2431
https://github.com/bazelbuild/bazel/issues/2449
--
PiperOrigin-RevId: 146091804
MOS_MIGRATED_REVID=146091804
|
|
|
|
|
|
|
|
|
| |
Move the functionality for building resources jars out of JavaBuilder, in
preparation for building resource jars as a separate action.
--
PiperOrigin-RevId: 146086774
MOS_MIGRATED_REVID=146086774
|
|
|
|
|
|
|
|
|
| |
This was a work-around for a javac bug, and is unnecessary now that
we're setting locations using the API.
--
PiperOrigin-RevId: 146079935
MOS_MIGRATED_REVID=146079935
|
|
|
|
|
|
|
|
| |
is a symlink. That may indicate that it points to the input manifest, and so comparing the manifests in this case would be useless.
--
PiperOrigin-RevId: 146048132
MOS_MIGRATED_REVID=146048132
|
|
|
|
|
|
|
|
|
|
| |
--android_resource_shrinking and --experimental_android_resource_shrinking as separate flags that affect the same behavior, instead of utilizing the 'oldName' feature of Options.
RELNOTES:
--
PiperOrigin-RevId: 146024304
MOS_MIGRATED_REVID=146024304
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this change:
(1) add a sanity check to verify that GNU bintools
are on the PATH
(2) correct the PATH on Windows if (1) failed
(3) use "<user>/My Documents/Temp" as the default
temp directory instead of "%windir%/Temp", because
the latter is non-writable
Motivated by:
https://github.com/bazelbuild/bazel/issues/2431
https://github.com/bazelbuild/bazel/issues/2449
--
PiperOrigin-RevId: 146006796
MOS_MIGRATED_REVID=146006796
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146005461
MOS_MIGRATED_REVID=146005461
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As more package options are added, it's confusing that the
debian package is generated in scripts/package/BUILD, but
scripts/package/debian/ contains the related files (and isn't
itself a Bazel package). This change makes the file locations
more predictable, and also makes it easier to see what
is happening in scripts/packages.
--
Change-Id: Id8c445fc164a1a4aa09c52559a5143578cfdea88
Reviewed-on: https://cr.bazel.build/8510
PiperOrigin-RevId: 146003934
MOS_MIGRATED_REVID=146003934
|
|
|
|
|
|
|
|
|
|
| |
dynamic ruleclass
transitions.
--
PiperOrigin-RevId: 146000375
MOS_MIGRATED_REVID=146000375
|
|
|
|
|
|
|
|
| |
--apple_crosstool_transition), the APPLE_CROSSTOOL distinguisher does not modify output directory.
--
PiperOrigin-RevId: 145999133
MOS_MIGRATED_REVID=145999133
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]:
Depsets (former sets) are converted to strings as "depset(...)" instead of
"set(...)".
--
PiperOrigin-RevId: 145990995
MOS_MIGRATED_REVID=145990995
|
|
|
|
|
|
|
|
|
|
| |
Skylark equivalent (from '$attr' and ':attr' to '_attr').
This CL eliminates duplicate code and makes sure that attribute names in SkylarkClassObjects are properly translated.
--
PiperOrigin-RevId: 145986380
MOS_MIGRATED_REVID=145986380
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows joining paths on "\" instead of "/"
when building for Windows.
See https://github.com/bazelbuild/bazel/issues/2107
--
Change-Id: I417ba40af6530650be2394db4bd445f0883d40e5
Reviewed-on: https://cr.bazel.build/8495
PiperOrigin-RevId: 145961689
MOS_MIGRATED_REVID=145961689
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Set $TMP to $TEST_TMPDIR, so that the
CaptureStderr can safely call SetTempPathA and not
get C:\Windows\ back as a result, which is
unfortunately read-only.
See https://github.com/bazelbuild/bazel/issues/2107
--
Change-Id: If63cb028f677d9a0d9597f83afc9e08f2e5d2529
Reviewed-on: https://cr.bazel.build/8494
PiperOrigin-RevId: 145961529
MOS_MIGRATED_REVID=145961529
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145859025
MOS_MIGRATED_REVID=145859025
|
|
|
|
|
|
|
|
| |
Skylark.
--
PiperOrigin-RevId: 145836240
MOS_MIGRATED_REVID=145836240
|
|
|
|
|
|
|
|
| |
objc_bundle_library rule
--
PiperOrigin-RevId: 145834899
MOS_MIGRATED_REVID=145834899
|
|
|
|
|
|
|
|
| |
This rule allows deploying more than just a single jar. It can also read structure from pkgfilegroup, allowing deployment of non-single-jar plugins.
--
PiperOrigin-RevId: 145828461
MOS_MIGRATED_REVID=145828461
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145827720
MOS_MIGRATED_REVID=145827720
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145818492
MOS_MIGRATED_REVID=145818492
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ActionSpawn/SpawnAction now deal exclusively in RunfilesSuppliers, manifests
maps are no more.
There is some lingering awkwardness, in particular:
- Manifests still need to be tracked in some places, we can work out if this is
still necessary on a case by case basis.
- Skylark makes actions' runfiles available via 'resolve_command' where they are
consumed by 'action'. I've updated the documentation, though the name isn't
entirely accurate anymore. That being said these interfaces _are_ marked as
experimental, so we _should_ be able to be flexible here.
Overall, I think the benefits consolidating runfiles into suppliers, from both
code cleanliness and performance perspectives (no longer needing to parse
manifests), outweights the awkwardnesses.
RELNOTES: resolve_command/action's input_manifest return/parameter is now list
--
PiperOrigin-RevId: 145817429
MOS_MIGRATED_REVID=145817429
|
|
|
|
|
|
|
|
|
|
|
| |
Somehow they were all uploaded as 0 bytes, but that's okay because the URLs
in the design doc were wrong, anyway.
Relavant design doc: https://bazel.build/designs/2016/09/19/recursive-ws-parsing.html, issue #1943.
--
PiperOrigin-RevId: 145799866
MOS_MIGRATED_REVID=145799866
|
|
|
|
|
|
|
|
| |
internal Google code.
--
PiperOrigin-RevId: 145795255
MOS_MIGRATED_REVID=145795255
|
|
|
|
|
|
|
|
| |
bundle, not the top level)
--
PiperOrigin-RevId: 145795138
MOS_MIGRATED_REVID=145795138
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145792618
MOS_MIGRATED_REVID=145792618
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move `strerror` calls into errors_<platform>.
We have to get rid of direct `errno` reading too,
because it doesn't work on Windows native.
Fixes https://github.com/bazelbuild/bazel/issues/2411
--
Change-Id: I69ff502487d698aa9e9147f02fd0bc5253e94e64
Reviewed-on: https://cr.bazel.build/8490
PiperOrigin-RevId: 145777524
MOS_MIGRATED_REVID=145777524
|
|
|
|
|
|
|
|
| |
They differed only in reporting action state and the way they reported "no include scanning happened" so there was no reason to have both of them around.
--
PiperOrigin-RevId: 145773972
MOS_MIGRATED_REVID=145773972
|
|
|
|
|
|
|
|
| |
Note that these aliases are intentionally not yet functional. Nothing should be trying to build them.
--
PiperOrigin-RevId: 145746166
MOS_MIGRATED_REVID=145746166
|