- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.9k
Allow codegen backends to indicate which crate types they support #148177
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
Conversation
Previously only --crate-type would be taken into account, not #![crate_type].
| Some changes occurred in compiler/rustc_codegen_ssa | 
| By the way I noticed that if you specify a crate type on the cli and this crate type is not supported by either the target or (with this PR) codegen backend, the crate will be treated as a library, but  | 
This way cargo will drop the unsupported crate types for crates that specify multiple crate types.
4059118    to
    b443a59      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me with green ci and with(out) the nit
554a58d    to
    9fc1378      
    Compare
  
    | @bors r=WaffleLapkin | 
…apkin Allow codegen backends to indicate which crate types they support This way cargo will drop the unsupported crate types for crates that specify multiple crate types. This is a prerequisite for rust-lang/miri#4648.
| @bors retry (yielding to a stable PR) | 
Rollup merge of #148177 - bjorn3:codegen_backend_crate_types, r=WaffleLapkin Allow codegen backends to indicate which crate types they support This way cargo will drop the unsupported crate types for crates that specify multiple crate types. This is a prerequisite for rust-lang/miri#4648.
This way cargo will drop the unsupported crate types for crates that
specify multiple crate types.
This is a prerequisite for rust-lang/miri#4648.