| commit | 9b198d720a7271fa9a8cf5e53c63a6e35d67ce7e | [log] [tgz] |
|---|---|---|
| author | Chris Cummins <chrisc.101@gmail.com> | Thu Apr 09 06:33:07 2020 +0100 |
| committer | GitHub <noreply@github.com> | Wed Apr 08 22:33:07 2020 -0700 |
| tree | fc5924ca7b473a3a32291adb3a34a357beb666a9 | |
| parent | 7f397b5d2cc2434bbd651e096548f7b40c128044 [diff] |
Remove -Bsymolink link option on macOS. (#10) This removes the hardcoded link option -Bsymbolic which is specific to GNU's linker when running on macOS.
Provided rules:
pybind_extension: Builds a python extension, automatically adding the required build flags and pybind11 dependencies. It also defines a .so target which can be manually built and copied. The arguments match a py_extension.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")