README: Copy splat documentation and describe --output
#96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It took a while to figure out how to use this tool, when it's not immediately obvious from the readme alone that `xwin splat --output` is the command that most users will likely want to use to extract all the headers, after which they are ready to cross-compile with MSVC.
Jake-Shadle
approved these changes
Sep 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It took a while to figure out how to use this tool, when it's not immediately obvious from the readme alone that
xwin splat --outputis the command that most users will likely want to use to extract all the headers, after which they are ready to cross-compile with MSVC.Note that I have added the setup from the blog /
xwin.dockerfilelocally to my~/.cargo/config.tomlvia[env]and[target.x86_64-pc-windows-msvc]. The[env]obviously only works for C/C++ code compiled within Rust /cargoprojects and not system-wide, but for example settingrustflagsvia[target.*]allows it to be merged with other target-specificrustflagsin project-specific./.cargo/config.tomlrather than being mutually exlusive with theRUSTFLAGSenv var: https://doc.rust-lang.org/cargo/reference/config.html#buildrustflags. Is it worth documenting this setup somewhere?