2
0
Fork 0
mirror of https://github.com/bazelbuild/bazel-skylib synced 2024-11-27 05:43:25 +00:00
Common useful functions and rules for Bazel
Find a file
László Csomor 6bf6443975
write_file: support different line endings (#150)
The user can specify which line endings they want
write_file to use. This helps avoiding line ending
mismatches with diff_test.

Example: diff_test verifies that a rule generates
correct output by comparing it to a checked-in
"golden" file. Both files are text files, and the
user builds on Windows but the golden file was
written on Linux and git checkout preserved
original line endings.

Without explicitly specifying which line endings
to use, this diff_test would fail on an otherwise
good output.

With explicit line endings we don't need to check
in the golden file to git, we can just generate it
with "auto" line endings.
2019-05-09 15:29:44 +02:00
.bazelci e2e tests: make them run on Windows (#121) 2019-03-19 13:37:33 +01:00
docs write_file: support different line endings (#150) 2019-05-09 15:29:44 +02:00
lib Pass through an attribute arguments to analysistest.make. (#140) 2019-05-03 16:24:20 -04:00
rules write_file: support different line endings (#150) 2019-05-09 15:29:44 +02:00
tests write_file: support different line endings (#150) 2019-05-09 15:29:44 +02:00
toolchains/unittest Add basic shell testing for unittest.bzl (#108) 2019-02-11 17:18:56 -05:00
.gitignore Add initial .gitignore with bazel-* folders 2017-10-31 07:04:27 -07:00
AUTHORS Fix grammar. 2018-02-20 16:53:50 -05:00
BUILD Add rules to the test_deps target. (#102) 2019-01-28 13:51:57 -05:00
bzl_library.bzl buildifier lint issues/validation 2018-11-21 13:04:25 -05:00
CODEOWNERS Create CODEOWNERS (#103) 2019-02-14 20:24:00 +01:00
CONTRIBUTING.md Initial check-in. 2017-10-10 07:59:31 -07:00
CONTRIBUTORS add cparsons and bttk to the CONTRIBUTORS file (#73) 2018-11-20 15:19:06 -05:00
lib.bzl Fix up lint issues. (#77) 2018-11-26 17:31:29 -05:00
LICENSE Initial check-in. 2017-10-10 07:59:31 -07:00
README.md Fix installation instructions (#135) 2019-04-05 13:18:40 +02:00
skylark_library.bzl Update to google style (#63) 2018-11-12 12:42:57 -08:00
WORKSPACE run buildifier 0.22.0 (#125) 2019-03-07 17:22:04 -05:00
workspace.bzl add missing license notices (#94) 2019-01-14 16:00:11 -05:00

Skylib

Build status

Skylib is a standard library that provides functions useful for manipulating collections, file paths, and other features that are useful when writing custom build rules in Bazel.

This library is currently under early development. Be aware that the APIs in these modules may change during this time.

Each of the .bzl files in the lib directory defines a "module"—a struct that contains a set of related functions and/or other symbols that can be loaded as a single unit, for convenience.

Skylib also provides build rules under the rules directory.

Getting Started

WORKSPACE file

Add the following to your WORKSPACE file to import the Skylib repository into your workspace. Replace the version number in the tag attribute with the version you wish to depend on:

# bazel-skylb 0.8.0 released 2019.03.20 (https://github.com/bazelbuild/bazel-skylib/releases/tag/0.8.0)
skylib_version = "0.8.0"
http_archive(
    name = "bazel_skylib",
    type = "tar.gz",
    url = "https://github.com/bazelbuild/bazel-skylib/releases/download/{}/bazel-skylib.{}.tar.gz".format (skylib_version, skylib_version),
    sha256 = "2ef429f5d7ce7111263289644d233707dba35e39696377ebab8b0bc701f7818e",
)

If you want to use lib/unittest.bzl from Skylib versions released in or after December 2018, then you also should add to the WORKSPACE file:

load("@bazel_skylib//:workspace.bzl", "bazel_skylib_workspace")

bazel_skylib_workspace()

BUILD and *.bzl files

Then, in the BUILD and/or *.bzl files in your own workspace, you can load the modules (listed below) and access the symbols by dotting into those structs:

load("@bazel_skylib//lib:paths.bzl", "paths")
load("@bazel_skylib//lib:shell.bzl", "shell")

p = paths.basename("foo.bar")
s = shell.quote(p)

List of modules (in lib/)

List of rules (in rules/)

Writing a new module

Steps to add a module to Skylib:

  1. Create a new .bzl file in the lib directory.

  2. Write the functions or other symbols (such as constants) in that file, defining them privately (prefixed by an underscore).

  3. Create the exported module struct, mapping the public names of the symbols to their implementations. For example, if your module was named things and had a function named manipulate, your things.bzl file would look like this:

    def _manipulate():
      ...
    
    things = struct(
        manipulate=_manipulate,
    )
    
  4. Add unit tests for your module in the tests directory.

bzl_library

The bzl_library.bzl rule can be used to aggregate a set of Starlark files and its dependencies for use in test targets and documentation generation.

Troubleshooting

If you try to use unittest and you get the following error:

ERROR: While resolving toolchains for target //foo:bar: no matching toolchains found for types @bazel_skylib//toolchains:toolchain_type
ERROR: Analysis of target '//foo:bar' failed; build aborted: no matching toolchains found for types @bazel_skylib//toolchains:toolchain_type

then you probably forgot to load and call bazel_skylib_workspace() in your WORKSPACE file.