protobuf

Commit Graph

Author	SHA1	Message	Date
Romfos	09f094c811	[dotnet, csharp] Run tests for supported platforms .NET 6, .NET Framework 4.6.2 (#12378 ) What's changed? - Update some nuget packages (for test projects) - Run unit tests for supported platforms: .NET 6 + .NET Framework 4.6.2 Notes: .NET Framework 4.6.1 is out of support, .NET Framework 4.6.2 is the older version that is still supported https://devblogs.microsoft.com/dotnet/net-framework-4-5-2-4-6-4-6-1-will-reach-end-of-support-on-april-26-2022/ .NET 5 is out of support https://devblogs.microsoft.com/dotnet/dotnet-5-end-of-support-update/ .NET Core 3.1 is out of support https://devblogs.microsoft.com/dotnet/net-core-3-1-will-reach-end-of-support-on-december-13-2022/ Visual studio 2012 is out of support https://devblogs.microsoft.com/visualstudio/support-ends-for-older-versions-of-visual-studio-feb2022 Closes #12378 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/12378 from Romfos:main `227661e02c` PiperOrigin-RevId: 523196896	2 years ago
Mike Kruskal	ff91b25494	Use generated Conformance proto for Bazel targets. PiperOrigin-RevId: 510158778	2 years ago
Jon Skeet	5c6c868588	Rename C# files to indicate generated code (#10801 ) * Change C# generation script to use .pb.cs extension * Rename generated C# files This was performed by running generate_protos.sh and then removing the old files. Notes: - This does not change the conformance test generated C# code - This does not change the compatibility C# code - There's currently no clean-up operation in generate_protos.sh to remove old .pb.cs files (which would now be feasible) - The changes to TestMessagesProto2.pb.cs are just due to formatting and a new Objective-C option * Fix well-known type source files for C# Bazel build	2 years ago
Mike Kruskal	8bad7e0dd0	Clean up leftover benchmark cruft (#10480 ) * Removing benchmark submodule * Removing C# benchmarks * Removing dangling benchmark references * Deleting unused function	2 years ago
Mike Kruskal	ed5c57a574	Remove all autotools usage (#10132 ) * Bazelfying conformance tests Adding infrastructure to "Bazelify" languages other than Java and C++ * Delete benchmarks for languages supported by other repositories * Bazelfying benchmark tests * Bazelfying python Use upb's system python rule instead of branching tensorflow * Bazelfying Ruby * Bazelfying C# * Bazelfying Objective-c * Bazelfying Kokoro mac builds * Bazelfying Kokoro linux builds * Deleting all deprecated files from autotools cleanup This boils down to Makefile.am and tests.sh and all of their remaining references * Cleanup after PR reorganizing - Enable 32 bit tests - Move conformance tests back - Use select statements to select alternate runtimes - Add internal prefixes to proto library macros * Updating READMEs to use bazel instead of autotools. * Bazelfying Kokoro release builds * First round of review fixes * Second round of review fixes * Third round of review fixes * Filtering out conformance tests from Bazel on Windows (b/241484899) * Add version metadata that was previously scraped from configure.ac * fixing typo from previous fix * Adding ruby version tests * Bumping pinned upb version, and adding tests to python CI	2 years ago
Deanna Garcia	2656854aa8	Rename and fix dist errors	2 years ago
Deanna Garcia	4bcc41af5c	Add bazel rule to build C# release artifacts	2 years ago
David L. Jones	cbd1adc6cf	[Bazel/C++] Factor out compiler packages. (#9985 ) This change adds packages for protoc sources under src/google/protobuf/compiler (this is similar to what was done in #9980).	3 years ago
David L. Jones	95da0ba5b4	Rename all BUILD files to BUILD.bazel (#9892 ) This avoids conflicting names in a couple of cases. 1. Within google, we want to sync files but not name them BUILD (since the structure doesn't match). 2. On case-insensitive filesystems, `build` may be used for a build directory. Naming `BUILD.bazel` avoids potentioal conflicts.	3 years ago
Joshua Haberman	dc4aad931e	Sync from Piper @444600173 PROTOBUF_SYNC_PIPER	3 years ago
David L. Jones	d76f8c868c	Add source distribution packaging rules (#9835 ) This change adds `rules_pkg`-based targets that will produce source distribution archives, similar to `make dist`. These rules produce nearly the same outputs as `make dist`. However, there are some differences and caveats: 1. The outputs do not contain vendored googletest sources. 2. You have to run `autogen.sh` before `blaze build pkg:all`. This produces several autotools-related files directly into the source tree. 3. The output .zip files do not have a directory prefix like `protobuf-3.20.1-rc-1` (this will be addressed after [Substitute package variables in `pkg_zip#package_dir`. bazelbuild/rules_pkg#577](https://github.com/bazelbuild/rules_pkg/pull/577); the tar files do have this prefix, though.) 4. One file is missing from the archives, which is produced during the `make` build: benchmarks/gogo/cpp_no_group/cpp_benchmark.cc 5. In several places, I have explicitly excluded some files that are not in the autotools distribution outputs. I think most of those files should probably be included, but for now, I'm aiming for parity with `make dist`. These are marked with comments, so it should be easy to clean them up later.	3 years ago

9 Commits (a47a7bdc8d023467f4f0586c393597af727e1d9e)