| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146005461
MOS_MIGRATED_REVID=146005461
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145744124
MOS_MIGRATED_REVID=145744124
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flag, the headers of a target are compiled into a C++ module instead of being
parsed as their own translation unit. The module otherwise remains unused.
This way, parse_headers can be used to get a codebase ready for C++ modules.
parse_headers currently already gets close, but there are still ways in which a
header can be modules-incompatible although it parses fine.
--
PiperOrigin-RevId: 145729231
MOS_MIGRATED_REVID=145729231
|
|
|
|
|
|
|
|
|
|
| |
* Bitcode symbol maps allow Apple to provide a new dSYM output when they recompile bitcode on the App Store. This makes it possible to debug apps build with embedded bitcode.
* The new debug outputs provider makes it easy (and correct) for other rules to post-process (package, analyze, upload) dSYM and Bitcode artifacts.
--
PiperOrigin-RevId: 145720293
MOS_MIGRATED_REVID=145720293
|
|
|
|
|
|
|
|
| |
but is no longer used anywhere.
--
PiperOrigin-RevId: 145716681
MOS_MIGRATED_REVID=145716681
|
|
|
|
|
|
|
|
|
|
| |
added as inputs to dependant compile actions. This puts
experimental_objc_library in line with the behavior of objc_library, and
allows targets that specific "-fmodules" to continue to build.
--
PiperOrigin-RevId: 145714898
MOS_MIGRATED_REVID=145714898
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145701736
MOS_MIGRATED_REVID=145701736
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145688972
MOS_MIGRATED_REVID=145688972
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145686107
MOS_MIGRATED_REVID=145686107
|
|
|
|
|
|
|
|
| |
This change modifies the warning text that's printed when passing --test_output=streamed.
--
PiperOrigin-RevId: 145675853
MOS_MIGRATED_REVID=145675853
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will enable the upcoming android test rules to write integration tests
that depend on the system image files from the Android SDK referenced by the
android_sdk_repository rule. E.g.,
```
$ cat WORKSPACE
android_sdk_repository(
name = "androidsdk",
)
$ cat BUILD
sh_test(
name = "integration_test_that_needs_a_system_image",
srcs = ["my_test.sh"],
deps = ["@androidsdk//:system-images/android-24/default/x86/system.img"],
)
```
--
PiperOrigin-RevId: 145675526
MOS_MIGRATED_REVID=145675526
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we were adding a dependency to the rule itself, however the repository
itself can depends on further dependencies (environment, template files, ...) with
Skylark repositories. Not invalidating when those change was causing weird invalidation
issues that were shown with the invalidation on environment (basically a refetch of
the repository on environment invalidation would not cause an invalidation of the
corresponding package, the next call would not have invalidation of the repository
but would see the change in the build files...).
--
Change-Id: I8945d9885e6390734ba02ccc6c3c6ca639fcec35
Reviewed-on: https://cr.bazel.build/8137
PiperOrigin-RevId: 145675258
MOS_MIGRATED_REVID=145675258
|
|
|
|
|
|
|
|
| |
RELNOTES: Android resource shrinking is now available for android_binary rules. To enable, set the attribute 'shrink_resources = 1'. See https://bazel.build/versions/master/docs/be/android.html#android_binary.shrink_resources.
--
PiperOrigin-RevId: 145674372
MOS_MIGRATED_REVID=145674372
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NDK13 changelog: https://github.com/android-ndk/ndk/wiki/Changelog-r13.
The most notable change is that the default compiler is now clang and GCC is not supported.
Also introduces an interface to encapsulate the creation and usage of ApiLevel and AndroidNdkCrosstoolsR* so that we can get rid of the repeated if-statements checking NDK major version.
RELNOTES: android_ndk_repository now supports Android NDK R13.
--
PiperOrigin-RevId: 145672022
MOS_MIGRATED_REVID=145672022
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
My assumption in commit 4cb32a994308e1b4921471e32a02c49d8ceffb84 was that lto-indexing action doesn't expand
linking features. This was wrong, and lto-indexing was broken since then as
-Wl,@thinlto_param_file was added to the command line.
This cl changes the situation by actually exposing 2 different build variables,
thinlto_indexing_param_file for lto-indexing actions, and thinlto_param_file
for normal linking actions.
--
PiperOrigin-RevId: 145669124
MOS_MIGRATED_REVID=145669124
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Wrong submit with unresolved issues
*** Original change description ***
Java template windows performance
Address issue #2426
Closes #2427.
--
PiperOrigin-RevId: 145668385
MOS_MIGRATED_REVID=145668385
|
|
|
|
|
|
|
|
|
|
|
| |
Address issue #2426
Closes #2427.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2427
PiperOrigin-RevId: 145664779
MOS_MIGRATED_REVID=145664779
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The effect of this change on Bazel is that we now set the entire list of
env variables needed for the various protocols: sharding protocol, undeclared
outputs protocol, test warnings, unused runfiles, premature exit signalling,
and coverage. We also now set TEST_SIZE, TEST_TIMEOUT, and TEST_RANDOM_SEED.
I'm not sure if all of the Bazel-side infrastructure for those protocols is
ready yet. With further progress on code sharing, they should fall into place
soon, though.
Also set GUNIT_OUTPUT for now. Ideally, we'd change upstream to accept our
more generic names, but this should do for now.
--
PiperOrigin-RevId: 145660945
MOS_MIGRATED_REVID=145660945
|
|
|
|
|
|
|
|
| |
information available in the xcode config
--
PiperOrigin-RevId: 145597372
MOS_MIGRATED_REVID=145597372
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2416
--
PiperOrigin-RevId: 145595491
MOS_MIGRATED_REVID=145595491
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145569440
MOS_MIGRATED_REVID=145569440
|
|
|
|
|
|
|
|
| |
Preconditions check because stringification is lazy.
--
PiperOrigin-RevId: 145560352
MOS_MIGRATED_REVID=145560352
|
|
|
|
|
|
|
|
|
| |
Reverts commit 4bf8cc30a572018ac27101396d18686b75ad1ab5.
With fix for https://github.com/bazelbuild/bazel/issues/2408.
--
PiperOrigin-RevId: 145544771
MOS_MIGRATED_REVID=145544771
|
|
|
|
|
|
|
|
|
|
| |
Fixed https://github.com/bazelbuild/bazel/issues/2242
--
Change-Id: I3a011c2575f47233091e8f5b87df6372a3438bdd
Reviewed-on: https://cr.bazel.build/8470
PiperOrigin-RevId: 145543780
MOS_MIGRATED_REVID=145543780
|
|
|
|
|
|
|
|
| |
Fixes #2372.
--
PiperOrigin-RevId: 145539067
MOS_MIGRATED_REVID=145539067
|
|
|
|
|
|
|
|
| |
Added tests for Java sandwich using java_binary, java_test and java_import.
--
PiperOrigin-RevId: 145538765
MOS_MIGRATED_REVID=145538765
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Change is abandoned because it's a wrong solution
See https://github.com/bazelbuild/bazel/issues/2242
*** Original change description ***
java_binary now supports long classpath that exceeds command line argment length limit
When classpath length exceeds the command line length limit, we create
an empty classpath jar whose manifest contaning the whole classpath
value.
See: https://github.com/bazelbuild/bazel/issues/2242
Fixed: https://github.com/bazelbuild/bazel/issues/1780
--
PiperOrigin-RevId: 145534282
MOS_MIGRATED_REVID=145534282
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
length limit
When classpath length exceeds the command line length limit, we create
an empty classpath jar whose manifest contaning the whole classpath
value.
See: https://github.com/bazelbuild/bazel/issues/2242
Fixed: https://github.com/bazelbuild/bazel/issues/1780
--
Change-Id: Id6dd503c17f7f17e4a4c37fa01da24e2a1ea2155
Reviewed-on: https://cr.bazel.build/8353
PiperOrigin-RevId: 145521892
MOS_MIGRATED_REVID=145521892
|