Skip to content

(optionally) emit warning messages from C(++) compiler #81

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
mystor opened this issue May 20, 2016 · 2 comments · Fixed by #91
Closed

(optionally) emit warning messages from C(++) compiler #81

mystor opened this issue May 20, 2016 · 2 comments · Fixed by #91

Comments

@mystor
Copy link
Contributor

mystor commented May 20, 2016

Once rust-lang/cargo#2630 lands, it would be awesome if there was an option to tell gcc-rs to forward the warning messages produced by the c/c++ compiler, but prefixed with cargo:warning=, to the build script's standard out. This would be useful for getting and fixing error messages in C++ and C code which is compiled through the build plugin as a companion to rust code.

@alexcrichton
Copy link
Member

Indeed! I hope to do this by default once that lands

@mystor
Copy link
Contributor Author

mystor commented Aug 19, 2016

In rust 1.11, I believe cargo:warning is now stable. Should we just collect the standard error from the compiler processes, and print anything written to it with each line prefixed with cargo:warning=?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants