Treat \ in cargo package -l output as /#213
Merged
Byron merged 1 commit intorust-lang:mainfrom Sep 6, 2024
Merged
Conversation
This was referenced Sep 5, 2024
Byron
approved these changes
Sep 6, 2024
Member
Byron
left a comment
There was a problem hiding this comment.
Thanks a lot! I really like the reformatting of the long line into easily consumable pieces!
Contributor
Author
I tend to like to do this for long pipelines, especially when they have more than two parts. But in this case it seemed valuable beyond being my own stylistic preference, since I was making an already-long command even longer by adding the |
This file contains hidden or 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
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.
Fixes #212
tr-ing the\characters to/in the output ofcargo package -lmakes thetarpipeline work and allows the build to succeed on Windows, presumably since files needed bycmakeare now available:(Those warnings are separate from this change and also occur without it on other systems and with
cargo build.)I tested on Ubuntu 24.04 LTS and macOS 14.6, and this change does not seem to have broken or degraded them. I noticed this on macOS, but it also happens on macOS on the main branch and thus appears independent of this change:
Since that appears altogether separate from this, I've opened #214 for it.
In all tests, I used
cargo clean -xdebetween the build (though I think actually no cleaning is really needed, since a temporary directory is used and it is different each time). To make sure this really was fixing the build on Windows, I re-cloned the repository and retested as well.The only commands I have tested are
./cargo-zngand./cargo-zng build. I have not tested publishing.