History

Kenta Iwasaki 4ad7069827 cargo-build-bpf: allow sdk path to be set by environment variables

In many Linux distros such as NixOS, the directory in which packages are
installed is assumed to be read-only. To work around this, it is
expected that the filepaths which packaged CLI tools take in are able to
be freely configured through either 1) command-line flags, 2)
environment variables, or 3) a configuration file.

In this commit, environment variables 'BPF_SDK_PATH' and 'BPF_OUT_PATH',
which map respectively to command-line flags '--bpf-sdk-path' and
'--bpf-out-dir', are now handled in cargo-build-bpf.

Additionally, given that arbitrary filepaths may now be set in which the
BPF SDK is located, the requirement in which
'$BPF_SDK_PATH/dependencies/bpf-tools' must strictly be a symbolic link
to the directory '$HOME/.cache/solana/${bpf-tools.version}/bpf-tools has
been relaxed.

Ideally, the directory in which bpf-tools is expected to be downloaded
to and stored should be configurable. Though, this commit serves as a
temporary fix which enables NixOS users to now start being able to build
applications with the Solana SDK.

2021-08-30 23:11:48 +02:00

benches

Store versioned transactions in the ledger, disabled by default (#19139 )

2021-08-17 15:17:56 -07:00

bpf

Split solana_sdk.h (#19172 )

2021-08-13 09:49:24 -07:00

cargo-build-bpf

cargo-build-bpf: allow sdk path to be set by environment variables

2021-08-30 23:11:48 +02:00

cargo-test-bpf

Reword help of generate-child-script-on-failure cargo bpf tools option (#18685 )