| commit | d88235336e00158d4fd3179c68288d4146545113 | [log] [tgz] |
|---|---|---|
| author | Armando Montanez <amontanez@google.com> | Wed Jun 05 17:01:58 2024 -0700 |
| committer | Armando Montanez <amontanez@google.com> | Wed Jun 05 17:08:47 2024 -0700 |
| tree | d2a3a8f711e9e92eb01ffaa30f1852d38f20fa31 | |
| parent | d397e0702a346d9a8fddea2947d685089d4474f9 [diff] |
Add defines required for older versions of libusb on Linux Change-Id: I249825d933ef3677f1aae2e0ab00c84ac6d43b33
A small wrapper Bazel module that builds libusb from sources. Supports Windows, macOS, and Linux.
At this time, rules_libusb only supports bzlmod projects. Legacy WORKSPACE projects are not explicitly supported.
Add rules_libusb to your MODULE.bazel file:
bazel_dep(name = "rules_libusb", version="0.1.0-rc1")
libusb = use_extension("@rules_libusb//:extensions.bzl", "libusb")
# Versioning constraints are optional.
libusb.source_release(min_version = "1.0.27")
use_repo(libusb, "libusb")
Note: source_release constraints follow bzlmod behavior of minimal version selection.
Then add to the tool that requires libusb:
cc_binary(
name = "my_tool",
srcs = ["main.cpp"],
deps = ["@libusb//:libusb"],
)
The libusb build file offers two targets to help guide link behavior:
//:libusb: The generic cc_library for libusb. Most build targets should just use this.//:libusb_dynamic: The actual libusb dynamic/shared library (e.g. libusb-1.0.so).By default, @libusb//:libusb will always dynamically link. This can be disabled by toggling the flag that controls this:
bazel build //... --@rules_libusb//:force_dynamic_linkage=False
When @rules_libusb//:force_dynamic_linkage is disabled, the link behavior is fully controlled by your build system, and can be controlled on a per-binary basis by specifying dynamic_deps on build targets that require dynamic linkage of libusb:
cc_binary(
name = "my_tool",
srcs = ["main.cpp"],
deps = ["@libusb//:libusb"],
dynamic_deps = ["@libusb//:libusb_dynamic"],
)
To build this repo, run:
bazel build @libusb//:libusb