| commit | 16ed1b8f308d2b3dec9d7e6decaad49ce4d28b43 | [log] [tgz] |
|---|---|---|
| author | Ryan Butler <thebutlah@gmail.com> | Mon May 04 00:28:02 2020 -0400 |
| committer | GitHub <noreply@github.com> | Sun May 03 21:28:02 2020 -0700 |
| tree | 97ceb29dab4ce02596cdc5b832d5a96a0760b326 | |
| parent | 34206c29f891dbd5f6f5face7b91664c2ff7185c [diff] |
Allow the python extension to be built by wildcards (#13) Removed manual tag Co-authored-by: chuckx <chuckx@cold-sun.com>
Provided rules:
pybind_extension: Builds a python extension, automatically adding the required build flags and pybind11 dependencies. It defines a *.so target which can be included as a data dependency of a py_* target.pybind_library: Builds a C++ library, automatically adding the required build flags and pybind11 dependencies. This library can then be used as a dependency of a pybind_extension. The arguments match a cc_library.pybind_library_test: Builds a C++ test for a pybind_library. The arguments match a cc_test.To test a pybind_extension, the most common approach is to write the test in python and use the standard py_test build rule.
In your WORKSPACE file:
http_archive( name = "pybind11_bazel", strip_prefix = "pybind11_bazel-<stable-commit>", urls = ["https://github.com/pybind/pybind11_bazel/archive/<stable-commit>.zip"], ) # We still require the pybind library. http_archive( name = "pybind11", build_file = "@pybind11_bazel//:pybind11.BUILD", strip_prefix = "pybind11-<stable-version>", urls = ["https://github.com/pybind/pybind11/archive/v<stable-version>.tar.gz"], ) load("@pybind11_bazel//:python_configure.bzl", "python_configure") python_configure(name = "local_config_python")
Then, in your BUILD file:
load("@pybind11_bazel//:build_defs.bzl", "pybind_extension")