Mizux Seiha
Mizux Seiha
One dirty solution, would be that pybind11_protobuf directly provide (and install?) the `proto_api.h` header in case of cmake based build at least...
If you [`FetchContent()`](https://cmake.org/cmake/help/latest/module/FetchContent.html) Protobuf, you could patch it to make the `proto_api.h` hdr available... see: https://github.com/google/or-tools/blob/870edf6f7bff6b8ff0d267d936be7e331c5b8c2d/patches/protobuf-v26.1.patch#L59-L68 and https://github.com/google/or-tools/blob/870edf6f7bff6b8ff0d267d936be7e331c5b8c2d/cmake/dependencies/CMakeLists.txt#L107-L110
On which OS did you work ? Can you share a minimal example so we can reproduce it ? note: on my side I have this example https://github.com/Mizux/bazel-pybind11
my 2 cents, you can take a look at: https://github.com/Mizux/bazel-pybind11 as template project with few ci jobs (e.g. https://github.com/Mizux/bazel-pybind11/actions/runs/4979586419) note: need to patch pybind11_bazel to fix windows support `-_-`
Please take a look at (currently writing it): TLDR: Bazel 7.0 should fix an issue so we can build proper native python lib (otherwise there is our hackish patch) https://github.com/Mizux/bazel-pybind11/issues/4#issue-1736947338
My 2 cents, Google Benchmark seems to use nanobind... https://github.com/google/benchmark/tree/main/bindings/python
Follow up on this topic in actions/virtual-environments/issues/4060 Question: https://github.com/actions/virtual-environments/issues/4060#issuecomment-950736374 Answer: https://github.com/actions/virtual-environments/issues/4060#issuecomment-950757410 TLDR: they should continue to support macos10.15 to support the use case Vagrant + VirtualBox etc...
nit: in ``` Preface ├── Introduction (From: Getting Started - Introduction) ├── FAQ ├── Governance ├── Release Notes └── Contribution Guide ``` I would put `FAQ` and `Release Notes` closer...
Why not adding C++ **23** and C++ **26** ? they have already landed in CMake and it will take months (years?) to have bazel 7.0 widely available so.... ``` 23...