# build: allow specifying rpaths explicitly \(\#8912\) · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/c0aa9292bafa1a10c43297d3d5929049fab84e9a)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: c0aa9292bafa1a10c43297d3d5929049fab84e9a

Requested commit: c0aa9292bafa1a10c43297d3d5929049fab84e9a

Commit: c0aa9292bafa1a10c43297d3d5929049fab84e9a

Tree: b0efded728c8580f086557b05f83faa6b0505074

Author: Jakub Konka

Committer: GitHub

## Message

```
build: allow specifying rpaths explicitly (#8912)

It currently looks like that if the user links in a dylib using
`lib_or_exe.linkSystemLibrary`, and the linked lib doesn't have
a hardcoded path in its description load command but rather it
allows for any runtime path via `@rpath`, then it is not possible
to specify the runtime path explicitly using the build system.
```

## Parents

- [ec10595b65490126e1b7d231f655be6d7d198acf](https://git.cafe/gitcafe/zig/commit/ec10595b65490126e1b7d231f655be6d7d198acf?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/c0aa9292bafa1a10c43297d3d5929049fab84e9a?format=markdown)