From bd4ca0b95ff9e8c5d6c9c3741e0d4d5131df5cfa Mon Sep 17 00:00:00 2001 From: brandjon Date: Mon, 5 Aug 2019 00:18:10 -0700 Subject: [PATCH] Add convention for location of standard runfiles library. hlopko@ approved this suggested convention before he left. It's consistent with what we already do in @bazel_tools. RELNOTES: None PiperOrigin-RevId: 261629882 --- site/docs/skylark/deploying.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/site/docs/skylark/deploying.md b/site/docs/skylark/deploying.md index 63dde22e906864..881fe7bca60b8d 100644 --- a/site/docs/skylark/deploying.md +++ b/site/docs/skylark/deploying.md @@ -49,6 +49,9 @@ For example, suppose we are writing new rules for the (make-believe) mockascript/ constraints/ BUILD + runfiles/ + BUILD + runfiles.mocs BUILD defs.bzl tests/ @@ -150,6 +153,13 @@ using [selects](https://docs.bazel.build/versions/master/be/functions.html#selec With custom constraints, you define a language that the whole Bazel ecosystem will speak. +### Runfiles library + +If your rule provides a standard library for accessing runfiles, it should be +in the form of a library target located at `///runfiles` (an abbreviation +of `///runfiles:runfiles`). User targets that need to access their data +dependencies will typically add this target to their `deps` attribute. + ### Repository Rules #### Dependencies