Open nical opened 3 years ago
Hmm, normally that output is captured and hidden, and even cargo build -v
doesn't show anything, but cargo build -v -v
does.
https://github.com/rust-lang/cargo/blob/8e403e5e77e1fb5ebdba3094c5cf424bfc473f9e/src/cargo/core/compiler/custom_build.rs#L353-L370
We could add some debug/verbosity control in autocfg
, redirecting rustc output to null if quiet -- and maybe that should be the default. It would probably need to be an environment variable, so you don't have to edit build scripts to affect this.
Thanks for the quick answer. It looks like Firefox's build uses -vv
intentionally since https://bugzilla.mozilla.org/show_bug.cgi?id=1473121 after some mismatched compiler versions had caused headaches.
I would greatly appreciate if autocfg
was quiet by default including in -vv
configurations, or if we could quiet it via an environment viable.
Why did you close?
Maybe I misunderstood, wasn't this resoved in #32 ?
That's not merged yet though.
My bad, I saw something landing into mozilla-central and thought it was resolved.
Hi,
Firefox's build and CI tooling parses the logs including verbose build script output to find and highlight errors. It helps a lot with quickly figuring out where build problems are, gets false positives from autocfg as it sees the rustc errors generated by attempts at determining if configurations build.
For example this:
Gets picked up in a linux64 build and confuses the tooling.
Is there a way for autocfg to consume the output of rustc in a way that doesn't make it show up the logs of the build that calls into autocfg?