1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
# Skylib
[](https://travis-ci.org/bazelbuild/bazel-skylib)
[](https://buildkite.com/bazel/bazel-skylib)
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. The top-level file `lib.bzl` acts
as an index from which the other modules can be imported.
## Getting Started
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:
```python
git_repository(
name = "bazel_skylib",
remote = "https://github.com/bazelbuild/bazel-skylib.git",
tag = "0.1.0", # change this to use a different release
)
```
Then, in the `BUILD` and/or `*.bzl` files in your own workspace, you can load
the modules (listed [below](#list-of-modules)) from `lib.bzl` and access the
symbols by dotting into those structs:
```python
load("@bazel_skylib//:lib.bzl", "paths", "shell")
p = paths.basename("foo.bar")
s = shell.quote(p)
```
## List of modules
* [collections](lib/collections.bzl)
* [dicts](lib/dicts.bzl)
* [paths](lib/paths.bzl)
* [selects](lib/selects.bzl)
* [sets](lib/sets.bzl)
* [shell](lib/shell.bzl)
* [unittest](lib/unittest.bzl)
* [versions](lib/versions.bzl)
## Writing a new module
Steps to add a module to Skylib:
1. Create a new `.bzl` file in the `lib` directory.
1. Write the functions or other symbols (such as constants) in that file,
defining them privately (prefixed by an underscore).
1. 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:
```python
def _manipulate():
...
things = struct(
manipulate=_manipulate,
)
```
1. Add a line to `lib.bzl` to make the new module accessible from the index:
```python
load("@bazel_skylib//lib:things.bzl", "things")
```
1. Clients can then use the module by loading it from `lib.bzl`:
```python
load("@bazel_skylib//:lib.bzl", "things")
things.manipulate()
```
1. Add unit tests for your module in the `tests` directory.
## `skylark_library`
The `skylark_library.bzl` rule can be used to aggregate a set of
Skylark files and its dependencies for use in test targets and
documentation generation.
|
