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

bindgen: C javadoc comments are not Markdown-escaped, triggering rustdoc warnings #323

Open
ojeda opened this issue May 29, 2021 · 4 comments
Labels
• misc Related to other topics (e.g. CI).

Comments

@ojeda
Copy link
Member

ojeda commented May 29, 2021

Example from the CI: https://github.com/Rust-for-Linux/linux/runs/2700777736?check_suite_focus=true#step:60:35.

Reported at rust-lang/rust-bindgen#2057.

@nbdd0121
Copy link
Member

Do we need these comments? We can just --no-doc-comments.

@ojeda
Copy link
Member Author

ojeda commented May 29, 2021

I guess not, though I thought it would be nice to report it to the bindgen folks.

We can mark this as a GFI then if we go for that.

@pvdrz
Copy link

pvdrz commented Nov 28, 2022

Now bindgen has a parse callback to handle commands but this requires using a build script and AFAIK rust-for-linux uses the CLI instead. Would it be possible to move to using a build script?

@ojeda
Copy link
Member Author

ojeda commented Nov 28, 2022

If you mean using it as a library, then yeah, it would be possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
• misc Related to other topics (e.g. CI).
Development

No branches or pull requests

3 participants