-
Notifications
You must be signed in to change notification settings - Fork 151
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
v0.5.1 Output invalid and all on one line with STM32F41x.svd #68
Comments
What svd2rust version were you using? This works for me:
With
No, that's normal (the quasiquoting crate we use under the hood doesn't preserve line breaks and just "inlines" everything). You can run |
I definitely still have problems with I did try patching svdrust to pull in the rustfmt crate and run that before generating output - it's a pretty small change and has generated the |
I find this very odd. Relatively "contemporary" versions of rustfmt and rustc should parse / understand the same syntax. I suppose that apart from rustfmt, calling I wonder if this because you are passing the code to format through rustfmt stdin (could maybe be some problem with your shell / environment / locale) rather than as passing it to rustfmt as a file. Do the steps from my previous comment don't work for you either? |
The unformatted output is expected and the docs recommend piping svd2rust output before writing it to a file. And I can't repro the rustfmt / compilation error with the STM32F41x.svd so I'm going to close this. Feel free to open a new issue (with repro steps) if you hit a compiler error with recent versions of svd2rust / rustc. |
I ran
rustup run nightly cargo install svd2rust
a couple of days ago usingrustc 1.18.0-nightly (40feadb96 2017-03-31)
and then ransvd2rust -i STM32F41x.svd > stm32f415.rs
with STM32F41x.svd.The output was a rust file with all the code on one line:
Trying to
rustfmt
thesvd2rust
output gives an error:Am I correct in thinking the output should have been properly pretty printed (not a giant 7.8M single line)? Is there anything I could look into to figure out why this is happening?
The text was updated successfully, but these errors were encountered: