commit | e5cf5398cd3e01d5552ed1056aafc06f92adb374 | [log] [tgz] |
---|---|---|
author | aiuto <aiuto@google.com> | Fri Oct 04 14:55:59 2019 -0400 |
committer | GitHub <noreply@github.com> | Fri Oct 04 14:55:59 2019 -0400 |
tree | 57902eb105ef60e84cdce0ad1ac4d29ff6726b29 | |
parent | f1475299afd41815c78c3768253468ea622669f3 [diff] |
Update version and changelog in prep for 1.0.0 release (#196) * -Update changelog to get ready for release 1.0 -Change README to point to releases page for WORKSPACE setup. Otherwise the readme shipped in the archive can never be in sync with the readme that has the correct sha256. * update incompatible changes * -Update changelog to get ready for release 1.0 -Change README to point to releases page for WORKSPACE setup. Otherwise the readme shipped in the archive can never be in sync with the readme that has the correct sha256. * fix wording of changelog * remove false file
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.
WORKSPACE
fileSee the WORKSPACE setup section for the current release.
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
filesThen, 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)
new_sets
Steps to add a module to Skylib:
Create a new .bzl
file in the lib
directory.
Write the functions or other symbols (such as constants) in that file, defining them privately (prefixed by an underscore).
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, )
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.
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.