Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

Support setting environment variables for a given tarball. #93

Open
epage opened this issue Dec 11, 2018 · 2 comments
Open

Support setting environment variables for a given tarball. #93

epage opened this issue Dec 11, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@epage
Copy link
Contributor

epage commented Dec 11, 2018

For use cases, see https://github.com/rust-lang-nursery/cli-wg/issues/34

An open question on this is if we need per-target-triplet environment variables or will people be defining separate cargo-tarball configurations for other platforms.

@kornelski
Copy link

kornelski commented Dec 11, 2018

I need OS-specific config, like whether a zlib-sys crate should be dynamic or static (dynamic on macOS, static on Linux-musl and Windows).

I need the +crt-static flag on Windows only (macOS doesn't have a stable kernel ABI, so it can't have a static runtime).

I also have per-OS per-machine env vars I have to set, but I'm not sure if they belong to cargo-tarball. For example, I build my own copy of LLVM, and clang-sys needs to know file path to it. This will be subtly broken if I forget to set that env var, so I'd really like to have that automated and guaranteed somewhere.

@epage
Copy link
Contributor Author

epage commented Dec 11, 2018

To be clear on expectations, I'm focusing a lot atm on getting Liquid into a solid state. After that, I'll continue to round out stager which builds on liquid. I'll then round out cargo-tarball which customizes stager for the specific distribution method.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants