Skip to content

Provide target-cpu and target-features to buildscripts #7828

@lukaslueg

Description

@lukaslueg

As far as I can see there is no reliable way for a buildscript to determine the value of target-cpu and target-features. Could we add and env-flag for Cargo to provide the values that will be used when the final crate is compiled for the target platform?

Downstream feature request from here

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions