2020-09-10 23:32:25 +08:00
|
|
|
name: test-bindings
|
|
|
|
|
|
|
|
on:
|
|
|
|
push:
|
2021-06-01 18:01:49 +08:00
|
|
|
branches: [main]
|
2020-09-10 23:32:25 +08:00
|
|
|
pull_request:
|
2021-06-01 18:01:49 +08:00
|
|
|
branches: [main]
|
2020-09-10 23:32:25 +08:00
|
|
|
|
|
|
|
jobs:
|
|
|
|
python_bindings:
|
2023-02-03 17:47:02 +08:00
|
|
|
name: Test GBM Python bindings on ${{ matrix.os }}
|
|
|
|
runs-on: ${{ matrix.os }}
|
|
|
|
strategy:
|
Switch bindings implementation to `nanobind` (#1526)
* End support for Python 3.7, update cibuildwheel and publish actions
Removes Python 3.7 from the support matrix, since it does not support
PEP590 vectorcalls.
Bumps the `cibuildwheel` and `pypa-publish` actions to their latest
available versions respectively.
* Add nanobind to the Bazel dependencies, add a BUILD file
The build file builds nanobind as a static `cc_library`. Currently,
the git SHA points to HEAD, since some necessary features have not
been included in a release yet.
* Delete pybind11 BUILD file
* Switch bindings implementation to nanobind
Switches over the binding tool to `nanobind` from `pybind11`. Most
changes in the build setup itself were drop-in replacements of existing
code changed to nanobind names, no new concepts needed to be
implemented.
Sets the minimum required macOS to 10.14 for full C++17 support. Also,
to avoid ambiguities in Bazel, build for macOS 11 on Mac ARM64.
* Use Bazel select for linker options
Guards against unknown linker option errors by selecting required
linker options for nanobind only on macOS, where they are relevant.
Other changes:
* Bump cibuildwheel action to v2.12.0
* Bump Bazel for aarch64 linux wheels to 6.0.0
* Remove C++17 flag from build files since it is present in setup.py `bazel build` command
* Bump nanobind commit to current HEAD (TBD: Bump to next stable release)
* Unbreak Windows builds of nanobind-based bindings
Guards compiler options behind a new `select` macro choosing between
MSVC and not MSVC.
Other changes:
* Inject the proper C++17 standard cxxopt in the `setup.py` build
command.
* Bump nanobind to current HEAD.
* Make `macos` a benchmark-wide condition, with public visibility to
allow its use in the nanobind BUILD file.
* Fall back to `nb::implicitly_convertible` for Counter construction
Since `benchmark::Counter` only has a constructor for `double`,
the nanobind `nb::init_implicit` template cannot be used. Therefore,
to support implicit construction from ints, we fall back to the
`nb::implicitly_convertible` template instead.
2023-02-06 21:07:17 +08:00
|
|
|
fail-fast: false
|
2023-02-03 17:47:02 +08:00
|
|
|
matrix:
|
2023-10-23 20:04:39 +08:00
|
|
|
os: [ ubuntu-latest, macos-latest, windows-latest ]
|
2020-09-10 23:32:25 +08:00
|
|
|
|
|
|
|
steps:
|
2023-10-23 20:04:39 +08:00
|
|
|
- uses: actions/checkout@v4
|
2023-12-19 22:13:08 +08:00
|
|
|
with:
|
|
|
|
fetch-depth: 0
|
|
|
|
- name: Set up Python 3.11
|
|
|
|
uses: actions/setup-python@v5
|
2020-09-10 23:32:25 +08:00
|
|
|
with:
|
2023-02-03 17:47:02 +08:00
|
|
|
python-version: 3.11
|
2023-10-23 20:04:39 +08:00
|
|
|
- name: Install GBM Python bindings on ${{ matrix.os }}
|
2023-12-19 22:13:08 +08:00
|
|
|
run: python -m pip install .
|
2023-02-03 17:47:02 +08:00
|
|
|
- name: Run bindings example on ${{ matrix.os }}
|
2020-09-10 23:32:25 +08:00
|
|
|
run:
|
|
|
|
python bindings/python/google_benchmark/example.py
|