4ad7069827
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.
|
||
|---|---|---|
| .. | ||
| benches | ||
| bpf | ||
| cargo-build-bpf | ||
| cargo-test-bpf | ||
| docker-solana | ||
| macro | ||
| program | ||
| src | ||
| .gitignore | ||
| Cargo.toml | ||
| README.md | ||
| Xargo.toml | ||
| build.rs | ||
README.md
Solana SDK
Use the Solana SDK Crate to write client side applications in Rust. If writing on-chain programs, use the Solana Program Crate instead.
More information about Solana is available in the Solana documentation.
The Solana Program Library provides examples of how to use this crate.
Still have questions? Ask us on Discord