paths
Utilities for working with file paths.
Macros and Functions
relative_file
Resolves a relative path between two files, "to_file" and "frm_file".
If neither of the paths begin with ../ it is assumed that they share the same root. When finding the relative path, the incoming files are treated as actual files (not folders) so the resulting relative path may differ when compared to passing the same arguments to python's "os.path.relpath()" or NodeJs's "path.relative()".
For example, 'relative_file("../foo/foo.txt", "bar/bar.txt")' will return '../../foo/foo.txt'
Example usage (generated):
load("@aspect_bazel_lib//lib:paths.bzl", "relative_file")
relative_file(
# the path with file name to resolve to, from frm
to_file = "",
# the path with file name to resolve from
frm_file = "",
)
to_file
Required.
the path with file name to resolve to, from frm
frm_file
Required.
the path with file name to resolve from
to_output_relative_path
The relative path from bazel-out/[arch]/bin to the given File object
Example usage (generated):
load("@aspect_bazel_lib//lib:paths.bzl", "to_output_relative_path")
to_output_relative_path(
# a `File` object
file = "",
)
file
Required.
a File
object
to_repository_relative_path
The repository relative path for a File
This is the full runfiles path of a File
excluding its workspace name.
This differs from root path (a.k.a. short_path) and
rlocation path as it does not include the repository name if the File
is from an external repository.
Example usage (generated):
load("@aspect_bazel_lib//lib:paths.bzl", "to_repository_relative_path")
to_repository_relative_path(
# a `File` object
file = "",
)
file
Required.
a File
object
to_rlocation_path
The rlocation path for a File
This produces the same value as the rlocationpath
predefined source/output path variable.
From https://bazel.build/reference/be/make-variables#predefined_genrule_variables:
rlocationpath
: The path a built binary can pass to theRlocation
function of a runfiles library to find a dependency at runtime, either in the runfiles directory (if available) or using the runfiles manifest.
This is similar to root path (a.k.a. short_path) in that it does not contain configuration prefixes, but differs in that it always starts with the name of the repository.
The rlocation path of a
File
in an external repository repo will start withrepo/
, followed by the repository-relative path.
Passing this path to a binary and resolving it to a file system path using the runfiles libraries is the preferred approach to find dependencies at runtime. Compared to root path, it has the advantage that it works on all platforms and even if the runfiles directory is not available.
Example usage (generated):
load("@aspect_bazel_lib//lib:paths.bzl", "to_rlocation_path")
to_rlocation_path(
# starlark rule execution context
ctx = None,
# a `File` object
file = "",
)
ctx
Required.
starlark rule execution context
file
Required.
a File
object