aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/protobuf
Commit message (Collapse)AuthorAge
* Remove resource_extractor from android_sdk rule.Gravatar ajmichael2017-06-29
| | | | | | | | | | resource_extractor has nothing to do with the Android SDK. Once upon a time, it was needed for jack support, so it was colocated with the jack attributes in android_sdk. Nowadays, it is used as a necessary step before singlejar can run to build the APK. RELNOTES: None PiperOrigin-RevId: 160479247
* Update the --incompatible_ flag requirements to use the metadata tag.Gravatar ccalvarin2017-06-28
| | | | | | Leave the category for now as the generated docs still do not use the new categorization. PiperOrigin-RevId: 160290297
* Add option tagging and categorizing enums.Gravatar ccalvarin2017-06-27
| | | | | | | | | | | | | | Begin work of transferring option categorization to a sustainable, documented setup. DocumentationCategories will replace the existing string category field, and will group flags in generated documentation. Each flag must belong to exactly 1 DocumentationCategory, whichever is most applicable or a new one. OptionEffectTags will document the effects of tags and will be used for filtering flags. These tags, unlike the categories, should be complete. All options that do affect Bazel's output should be tagged as affecting Bazel's output, for example. This is necessary for them to be useful when trying to isolate the cause of an issue or behavior by allowing irrelevant options to be filtered out. Each flag must have at least 1 intended behavior, so should have 1+ OptionEffectTag. If no effect tag applies, find a general tag that would apply and add it to all relevant options. OptionMetadataTags will hold information about the flag itself. Information about the lifecycle of a flag, for example, should belong in an OptionMetadataTag. It is useful for filtering, since it describes how trustworthy we might think the flag would be, but does not actually describe the “intent” or “meaning” of a flag. This can be an empty list, but options can also have multiple OptionMetadataTags All options will be switched from the old "category" field to this new system. A few general OptionsBases are provided as an example. PiperOrigin-RevId: 160180328
* Remove remaining xcodegen references.Gravatar schmitt2017-06-26
| | | | | | | Deletes last code references to xcodegen tool as well as tool itself. RELNOTES: None. PiperOrigin-RevId: 160137807
* Update incorrect build.proto documentation for AttributeDefinition.name field.Gravatar Googler2017-06-26
| | | | | RELNOTES: None. PiperOrigin-RevId: 160013691
* Switching Bazel to use the new remote execution API: ↵Gravatar olaola2017-06-09
| | | | | | | | | https://docs.google.com/document/d/1AaGk7fOPByEvpAbqeXIyE8HX_A3_axxNnvroblTZ_6s/edit Also refactored away the various *Interface* files, no need since unit testing can be done with mocking the appropriate gRPC Impl classes directly (see tests). This also fixes the RemoteSpawnRunner, which should use different objects for remote caching and remote execution, the same way RemoteSpawnStrategy does. RELNOTES: n/a PiperOrigin-RevId: 158473700
* protobuf: Use bazel's native java_proto_library rules.Gravatar Jakob Buchgraber2017-06-06
| | | | | | | | | Additional changes: - Introduce a Skylark macro java_library_srcs that provides the source jars of a java_*_library rule. - Remove bazel's own java_proto_library implementation. Change-Id: I18f2259bc75ca0fb32dcd8a6a857c609bd2c7773 PiperOrigin-RevId: 158146210
* Make C++ archiving use action_configs instead of hardcoded flagsGravatar hlopko2017-06-01
| | | | | RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag. PiperOrigin-RevId: 157685703
* Keep "srcs", "hdrs" and "textual_hdrs" separate.Gravatar Googler2017-05-29
| | | | | | | | | | Each can has slightly different semantics for the IDE, and it is better to use the information on which files belong to which group from BUILD file rather than use heuristics like file extension to determine it. The contents of "textual_hdrs" are added by the prefetcher. RELNOTES: None. PiperOrigin-RevId: 157256048
* Store the features enabled for each targetGravatar Googler2017-05-23
| | | | | | | ctx.features has already merged the package-level and rule-level feature sets. RELNOTES: None. PiperOrigin-RevId: 156811464
* Expose javac jar in java_toolchain's skylark providerGravatar Googler2017-05-22
| | | | PiperOrigin-RevId: 156589908
* Rollforward of commit aa7f9307636d38cbb93a03acac8f4c59adfa0ee8.Gravatar ccalvarin2017-05-04
| | | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Filter out conflicting flag policies for applicable commands. Only enforce the filtered, applicable policy. *** Original change description *** Automated g4 rollback of commit aa7f9307636d38cbb93a03acac8f4c59adfa0ee8. *** Reason for rollback *** Broke --experimental_inmemory_dotd_files *** Original change description *** Filter out conflicting flag policies before invocation policy enforcement. This is to minimize the likelihood of obscure policy conflict. Now, the last policy on a flag (after policy expansion) will be the only one in the "canonical" invocation policy. There should be no reason for explicitly setting multiple policies on a single flag, but if an expansion flag is policy'd and one of its children has a more specific policy on it, make sure that the policy on the child flag is after the policy on the expansion flag. Note that this restriction (only the last policy gets applied) also applies for repeatable flags. Make sure all values being set to a repeatable flag are set in a single SetValue operation, with multiple flagValues set. PiperOrigin-RevId: 154969189
* Update protobuf dependency to 3.2.0Gravatar Jakob Buchgraber2017-05-02
| | | | | Change-Id: I32f6b16955ecefc242af8d9261418452d698c9ff PiperOrigin-RevId: 154812955
* Remove Scala IDE info, and use Java IDE info instead.Gravatar Googler2017-05-02
| | | | | | | | Scala IDE info is a subset of Java IDE info anyway, and would make reusing Java-specific utilities easier in the sync plugin. RELNOTES: None. PiperOrigin-RevId: 154728036
* Automated g4 rollback of commit aa7f9307636d38cbb93a03acac8f4c59adfa0ee8.Gravatar ajmichael2017-04-28
| | | | | | | | | *** Reason for rollback *** Broke --experimental_inmemory_dotd_files RELNOTES: None PiperOrigin-RevId: 154477949
* Add Scala IDE info to Intellij aspect.Gravatar Googler2017-04-26
| | | | | RELNOTES: None. PiperOrigin-RevId: 154322648
* Remove the dash moduleGravatar dmarting2017-04-20
| | | | | | | | | | This module rely on an un-maintained codepath and is hardly used by anyone. We should also archive the code from dash until we can revive it with BEP RELNOTES[INC]: --use_dash, --dash_url and --dash_secret are removed. PiperOrigin-RevId: 153701824
* Filter out conflicting flag policies before invocation policy enforcement.Gravatar ccalvarin2017-04-20
| | | | | | | | | | | | | This is to minimize the likelihood of obscure policy conflict. Now, the last policy on a flag (after policy expansion) will be the only one in the "canonical" invocation policy. There should be no reason for explicitly setting multiple policies on a single flag, but if an expansion flag is policy'd and one of its children has a more specific policy on it, make sure that the policy on the child flag is after the policy on the expansion flag. Note that this restriction (only the last policy gets applied) also applies for repeatable flags. Make sure all values being set to a repeatable flag are set in a single SetValue operation, with multiple flagValues set. PiperOrigin-RevId: 153584034
* Remove references to STRING_DICT_UNARYGravatar michajlo2017-04-19
| | | | | | | This type is no longer used and has removed from bazel. RELNOTES: None PiperOrigin-RevId: 153471066
* Automated g4 rollback of commit 045104899738594d85f9ab9b0b9ccbde320b8055.Gravatar jfield2017-04-18
| | | | | | | | | | | | | *** Reason for rollback *** Breaks internal tests that use nonstandard crosstools *** Original change description *** Make C++ archiving use action_configs instead of hardcoded flags RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag. PiperOrigin-RevId: 153344597
* 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
* 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
* Move InvocationPolicy from a startup argument to part of the RunRequest proto.Gravatar ccalvarin2017-04-07
| | | | | | | | | The user interface is not changing. The policy will still be accepted as a flag passed to the client, as a startup flag (before the command), it will just no longer trigger server restarts and will not be passed on to a bazel server as part of the startup arguments. In batch mode, however, it will still be a startup argument, because the RunRequest proto is not sent, and all invocations restart bazel in batch mode anyway. Since invocation policy only affects command arguments, and changes in command arguments do not cause server restarts, this is consistent with other server restart behavior. RELNOTES: Changing --invocation_policy will no longer force a server restart. PiperOrigin-RevId: 152426207
* Add environment variables to CppCompileInfo.Gravatar cpeyser2017-04-05
| | | | PiperOrigin-RevId: 152173189
* Remove jack support and make jack/jill attributes of android_sdk optional.Gravatar ajmichael2017-04-04
| | | | | | | | | Closes https://github.com/bazelbuild/bazel/issues/1391. RELNOTES: Removed --experimental_use_jack_for_dexing and libname.jack output of android_library. PiperOrigin-RevId: 152131075
* Add internal section to override android jar.Gravatar Googler2017-04-03
| | | | PiperOrigin-RevId: 151825956
* Delete STRING_DICT_UNARYGravatar michajlo2017-03-31
| | | | | | | This isn't used anymore, it's the same as STRING_DICT, deleting so no one tries to use it. PiperOrigin-RevId: 151738915
* Make apkbuilder attribute of android_sdk optional.Gravatar ajmichael2017-03-31
| | | | | | | | This change is one step towards removing --nouse_singlejar_apkbuilder. RELNOTES: None PiperOrigin-RevId: 151730390
* Also report starting times of test actionsGravatar aehlig2017-03-31
| | | | | | | | | Record the starting times of test actions, so that they can be reported in the build event protocol. Change-Id: I28e8d7d6ad39d91f4ffdd8a6161a5fc30f9a39b8 PiperOrigin-RevId: 151724760
* Changing package name for remote execution proto.Gravatar Ola Rozenfeld2017-03-23
| | | | | | | | | | Preparing for it to be a proper OnePlatform API. TESTED=n/a -- PiperOrigin-RevId: 150997585 MOS_MIGRATED_REVID=150997585
* Clarify UseDefault behavior surrounding expansion flags.Gravatar Chloe Calvarin2017-03-14
| | | | | | | | Also warn that user values can be lost, at which point later policies won't revive them. This warning should be removed once [] is fixed. -- PiperOrigin-RevId: 149939586 MOS_MIGRATED_REVID=149939586
* Adding an opaque Platform message with keys and values. As a first stepGravatar Ola Rozenfeld2017-03-10
| | | | | | | | | | | | towards cross-platform support, we will add a hack that takes some values via a command line flag, and pass them on to a remote execution engine (next CL). TESTED=no change RELNOTES: n/a -- PiperOrigin-RevId: 149753326 MOS_MIGRATED_REVID=149753326
* Read intellij plugin debug target deploy info from the build step instead of ↵Gravatar Googler2017-03-10
| | | | | | | | via the target map. -- PiperOrigin-RevId: 149666196 MOS_MIGRATED_REVID=149666196
* Make external workspace handling forwards and backwards compatible.Gravatar Googler2017-03-09
| | | | | | | | | Add a field to the IntelliJ aspect proto which handles both current and future formats. -- PiperOrigin-RevId: 149559228 MOS_MIGRATED_REVID=149559228
* Revert "Upgrade //third_party/protobuf to v3.2.0"Gravatar Irina Iancu2017-02-24
| | | | | | | | | | | | | This reverts commit 2346f5a01561f695a2b2ba7655359d5020105077. It breaks bazel build in freebsd[1]. The solution is to patch https://svnweb.freebsd.org/ports/head/devel/protobuf/files/. I rolled-back this since the other builds will not automatically start if Bazel is broken. [1] http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1312/ Change-Id: I7e939a4293d799ab6dd67f93d219d1efdf4cd901
* Add is_external support to PackageManifestParser.Gravatar Googler2017-02-24
| | | | | | -- PiperOrigin-RevId: 148375330 MOS_MIGRATED_REVID=148375330
* Add the LABEL_KEYED_STRING_DICT type for attributes.Gravatar Michael Staib2017-02-24
| | | | | | | | | This enables both native and Skylark rules to declare attributes which have labels/Targets as keys, and have string values. -- PiperOrigin-RevId: 148365033 MOS_MIGRATED_REVID=148365033
* Upgrade //third_party/protobuf to v3.2.0Gravatar Carmi Grushko2017-02-23
| | | | | | | with some backports from HEAD (:java_toolchain, internal_gen_well_known_protos_java) Change-Id: I54be8809f411ec8cb02203b478f699e1fccb5f62
* Switch from protobuf_clib to protobuf, and protobuf-util to protobuf_java_util.Gravatar Carmi Grushko2017-02-10
| | | | | | | | The latter are the names in the upstream protobuf repo. -- PiperOrigin-RevId: 147163206 MOS_MIGRATED_REVID=147163206
* Pass 'main_class' attribute value through in the IntelliJ aspect.Gravatar Googler2017-02-09
| | | | | | | | Then use it in the blaze plugin's main class run configuration producer. -- PiperOrigin-RevId: 146980092 MOS_MIGRATED_REVID=146980092
* Add a boolean flag to a Feature to specify whether it is enabled by default.Gravatar Googler2017-02-08
| | | | | | | | | This enables us to configure default features for each toolchain without having to hard-code anything in class such as CcCommon. -- PiperOrigin-RevId: 146904287 MOS_MIGRATED_REVID=146904287
* RELNOTES: Allow CROSSTOOL files to have linker flags specific to static ↵Gravatar Googler2017-02-06
| | | | | | | | shared libraries. -- PiperOrigin-RevId: 146655595 MOS_MIGRATED_REVID=146655595
* Add intellij_plugin_debug_target rule.Gravatar Googler2017-01-30
| | | | | | | | 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
* Description redacted.Gravatar Googler2017-01-20
| | | | | | -- PiperOrigin-RevId: 144983864 MOS_MIGRATED_REVID=144983864
* Adding Golang support to the remote_protocol proto library.Gravatar Ola Rozenfeld2017-01-13
| | | | | | -- PiperOrigin-RevId: 144348933 MOS_MIGRATED_REVID=144348933
* Expose Worker protocol buffer to C++ so we can implement persistent actions ↵Gravatar Andreas Bergmeier2017-01-12
| | | | | | | | | | | | in C++. Protocol was already exposed for Python and Java, only make C++ a first class citizen. -- Change-Id: Ib2aa45bdb534f0f9181483b0161f2aa7c857dfb4 Reviewed-on: https://cr.bazel.build/7814 PiperOrigin-RevId: 144300665 MOS_MIGRATED_REVID=144300665
* Introduce expand_if_none_available to crosstoolGravatar Marcel Hlopko2017-01-10
| | | | | | | | | | This feature allows us to expand a flag_group when a build variable is not available. This is helpful when migrating crosstools in a backward compatible way (that works with released bazel as well as with bazel at HEAD). -- PiperOrigin-RevId: 143955333 MOS_MIGRATED_REVID=143955333
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-05 01:58:22 +0000