On Mon, 24 Oct 2022 at 19:10, Anton Antonov <anton.anto...@arm.com> wrote:
> To fix the issue in our recipe we can define “CRATE_CC_NO_DEFAULTS” env > variable which disables adding compiler flags in "cc-rs": > https://github.com/rust-lang/cc-rs#external-configuration-via-environment-variables > So, my questions is: shouldn’t “CRATE_CC_NO_DEFAULTS” be defined in the > Rust bbclass instead of expecting that owners of all Rust apps recipes would > be aware about this issue for some machines and would add workarounds in > their recipes? > I've tried to add "CRATE_CC_NO_DEFAULTS" into rust-target-config.bbclass, > but it breaks building rust-native. Looks like we don’t define all the > required parameters for native builds and rely (maybe not even intentionally) > on parameters defined by cc-rs crate. Therefore to do it properly there > should be some logic around defining of "CRATE_CC_NO_DEFAULTS" in > rust-target-config.bbclass. I would be happy to hear ideas or recommendations. I'd suggest you discuss the issue with cc-rs upstream first. Historically, we don't want components making guesses about target-specific compiler flags, and end up disabling or overriding them, so that compiler output is consistent across the whole build. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#172115): https://lists.openembedded.org/g/openembedded-core/message/172115 Mute This Topic: https://lists.openembedded.org/mt/94539875/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
