aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
...
* Enable params files for resource jar actionsGravatar cushon2017-04-18
| | | | | | | to avoid exceeding the command line length limit for libraries with very large numbers of resources. PiperOrigin-RevId: 153191465
* Remove the use_objc_header rule warning. Add a generic migration warning to ↵Gravatar kaipi2017-04-18
| | | | | | objc_proto_library without the portable_proto_filters attribute. PiperOrigin-RevId: 153189663
* Roll forward of ↵Gravatar cushon2017-04-18
| | | | | | | | https://github.com/bazelbuild/bazel/commit/4a303e2cd840810b95cbc793e38bdca48e6d9556 Only unescape @@-quoted args once PiperOrigin-RevId: 153189611
* Migrate UnixGlob to Path#statIfFound() instead of #statNullable(). The ↵Gravatar felly2017-04-18
| | | | | | | | | latter swallows all filesystem failures, and does not disambiguate missing files from filesystem problems. The syscall cache now tracks IOExceptions if they are present, just as it does with readdir(). RELNOTES: None PiperOrigin-RevId: 153185433
* In android_library targets, R.class files should not be runtime dependenciesGravatar Googler2017-04-18
| | | | | | | | | | | | | | | | | | android_binary targets have their own R.java files (built from merging dependencies and any resources that belong directly to the target). As such, they don't need inherited R.java files at runtime. Taking these out makes for smaller APKs and less inheritance from the target's dependencies. Add a flag to control this behavior. Have it default to continue to include R.class files as runtime dependencies so we can control rollout of this behavior. Add tests of android_binary to ensure the JAR is filtered out as appropriate, and of android_robolectrictest to ensure that those tests still have access to the JARs. RELNOTES: none PiperOrigin-RevId: 153177074
* Fix `in` operator for targetsGravatar vladmos2017-04-18
| | | | | | `DefaultInfo in target` should always return `true` for any target. PiperOrigin-RevId: 153166669
* Introduce linkmap support for --experimental_objc_crosstool=allGravatar cpeyser2017-04-18
| | | | PiperOrigin-RevId: 153161442
* Revert "protobuf: Update protobuf to @laszlocsomor's master at commit 421d909."Gravatar Jakob Buchgraber2017-04-14
| | | | | | | This reverts commit 5235d06159ba6fee412bee261ea7867d061252b0. Unfortunately, we noticed several build errors / test failures internally due this change.
* protobuf: Update protobuf to @laszlocsomor's master at commit 421d909.Gravatar Jakob Buchgraber2017-04-14
| | | | | | | | | | | | Update protobuf to @laszlocsomor's fork of protobuf. This is essentially the development version of protobuf 3.2.0 and windows specific fixes from laszlo. Those fixes will be merged into protobuf soon: https://github.com/google/protobuf/pull/2969). For instructions on how to update protobuf for bazel see README.bazel.md. Change-Id: Ic1daafe30270cb6bcc6231e6c94fb670af0475e7
* Partition ObjC header scanning actions to better handle large targets.Gravatar Googler2017-04-14
| | | | PiperOrigin-RevId: 153140874
* Automated g4 rollback of commit b0ac3b41700cdc575c36ff2de191bc9ba2b6abf0.Gravatar cushon2017-04-14
| | | | | | | | | | | | | | | | | | *** Reason for rollback *** kokoro failures were not flakes :( *** Original change description *** Fix escaping of '@' in javabuilder command lines "@" is used to denote params files, so when it appears in labels it is escaped as "@@". The second "@" should be removed during flag parsing to avoid e.g. having it show up in strict deps errors. See bazelbuild/buildtools#83 PiperOrigin-RevId: 153127997
* Fix escaping of '@' in javabuilder command linesGravatar cushon2017-04-14
| | | | | | | | | | "@" is used to denote params files, so when it appears in labels it is escaped as "@@". The second "@" should be removed during flag parsing to avoid e.g. having it show up in strict deps errors. See bazelbuild/buildtools#83 PiperOrigin-RevId: 153098855
* Sets --objc_includes_prioritize_static_libs to be true by default.Gravatar cpeyser2017-04-14
| | | | PiperOrigin-RevId: 153096906
* BEP: report shard and numbers 1-basedGravatar Klaus Aehlig2017-04-14
| | | | | | | | | In this way, all indices are reported with 1 being the smallest possible. Also, the numbers fit better with the file names generated for log files etc. Change-Id: I7671e5a79dd47c3e3afac16108acaeacdf018fc5 PiperOrigin-RevId: 153080339
* Stop embedding apkbuildermain in Bazel binary.Gravatar ajmichael2017-04-14
| | | | | | | | | | | It is no longer used since --use_singlejar_apkbuilder is the default. A future change will remove apkbuildermain from the Bazel codebase. 4MB bazel binary size savings! :) RELNOTES: None PiperOrigin-RevId: 153079733
* Move xcrunwrapper and libtool to third_party/bazel/tools/objc from their ↵Gravatar cparsons2017-04-14
| | | | | | | | | xcode src directories There's no value in having these copied over from src/tools to tools/objc separately. RELNOTES: None. PiperOrigin-RevId: 153060955
* Update comments and remove obsolete field.Gravatar laurentlb2017-04-13
| | | | | RELNOTES: None. PiperOrigin-RevId: 153058374
* Remove empty_files for bazel binary installer.Gravatar Harsh Vardhan2017-04-13
| | | | | | | | | Bazel binary installer contains empty files because of the line that wasn't removed while packaging bazel_tools inside bazel. Fixes: https://github.com/bazelbuild/bazel/issues/2662 Change-Id: I53a1f74566c48c3458ced2d46362873a68b6bf49 PiperOrigin-RevId: 153048191
* Make C++ archiving use action_configs instead of hardcoded flagsGravatar hlopko2017-04-13
| | | | | RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag. PiperOrigin-RevId: 153046587
* Revert "protobuf: Update protobuf to @laszlocsomor's master at commit 421d909."Gravatar Jakob Buchgraber2017-04-13
| | | | This reverts commit ea82aa115794b019472b44d4f94ed902c1217f30.
* protobuf: Update protobuf to @laszlocsomor's master at commit 421d909.Gravatar Jakob Buchgraber2017-04-13
| | | | | | | | | | | | Update protobuf to @laszlocsomor's fork of protobuf. This is essentially the development version of protobuf 3.2.0 and windows specific fixes from laszlo. Those fixes will be merged into protobuf soon: https://github.com/google/protobuf/pull/2969). For instructions on how to update protobuf for bazel see README.bazel.md. Change-Id: I4f663955b0baeea3232b69ce32d9292427f5274a
* Remove duplicate LICENSE.txt.Gravatar Adam Michael2017-04-13
| | | | Change-Id: I17be35088c18e041c965bfdc0ad043271e152d44
* BEP: for local transports optionally drop path conversionGravatar Klaus Aehlig2017-04-13
| | | | | | | | | For transports that are purely local (like the ones writing to a local file), it sometimes can be useful to skip path conversion and use the local paths directly. Support this for the text and binary format file transports. Change-Id: I2ac2e187ebb11ff82c4e1ddf4881ea54f9d4205d PiperOrigin-RevId: 153044267
* Make src/test/shell/integration/logging_test.sh executable.Gravatar buchgr2017-04-13
| | | | | | ci.bazel.io fails because this shell script is not executable. PiperOrigin-RevId: 153042368
* Do not add a build id to C++ binaries by default.Gravatar lberki2017-04-13
| | | | | | | Fixes #2805. RELNOTES: None. PiperOrigin-RevId: 153039178
* Make FakeCppCompileAction fail if its source file doesn't compile without ↵Gravatar lberki2017-04-13
| | | | | | any extra defines. PiperOrigin-RevId: 153039146
* Lifting restriction that java home cannot be absolute path when jvm label is ↵Gravatar Googler2017-04-13
| | | | | | used. PiperOrigin-RevId: 153020672
* Add qemu2_x86 filegroup to @androidsdk.Gravatar ajmichael2017-04-13
| | | | | | | | | | | | This filegroup is used by the Android testing infrastructure to launch QEMU2 emulators. This filegroup will only build correctly on Linux. Tracking issue: https://github.com/bazelbuild/bazel/issues/903 RELNOTES: None PiperOrigin-RevId: 153003267
* Aspect-side compatibility with pending external workspace changes.Gravatar Googler2017-04-13
| | | | PiperOrigin-RevId: 152979269
* Remove special cases for "name" in implicit outputs codeGravatar Benjamin Peterson2017-04-13
| | | | | | | | | | | | | fa97703c1edf ("allow skylark implicit output callbacks to use the rule name") fixed a limitation of the skylark implicit outputs by adding a special case for "name" to the implicit outputs code. Later, 015e5954157a ("Remove special handling of name attribute") fixed the general problem of "name" being a special case in the attribute map. Therefore, we can remove my original fix. We may also excise an older special case in the implicit outputs templating code. Change-Id: I606c9decd98a8df492d2359abe540d3263f99fe1 PiperOrigin-RevId: 152974774
* Remove Preprocessor.ResultGravatar laurentlb2017-04-13
| | | | | RELNOTES: None. PiperOrigin-RevId: 152965874
* Fix memory regression introduced by default providersGravatar vladmos2017-04-13
| | | | | | | The memory regression was introduced in https://github.com/bazelbuild/bazel/commit/360fb4d9a1e2c44154b17aeb866e07bac2dd1b5b , now default providers are optimized and are built only on demand for all types of targets. PiperOrigin-RevId: 152957220
* Add select() support for "query --output=build".Gravatar gregce2017-04-13
| | | | | | | | | | | | | | | | | | | | | | | | | Before this change, attributes with select() were completely skipped. This doesn't attempt to merge "trivial" selects, e.g. even though: attr = [":foo"] + select({"//conditions:default": [":bar"]}) always resolves to: attr = [":foo", ":bar"] this change still produces: attr = [":foo"] + [":bar"] We could merge these in a future change, if desired. But it's not even clear that's desired. There's conceptual value in keeping the lists separate since that's how they were originally written. That gives users a cue to maybe refactor their rules. RELNOTES[NEW]: "query --output=build" now includes select()s PiperOrigin-RevId: 152956939
* Make Android data binding rules explicitly depend on the runtime library.Gravatar gregce2017-04-13
| | | | | | | | | Before this change Bazel was adding this implicitly. But that wasn't working properly with --incremental_dexing. And that implementation is a lot messier and bug-prone vs. just including it as a standard dependency. Issue: #2694 PiperOrigin-RevId: 152956638
* Add a custom single-line formatter for java.log.Gravatar schmitt2017-04-13
| | | | | | | | This logger makes it easier to parse log statements and is now enabled for Bazel's java.log. RELNOTES[INC]: Bazel now prints logs in single lines to java.log PiperOrigin-RevId: 152954337
* "minimum_os" attribute on multi-arch linking rules.Gravatar cparsons2017-04-13
| | | | | | | This issues a configuration transition on the dependencies of the rule, causing deps to be compiled with the appropriate minimum os version. RELNOTES: None. PiperOrigin-RevId: 152952168
* Remove unused variableGravatar dmishe2017-04-13
| | | | PiperOrigin-RevId: 152951579
* Add feature_flags attribute to Android binary rules.Gravatar mstaib2017-04-13
| | | | | | | | | | | This is the first actual user of the config_feature_flag rule, able to actually set its value (and thus give a point to using it!) This feature is not fully launched yet, but it is usable in any build containing this change. RELNOTES: None. PiperOrigin-RevId: 152948153
* Update outdated commentGravatar brandjon2017-04-13
| | | | | RELNOTES: None PiperOrigin-RevId: 152947523
* Document the current confusing semantics of relative windows paths with ↵Gravatar nharmata2017-04-13
| | | | | | | drive letters. RELNOTES: None PiperOrigin-RevId: 152944088
* Fix ProtobufSupport.java to use the build configuration when being called ↵Gravatar kaipi2017-04-13
| | | | | | from an apple_binary split transition context. Refactors ProtobufSupport to not rely on ruleContext for dependencies. PiperOrigin-RevId: 152939984
* BuildEvent: reflect generic converter property also in interface variablesGravatar Klaus Aehlig2017-04-13
| | | | | Change-Id: I55fd5b2f38cad9d2b18d369ae51dbd93c2c92288 PiperOrigin-RevId: 152925304
* Bazel client, Windows: impl. client-level lockingGravatar laszlocsomor2017-04-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement blaze::AcquireLock and ReleaseLock. These methods implement the Bazel client-level locking, whose purpose is to detect concurrently running Bazel instances attempting to write to the same output directory. The Bazel server also detects this case (see BlazeCommandDispatcher) but the client needs to start the server first, meaning this cannot detect races between clients that are in the middle of installing. You can see this locking in effect if you run `bazel --output_user_root=/c/foo build src:bazel` in one terminal, then run `bazel --output_user_root=/c/foo help` in another but the same working directory. The second one will say "Another command is running." See https://github.com/bazelbuild/bazel/issues/2107 See https://github.com/bazelbuild/bazel/issues/2647 RELNOTES: none PiperOrigin-RevId: 152919185
* Delete Preprocessor.FactoryGravatar laurentlb2017-04-12
| | | | PiperOrigin-RevId: 152916191
* Squash remaining unmerged changes and resubmit PR from #2758Gravatar Peter Mounce2017-04-12
| | | | | | Closes #2764. PiperOrigin-RevId: 152907840
* Make android_sdk_repository generate filegroups containing system image ↵Gravatar ajmichael2017-04-12
| | | | | | | | | | | | | | | | | | files for all android system images installed in the SDK. For system images that are not installed, create genrule "poison pills" that print a helpful error message if you attempt to build them. These filegroups are intended to be used as the system_image attribute of the android_device rule. Example: $ bazel build @android_test_support//tools/android/emulated_devices/pixel:android_25_x86 Extracting Bazel installation... . INFO: Found 1 target... ERROR: /usr/local/google/home/ajmichael/.cache/bazel/_bazel_ajmichael/efa32264346ef1fc4fec492202b88b31/external/androidsdk/BUILD.bazel:56:1: Executing genrule @androidsdk//:emulator_images_android_25_x86 failed: Process exited with status 1 [sandboxed]. This rule requires that the Android SDK used by Bazel has the following system image installed: emulator_images_android_25_x86. Please install this system image through the Android SDK Manager and try again. RELNOTES: None PiperOrigin-RevId: 152889824
* Delete Preprocessor.Factory.SupplierGravatar laurentlb2017-04-12
| | | | | RELNOTES: None. PiperOrigin-RevId: 152882585
* Put my name on the proto_library blog post.Gravatar carmi2017-04-12
| | | | | RELNOTES=None PiperOrigin-RevId: 152854488
* Introduce hidden configuration flag to list dexopts used by DexFileMerger ↵Gravatar kmb2017-04-12
| | | | | | | | tool during incremental dexing RELNOTES: none PiperOrigin-RevId: 152838197
* Used 'DefaultInfo' instead of `ctx.default_provider`.Gravatar dslomov2017-04-12
| | | | | | | This follows our CamelCaseInfo naming conventions for providers. RELNOTES: None. PiperOrigin-RevId: 152832215
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-03 07:08:24 +0000