Common useful functions and rules for Bazel
Go to file
Thomas Van Lenten 2d356cf857 Doc and code fixes found via skylint. (#38)
* Fix up the skylint warning about depset usage.

* Remove the reassignment of max_bazel_version.

This was flagged by skylint, the reality is _is_at_most() does the parsing
so it shouldn't be parsed before sent on the way.

* Fix up the skylint warning about depset usage.

* Fixup the skylint warning about re-exports.

Just move to the explicit re-export form.

* Fix the fail() call to use the right variable.

skylint flagged this variable as undefined, but it it seems like this
was never right and should have been "key" all along.

* Fixup docstring formatting for skylint.
2018-04-26 12:08:01 -04:00
.bazelci add buildkite to bazel's new ci 2018-02-28 08:31:03 -08:00
lib Doc and code fixes found via skylint. (#38) 2018-04-26 12:08:01 -04:00
tests Introduce new_sets.bzl (#32) 2018-04-20 14:44:25 -07:00
.gitignore Add initial .gitignore with bazel-* folders 2017-10-31 07:04:27 -07:00
.travis.yml Move to Xcode 9.3 which also means a High Sierra image. (#37) 2018-04-20 13:00:15 -07:00
.travis_build.sh Drop the rc file flag. 2018-03-14 13:37:28 -04:00
.travis_install.sh Test HEAD bazel on travis. 2018-03-01 09:17:31 -05:00
AUTHORS Fix grammar. 2018-02-20 16:53:50 -05:00
BUILD Introduce new_sets.bzl (#32) 2018-04-20 14:44:25 -07:00
CONTRIBUTING.md Initial check-in. 2017-10-10 07:59:31 -07:00
CONTRIBUTORS Add support for 'functools.partial' like functionality. (#34) 2018-04-17 09:33:38 -07:00
LICENSE Initial check-in. 2017-10-10 07:59:31 -07:00
README.md Fix the buildkite link. 2018-02-28 13:53:36 -05:00
WORKSPACE Initial check-in. 2017-10-10 07:59:31 -07:00
lib.bzl Doc and code fixes found via skylint. (#38) 2018-04-26 12:08:01 -04:00
skylark_library.bzl Doc and code fixes found via skylint. (#38) 2018-04-26 12:08:01 -04:00

README.md

Skylib

Build Status 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. 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:

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)

List of modules

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 a line to lib.bzl to make the new module accessible from the index:

    load("@bazel_skylib//lib:things.bzl", "things")
    
  5. Clients can then use the module by loading it from lib.bzl:

    load("@bazel_skylib//:lib.bzl", "things")
    
    things.manipulate()
    
  6. 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.