| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
a strict deps error.
Currently, the plugin canonicalizes targets using the 'target.properties' resource, this allows strict deps on private visibility rules to be resolved. However, if a rule in the target mapping itself has a strict deps error the wrong recipient will be calculated.
--
PiperOrigin-RevId: 145745493
MOS_MIGRATED_REVID=145745493
|
|
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
|
|
| |
Per review feedback from commit efb2f17075a3dbc3d5875699252db7e35a28c8d7, add Fission feature
per_object_debug_info to MockCcSupport, replacing real -gsplit-dwarf
with a fake name and use it in the added Fission tests.
--
PiperOrigin-RevId: 145540550
MOS_MIGRATED_REVID=145540550
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145538761
MOS_MIGRATED_REVID=145538761
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This change is no longer needed because commit d9a7d3a789be559bd6972208af21adae871d7a44 is rollbacked
*** Original change description ***
Add --manifest_file option into BazelJavaBuilder
Now Bazel JavaBuilder can specifiy a file as the manifest file, before
this it just creates the manifest file on the fly.
--
PiperOrigin-RevId: 145534408
MOS_MIGRATED_REVID=145534408
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145524911
MOS_MIGRATED_REVID=145524911
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example for this library:
```
bazel run //src/tools/generate_workspace -- --artifact=com.wix:wix-embedded-mysql:2.1.3
```
I get this exception:
```
Exception in thread "main" java.lang.ClassCastException: sun.net.www.protocol.ftp.FtpURLConnection cannot be cast to java.net.HttpURLConnection
at com.google.devtools.build.workspace.maven.DefaultModelResolver.pomFileExists(DefaultModelResolver.java:143)
at com.google.devtools.build.workspace.maven.DefaultModelResolver.getModelSource(DefaultModelResolver.java:124)
at com.google.devtools.build.workspace.maven.DefaultModelResolver.resolveModel(DefaultModelResolver.java:96)
at com.google.devtools.build.workspace.maven.Resolver.resolveEffectiveModel(Resolver.java:172)
at com.google.devtools.build.workspace.maven.Resolver.resolveArtifact(Resolver.java:137)
at com.google.devtools.build.workspace.GenerateWorkspace.generateFromArtifacts(GenerateWorkspace.java:123)
at com.google.devtools.build.workspace.GenerateWorkspace.main(GenerateWorkspace.java:64)
```
The cause is the dependency's pom is resolved as `file://${basedir}/src/test/lib/org/apache/httpcomponents/httpclient/4.2.5/httpclient-4.2.5.pom`, which can't be tested with HTTP HEAD request, obviously.
This patch is workaround, until there will be some better handling of such cases.
Closes #2348.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2348
PiperOrigin-RevId: 145523022
MOS_MIGRATED_REVID=145523022
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
Fixed: https://github.com/bazelbuild/bazel/issues/2242
--
Change-Id: I6aa7c97487b3add30df59c4483e409bb4d4c7532
Reviewed-on: https://cr.bazel.build/8399
PiperOrigin-RevId: 145520851
MOS_MIGRATED_REVID=145520851
|
|
|
|
|
|
|
|
| |
The tool will be used to construct resources jars separately from JavaBuilder.
--
PiperOrigin-RevId: 145511455
MOS_MIGRATED_REVID=145511455
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145507177
MOS_MIGRATED_REVID=145507177
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145495392
MOS_MIGRATED_REVID=145495392
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145473478
MOS_MIGRATED_REVID=145473478
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145473123
MOS_MIGRATED_REVID=145473123
|
|
|
|
|
|
|
|
| |
performed in order to expose it in build summary output.
--
PiperOrigin-RevId: 145457357
MOS_MIGRATED_REVID=145457357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
After discussing with thomaswk@, we've decided not to put these in the android_sdk.
*** Original change description ***
Add attributes to android_sdk rule so that they will be available for open sourcing android_device.
--
PiperOrigin-RevId: 145444443
MOS_MIGRATED_REVID=145444443
|
|
|
|
|
|
|
|
| |
sourcing android_device.
--
PiperOrigin-RevId: 145429610
MOS_MIGRATED_REVID=145429610
|
|
|
|
|
|
|
|
|
|
|
| |
Now Bazel JavaBuilder can specifiy a file as the manifest file, before
this it just creates the manifest file on the fly.
--
Change-Id: I515d63a008e2c9e9113c56d3646b8bc78b76b3a7
Reviewed-on: https://cr.bazel.build/8352
PiperOrigin-RevId: 145428635
MOS_MIGRATED_REVID=145428635
|
|
|
|
|
|
|
|
| |
transition at the top level for the expanded set of apple rule classes
--
PiperOrigin-RevId: 145421255
MOS_MIGRATED_REVID=145421255
|