protobuf

Commit Graph

Author	SHA1	Message	Date
Protobuf Team Bot	a2c5ea614c	[ObjC] make the bazel build always use generated WKTs. This is done in basically the same way the C++ does this. It was tested locally be putting `#error` directives in the pre-generated sources and running the bazel build (it worked). PiperOrigin-RevId: 509261352	2 years ago
Protobuf Team Bot	e2aa06eaa8	[ObjC] Set up a stateless test for the WKTs. Also wire it into the regeneration script. PiperOrigin-RevId: 508751290	2 years ago
Protobuf Team Bot	26dae8d94a	[ObjC] Test pddm expansion Testing both the support and the sources expanded. PiperOrigin-RevId: 508471876	2 years ago
Protobuf Team Bot	b977cf5c7e	Mark some targets with target_compatible_with. objc_library really will only build for Apple platforms, so tag it as such. The objc conformance test really will only build/run on macOS, so tag it as such. With these two changes, it should be safer for recursive builds that include this directory no matter what the host platform is. PiperOrigin-RevId: 508438744	2 years ago
Protobuf Team Bot	2fed1e3e83	[ObjC] Move the version check out into a sh_test. Since the sources can't reference each other, this is what helps keep them in sync. Move it out to be a stand alone test in bazel instead of having it wired into the Xcode projects. PiperOrigin-RevId: 508429454	2 years ago
Xavier Bonaventura	c8ebeb1733	Set incompatible_disallow_empty_glob in CI tests In order to flip the flag, all downstream projects should be adapted. However, it is hard to fix them all if there are constant regressions. Adding it to the CI will ensure that once the project can build with incompatible_disallow_empty_glob it can keep building like that. See: bazelbuild/bazel#15327 PiperOrigin-RevId: 507927389	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
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
Joshua Haberman	95e6c5b474	Sync from Piper @327110949 PROTOBUF_SYNC_PIPER	4 years ago
Yannic Bonenberger	8b93b8eae5	[bazel] Move Objective-C runtime into //objectivec Removing language-specific targets from the top-level BUILD file will allow users to keep their workspaces smaller and easier to maintain by not depending on language rules they don't need. Similar work was done for Java in #7190.	4 years ago

8 Commits (9a76b96cc4c659d9b677cfe476a027556a28638c)