support/download/cargo-post-process: make manifest path configurable
In most pure Rust packages, the Cargo.toml manifest is at the root directory, which is why we could call "cargo vendor" without specifying the path of the manifest. However, other packages, such as python-cryptography, which have parts implemented in Rust, have their Cargo.toml located in a specific subdirectory. This commit extends the cargo-post-process download script to understand a BR_CARGO_MANIFEST_PATH environment variable, which allows a package to pass the location of the Cargo.toml file. If not passed, "Cargo.toml" is used, preserving the existing behavior for other packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This commit is contained in:
parent
b0a7bffad9
commit
36e8743da1
@ -22,7 +22,7 @@ post_process_unpack "${base_name}" "${output}"
|
||||
|
||||
# Do the Cargo vendoring
|
||||
pushd "${base_name}" > /dev/null
|
||||
cargo vendor --locked VENDOR
|
||||
cargo vendor --manifest-path ${BR_CARGO_MANIFEST_PATH-Cargo.toml} --locked VENDOR
|
||||
|
||||
# Create the local .cargo/config with vendor info
|
||||
mkdir -p .cargo/
|
||||
|
Loading…
Reference in New Issue
Block a user