diff options
author | Doron Behar <doron.behar@gmail.com> | 2021-12-08 18:59:38 +0200 |
---|---|---|
committer | Doron Behar <doron.behar@gmail.com> | 2021-12-08 18:59:38 +0200 |
commit | 32d566e1b9d9ff55ec5b013d5420419649780e0d (patch) | |
tree | 91e7fd14cd4b23f2e62f0bb51b681898e542e912 /doc | |
parent | 7cf1aa102a513ad7df9c6e6c0e57254b2f44efaf (diff) |
wrapProgramBinary -> binaryWrapProgram
Diffstat (limited to 'doc')
-rw-r--r-- | doc/stdenv/stdenv.chapter.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/stdenv/stdenv.chapter.md b/doc/stdenv/stdenv.chapter.md index 91e59bbce48e..bd9d9e1e3689 100644 --- a/doc/stdenv/stdenv.chapter.md +++ b/doc/stdenv/stdenv.chapter.md @@ -796,7 +796,7 @@ A setup-hook very similar to `makeWrapper`, only it creates a tiny _compiled_ wr Compiled wrappers generated by `makeBinaryWrapper` can be inspected with `less <path-to-wrapper>` - by scrolling past the binary data you should be able to see the C code that generated the executable and there see the environment variables that were injected into the wrapper. -Similarly to `wrapProgram`, the `makeBinaryWrapper` setup-hook provides a `wrapProgramBinary` with similar command line arguments. +Similarly to `wrapProgram`, the `makeBinaryWrapper` setup-hook provides a `binaryWrapProgram` with similar command line arguments. ### `substitute` \<infile\> \<outfile\> \<subs\> {#fun-substitute} @@ -875,7 +875,7 @@ Convenience function for `makeWrapper` that replaces `<\executable\>` with a wra If you will apply it multiple times, it will overwrite the wrapper file and you will end up with double wrapping, which should be avoided. -### `wrapProgramBinary` \<executable\> \<makeBinaryWrapperArgs\> {#fun-wrapProgramBinary} +### `binaryWrapProgram` \<executable\> \<makeBinaryWrapperArgs\> {#fun-binaryWrapProgram} Convenience function for `makeBinaryWrapper` that replaces `<\executable\>` with a wrapper that executes the original program. It takes all the same arguments as `makeBinaryWrapper`, except for `--argv0`. |