Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customization of std #98

Closed
japaric opened this issue Dec 21, 2016 · 0 comments · Fixed by #103
Closed

Customization of std #98

japaric opened this issue Dec 21, 2016 · 0 comments · Fixed by #103

Comments

@japaric
Copy link
Owner

japaric commented Dec 21, 2016

Once #77 is implemented, people are going to ask for a way to customize the std crate (jemalloc vs alloc_system, backtrace or not, etc.).

So, I have been thinking about how to present "customizability" to users and how to solve the problem of nasty build errors, like libc, that are not actual errors.

My idea is to, by default, only build the core crate and have users specify what other dependencies they want + how to customize them via a Xargo.toml file in the root of the Cargo project.

Syntax is undecided but maybe something that looks like Cargo.toml:

# Xargo.toml
[dependencies]
collections = "0"  # NOTE version doesn't actually matter

[dependencies.compiler-builtins]
features = ["mem"]
version = "0"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant