And `Rlocation` requires a **path** relative to the runfiles directory.
Also note that the file path includes the repository name, which in the case of unnamed repositories is `_main`. Now, that's not documented in the docs for `Rlocation`, but follows from the ability to refer to runfiles that come from external repos.
I am not sure I would recommend using Rlocation this way, since things may get messed up if this repo is being used as an external repo of another project. Perhaps some of the bazel folks could chime in and explain the intention here.
There is a much easier way to get at the rlocation of this file, which is to do something like this:
```
cc_binary(
name = "example_bin",
...
args = [
"$(location //example_bin/data:Roboto-Black.ttf)",
]
data = [
"//example_bin/data:Roboto-Black.ttf",
],
```
This gives you the path of the file in `argv[1]` once example runs, which isn't very elegant but removes the need for the `runfiles` library.
I also fixed the `glob(...)` call.
In general I recommend scrutinizing the documentation a bit more closely. There's plenty of undocumented tidbits as it is now, but what is documented is usually very important. It's all part of a learning process.
HTH,
F