Kaizen/external/fmt/support/bazel
2024-09-22 15:18:54 +02:00
..
.bazelversion Merge commit '2abfcd02f1868bc12b5b0934101d2845c41e3cf5' into dev 2024-09-22 15:18:54 +02:00
BUILD.bazel Merge commit '2abfcd02f1868bc12b5b0934101d2845c41e3cf5' into dev 2024-09-22 15:18:54 +02:00
MODULE.bazel Merge commit '2abfcd02f1868bc12b5b0934101d2845c41e3cf5' into dev 2024-09-22 15:18:54 +02:00
README.md Merge commit '2abfcd02f1868bc12b5b0934101d2845c41e3cf5' into dev 2024-09-22 15:18:54 +02:00
WORKSPACE.bazel Merge commit '2abfcd02f1868bc12b5b0934101d2845c41e3cf5' into dev 2024-09-22 15:18:54 +02:00

Bazel support

To get Bazel working with {fmt} you can copy the files BUILD.bazel, MODULE.bazel, WORKSPACE.bazel, and .bazelversion from this folder (support/bazel) to the root folder of this project. This way {fmt} gets bazelized and can be used with Bazel (e.g. doing a bazel build //... on {fmt}).

Using {fmt} as a dependency

Using Bzlmod

The Bazel Central Registry provides support for {fmt}.

For instance, to use {fmt} add to your MODULE.bazel file:

bazel_dep(name = "fmt", version = "10.2.1")

Live at head

For a live-at-head approach, you can copy the contents of this repository and move the Bazel-related build files to the root folder of this project as described above and make use of local_path_override, e.g.:

local_path_override(
    module_name = "fmt",
    path = "../third_party/fmt",
)