aboutsummaryrefslogtreecommitdiffhomepage
path: root/BUILD
Commit message (Collapse)AuthorAge
* Removed some unused C++ source filesGravatar Adam Cozzette2018-03-22
|
* Merge pull request #4347 from xfxyjwf/pluginpbGravatar Feng Xiao2018-03-09
|\ | | | | Revert "Move `compiler/plugin.pb.cc` to libprotobuf with the other WKT sources."
* | Replace //:protoc and similar default macro arguments withGravatar James O'Kane2018-03-08
| | | | | | | | | | | | | | @com_google_protobuf prefixed versions. This allows them to work in 3rd party repositories. Fix a bad visibility rule. :hidden does not exist, but :private does.
| * Revert "Move `compiler/plugin.pb.cc` to libprotobuf with the other WKT sources."Gravatar Feng Xiao2018-03-01
|/ | | | This reverts commit 724f0be33d0eb42055ebe81ce0c8c7bf88ea666c.
* Blacklist all WELL_KNOWN_PROTOS from Bazel C++ code generation.Gravatar John Millikin2018-02-24
| | | | | | | | | This prevents the Bazel `CcProtoAspect` from generating and linking C++ object code for these files. Without this blacklist, symbols for protobuf types depended on by `libprotobuf` may be defined multiple times and violate the ODR rule. Fixes https://github.com/google/protobuf/issues/4311
* Move `compiler/plugin.pb.cc` to libprotobuf with the other WKT sources.Gravatar John Millikin2018-02-24
| | | | | This lets all values of `WELL_KNOWN_PROTOS` be treated the same with regard to Bazel's protobuf blacklisting.
* Bazel: Support building with Java 9Gravatar David Ostrovsky2018-01-31
| | | | | | | | | | | | | | | | | | Fixes: #4256. Bazel@HEAD supports Java 9. The current code has one single issue with Java 9 compliance: the usage of sun.misc package. We add jdk.unsupported module with --add-modules compiler option for now. Long term, the usage of non public API should be avoided. To build with Java 9, build custom bazel version and issue: $ bazel --host_javabase=/usr/lib64/jvm/java-9-openjdk build \ --javacopt='--release 9' \ --java_toolchain=@bazel_tools//tools/jdk:toolchain_jdk9 \ :protobuf_java
* Drop java 6 supportGravatar David Ostrovsky2018-01-25
| | | | Fixes #4220.
* Merge pull request #2834 from aj-michael/masterGravatar Jisi Liu2017-12-12
|\ | | | | Make //:protobuf_python have correct __init__.py.
* | Ran update_file_lists.sh to update Bazel and CMake file listsGravatar Adam Cozzette2017-12-07
| | | | | | | | | | This should fix Bazel builds, since those were missing a new file (implicit_weak_message.cc).
* | Remove unhelpful build warningsGravatar Justine Tunney2017-11-17
| | | | | | | | | | | | | | | | -Wno-writable-strings removes 230 "ISO C++11 does not allow conversion from string literal to 'char *'" warnings from TensorFlow test / build output. These happen because pyext/ sources pass string literals to Python C API data structures, e.g. PyGetSetDef, which for some reason were designed to not have the const qualifier.
* | Merge pull request #3757 from spinorx/masterGravatar Jisi Liu2017-10-20
|\ \ | | | | | | Fix iOS cc_library build for protobuf.
* | | Fix bazel buildGravatar Jisi Liu2017-10-18
| | |
| * | Fix iOS cc_library build for protobuf.Gravatar Param Reddy2017-10-15
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SDK and os versions were hard coded. Archs were mixed up. Because of this, Was getting errors with latest SDK: clang: warning: no such sysroot directory: '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/' [-Wmissing-sysroot] clang: warning: no such sysroot directory: '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/' [-Wmissing-sysroot] clang: warning: no such sysroot directory: '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/' [-Wmissing-sysroot] In file included from external/com_google_protobuf/src/google/protobuf/io/printer.cc:35: In file included from external/com_google_protobuf/src/google/protobuf/io/printer.h:40: In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/string:470: In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/string_view:171: In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__string:56: In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/algorithm:638: In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cstring:61: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/string.h:61:15: fatal error: 'string.h' file not found ^~~~~~~~~~ 1 error generated. Currently none of these are needed when using bazel with https://github.com/bazelbuild/rules_apple. -target arm64-apple-ios is passed properly to clang. So -arch armv7 etc are not needed. OS_IOS is not used anywhere. Sources have: GOOGLE_PROTOBUF_NO_THREADLOCAL defined in src/google/protobuf/stubs/platform_macros.h for iOS. So __thread= is not needed. In fact now that bazel is using C++11 by default, __thread should ideally be moved to thread_local. -miphoneos-version-min is passed by rules_apple.
* | Don't pass -lpthread and -lm on WindowsGravatar Seth Greenstein2017-10-10
| | | | | | These flags are ignored by cl.exe and have no effect, but add noise to the build logs.
* | Integrated internal changes from GoogleGravatar Adam Cozzette2017-09-14
| |
* | Exclude addressbook.proto from C# boostrap test.Gravatar Feng Xiao2017-09-11
| | | | | | | | | | This addressbook.proto now belongs to its own bazel pacakge and can't be accessed in bazel protobuf_test target.
* | bazel: Add proto_library rules for well known types. Fixes #2763Gravatar Jakob Buchgraber2017-09-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds a proto_library rule for each well known type proto: $ bazel query "filter(\".*_proto$\", \"...\")" //:wrappers_proto //:timestamp_proto //:struct_proto //:field_mask_proto //:empty_proto //:duration_proto //:compiler_plugin_proto //:descriptor_proto //:api_proto //:type_proto //:source_context_proto //:any_proto Bazel users can reference these proto_library rules for their own language specific rules i.e. java_proto_library( name = "any_java_proto", deps = ["@com_google_protobuf//:any_proto"], ) Also set the workspace name to "com_google_protobuf", as proto_library rules reference protobuf that way.
* | Fix makefile.amGravatar Jisi Liu2017-07-25
| |
* | Fix build filesGravatar Jisi Liu2017-07-25
| |
* | Merge from masterGravatar Jisi Liu2017-07-25
| |
* | update build file listGravatar Jisi Liu2017-07-19
| |
* | bazel: Make compiled jars java 6 binary compatible.Gravatar Jakob Buchgraber2017-06-16
| | | | | | | | See: https://github.com/bazelbuild/bazel/issues/3198
* | Refactor cc options in BUILD file for WindowsGravatar Yun Peng2017-05-31
| | | | | | | | | | Don't put gcc warnings options in copts, so that protobuf is able to build by MSVC toolchain without python wrappers.
* | Merge pull request #3024 from acozzette/merge-3.3-to-masterGravatar Adam Cozzette2017-05-01
|\ \ | | | | | | Merged 3.3.x branch to master
* | | added "objectivec" build target (#3033)Gravatar makdharma2017-05-01
| | | | | | | | | This target will be used by gRPC iOS bazel build system.
| * | Update BUILD file for C# tests.Gravatar Feng Xiao2017-03-29
| | |
| * | Fix C++ build for down-integration.Gravatar Feng Xiao2017-03-29
|/ /
* | Compile the Java proto runtime with Java 6Gravatar cgrushko2017-03-22
| | | | | | | | in order to avoid errors related to generics when building user code in newer versions of Java.
* | Update BUILDGravatar Bairen Yi2017-03-21
| |
* | migrate delimited messages functions to util packageGravatar Byron Yi2017-03-16
| |
| * Make //:protobuf_python have correct __init__.py.Gravatar Adam Michael2017-03-10
|/ | | | | Previously //:protobuf_python set no __init__.py so Bazel created an empty one. This change makes it use the __init__.py from the repository.
* Merge pull request #2751 from keveman/masterGravatar Feng Xiao2017-03-06
|\ | | | | Added a header only cc_library target for the protobuf library.
| * Added comment explaining the protobuf_headers target.Gravatar Manjunath Kudlur2017-03-02
| |
* | Merge pull request #2630 from blodan/masterGravatar Jisi Liu2017-02-24
|\ \ | | | | | | FreeBSD compatibility
| | * Added a header only cc_library target for the protobuf library.Gravatar Manjunath Kudlur2017-02-23
| |/ |/|
* | Update load() statement to latest styleGravatar cgrushko2017-02-08
| | | | | | | | The first argument is currently implicitly a .bzl file. Change this to be explicit.
| * FreeBSD compatibilityGravatar Daniel Ylitalo2017-01-25
|/
* Add a proto_lang_toolchain for JavaGravatar cgrushko2017-01-12
| | | This allows easy use of Bazel's java_proto_library native rule.
* Added Bazel genrule for generating well_known_types_embed.ccGravatar Adam Cozzette2016-12-20
| | | | | In pull request #2517 I made this change for the CMake and autotools builds but forgot to do it for the Bazel build.
* Add missing files.Gravatar Jisi Liu2016-12-05
|
* Add a proto_lang_toolchain() for cc_proto_libraryGravatar cgrushko2016-12-02
| | | | | | | | | Bazel's built-in cc_proto_library rule uses a proto_lang_toolchain to learn how to invoke proto-compiler. To use Bazel's cc_proto_library, add the following to your project's WORKSPACE file: local_repository( name = "com_google_protobuf_cc", path = "/path/to/protobuf-distribution/" )
* Place Python extensions correctly in Bazel build.Gravatar Richard Shin2016-10-18
|
* update files to include php generatorsGravatar Jisi Liu2016-10-10
|
* Silence compile warnings in bazelGravatar Andy Hochhaus2016-10-09
|
* Remove inexist files from build.Gravatar Feng Xiao2016-10-06
|
* update files to include php generators (#2165)Gravatar Jisi Liu2016-10-06
|
* Bazel: export LICENSE file.Gravatar Piotr Sikora2016-08-04
| | | | Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* Bazel build: Keep generated sources and Python runtime in the same directory.Gravatar David Z. Chen2016-05-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Users often encounter a Python import error when trying to build Python protos if protobuf is installed locally on the machine. In this case, Python ends up looking in the wrong directory when importing files (see bazelbuild/bazel#1209 and tensorflow/tensorflow#2021). It seems that the problem is caused by Python getting confused when there are Python source files that are meant to be part of the same package but are in separate directories. Prior to #1233, the Bazel build setup would copy the Python runtime sources and all generated sources for the builtin protos into the root directory (assuming that the protobuf tree is vendored in a google/protobuf directory). With #1233, the two sets of sources are kept in their respective directories but both `src/` and `python/` are added to the `PYTHONPATH` using the new `imports` attribute of the Bazel Python rules. However, both the runtime sources and the generated sources are under the same package: `google.protobuf`, causing Python to become confused when trying to import modules that are in the other directory. This patch adds a workaround to the Bazel build to add a modified version of the original `internal_copied_filegroup` macro to copy the `.proto` files under `src/` to `python/` before building the `py_proto_library` targets for the builtin protos. This ensures that the generated sources for the builtin protos will be in the same directory as the corresponding runtime sources. This patch was tested with the following: * All Python tests in protobuf * All Python tests in tensorflow * All tests in [Skydoc](https://github.com/bazelbuild/skydoc) * Importing protobuf as `//google/protobuf` * Importing and binding targets under `//external` * Importing protobuf as `//third_party/protobuf`
* Update file lists.Gravatar Jisi Liu2016-04-28
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-26 15:21:28 +0000