| commit | 6301f974f02350fe973d8631cf1bb87ab8d2a2bd | [log] [tgz] |
|---|---|---|
| author | oquenchil <23365806+oquenchil@users.noreply.github.com> | Wed Jun 27 10:22:33 2018 +0200 |
| committer | GitHub <noreply@github.com> | Wed Jun 27 10:22:33 2018 +0200 |
| tree | 72b04e54aaf97e1d6680181919d10c9bbec70e48 | |
| parent | 3fea8cb680f4a53a129f7ebace1a5a4d1e035914 [diff] |
Makes package public by default When creating a skylark_library A anywhere downstream, if a bzl file in A loads() any of the bzl libraries in this package, then the bzl files in this package will have to be in deps as a skylark_library. The current public filegroup cannot be used as a dependency of skylark_libraries.
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.
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:
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) from lib.bzl and access the symbols by dotting into those structs:
load("@bazel_skylib//:lib.bzl", "paths", "shell") p = paths.basename("foo.bar") s = shell.quote(p)
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 a line to lib.bzl to make the new module accessible from the index:
load("@bazel_skylib//lib:things.bzl", "things")
Clients can then use the module by loading it from lib.bzl:
load("@bazel_skylib//:lib.bzl", "things") things.manipulate()
Add unit tests for your module in the tests directory.
skylark_libraryThe 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.