-
Notifications
You must be signed in to change notification settings - Fork 347
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
Automatically build libstd #543
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not very up to date on the cli working group things, but I think they are at a point where it might make sense to look at the best practices and crates for writing cli tools. Not a blocker for this PR, feel free to punt to an issue and assign to me
} | ||
// The interesting bit: Xargo.toml | ||
File::create(dir.join("Xargo.toml")).unwrap() | ||
.write_all(br#" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe put these into files in a separate directory and use include_bytes!
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You think that's worth it? They are rather short.
Done: #546 |
45d4ea6
to
07f78a3
Compare
needs a rebase r=me with nit fixed |
Uh... which directory will this be on Windows? We need to know for CI.^^ |
1bc88e0
to
27ac0c5
Compare
Uh... now the path is different on Linux and macOS, and travis needs to know that. :/ |
ce856d7
to
fbd7d11
Compare
Cc #520