Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Mike Kruskal	fc73215f86	Internal change PiperOrigin-RevId: 480942674	2 years ago
Mike Kruskal	72f7799d12	Internal change PiperOrigin-RevId: 480925629	2 years ago
Joshua Haberman	49f356a801	For macOS, build a single multiarch "universal2" wheel instead of separate x86_64 and arm64 wheels. When I tried the previous `arm64` wheel on macOS, I discovered that `pip` on macOS only supports the `arm64` platform tag in a limited set of circumstances. pip seems to prefer `universal2` wheels. To build a `universal2` wheel, we must run the `llvm-lipo` tool to bundle multiple `cc_binary()` outputs into a single output wheel. We use a transition to depend on multiple architectures for the extension, if we see that we are building for a multiarch CPU. PiperOrigin-RevId: 447486256	3 years ago
Joshua Haberman	3de02fdb8b	Created a pure-Python wheel and added a test for it. PiperOrigin-RevId: 446752839	3 years ago
Joshua Haberman	fbcd42b9f0	Added a test that the Python module is importable, and fixed several issues that were required to make the test pass: 1. For some reason the version script was not working, it was failing to export the main symbol for the Python extension. I fixed this by using the `visibility` attribute instead to export the `PyInit__message` function. 2. We were not properly stripping the `python/dist/` prefix for the C module, which was making the module exported under the name `dist.google._upb` instead of `google._upb`. 3. The `py_library()` rule was failing to actually propagate the module file into the wheel, so I just removed it. PiperOrigin-RevId: 445446611	3 years ago
Protobuf Team	ee6b1abb35	Create targets for UPB release PiperOrigin-RevId: 441496547	3 years ago