-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Is rustc --emit=<type>=<path>
supported?
#30204
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
Comments
(or is it somehow meant to be used as an input filename? ) |
Yeah this was added recently to make We've also got what I was hoping was a pretty exhaustive test for this sort of functionality, and when I run When you say that it doesn't work, what sort of behavior did you see? |
@alexcrichton oh maybe I wasn't testing against nightly; let me double check |
@alexcrichton I think I know the problem: I'm using Update: /me goes off to review what |
Oh weird, I would expect getopts to consider those two equivalent... I wonder if there's a bug in getopts? |
@alexcrichton yes I think it is, I just saw something suspicious; look here: https://github.com/rust-lang/rust/blob/master/src/libgetopts/lib.rs#L605 (I bet the Update: Yeah, compare it against the version that is hosted on crates.io, which does use https://github.com/rust-lang-nursery/getopts/blob/master/src/lib.rs#L338 |
Ah yep that'd do it! |
I'm cherry-picking rust-lang/getopts@8ec916b as we speak. :) |
…ichton Fix internal `getopts` so `--a=b=c` acts like `--a b=c` rather than `--a b`. Fix #30204
There seems to be code hanging around to support a variant of
--emit
of the form--emit=<type>=<path>
.Its not clear what it is supposed to do.
I suspect it was meant to be a way to indicate a specific file name to use for an output (so that one could do e.g.
rustc --emit asm=bar.s --emit obj foo.rs
to get machine code infoo.o
(inferred) and assembly inbar.s
(explicitly specified).But if that's the intention, it does not seem to work currently. (Which is fine because the option is undocumented anyway.)
The text was updated successfully, but these errors were encountered: