These are chat archives for rust-lang/rust
--message-format=jsonand look for
cargo outputto print out expected results would work
cargo metadataas a subprocess and get all info as json
foomay end up in
target/releaseor perhaps elsewhere, if we add custom profiles.
message-formatJSON requires that you execute the actual build.
metadatagives you the names of the artifacts (
target), but it does not give you paths.
what package I am compilingagain depends on how exactly you execute cargo. You may invoke
cargo build -p, or
cargo build --all
name-version-paththing is an "opaque" id)
ibm-cloud-rust-web-template 0.0.1 (path+file:///C:/Users/huhlig/Projects/rust/ibm-cloud-rust-web-template)<- this is the id
--outputflag to Cargo, to make such stuff easier?
--message-format=jsonare actually awesome, because they give you very detailed information. But they are absolutely impossible to use from a bash script.
cargo run --releaseas my command except after compilation the compiler isn't included in the container for space reasons