You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to configure the VCPKGRS_* environmental variables from the Config object exposed by the library, with the library setting overridden by the environment?
This would allow us to manage this for different targets in build.rs, aiming to simplify the build process for *-sys crate consumers.
I'm open to the idea, for sure. I assume you are mainly wanting to select which vcpkg triplet to build with? At the moment I think there is no way to do that but I think it would not be a big deal to support it.
This is now supported from builds.rs as you suggested. It's typically better to use the environment variables because it can be a requirement that all external dependencies come from the same vcpkg installation and use the same triplet.
There is also a new tool cargo vcpkg that allows the triplet and required packages to be specified as metadata in Cargo.toml. If required it will create a vcpkg tree from scratch, so cargo vcpkg build && cargo build can be enough to get up and running.
(Please let me know if this doesn't address your need.)
Hey there,
Would it be possible to configure the
VCPKGRS_*
environmental variables from theConfig
object exposed by the library, with the library setting overridden by the environment?This would allow us to manage this for different targets in
build.rs
, aiming to simplify the build process for*-sys
crate consumers.Somewhat related issue: rust-embedded#481
Cheers,
Ryan
The text was updated successfully, but these errors were encountered: