Skip to content

Fix use in multi-config builds that don't target glibc #208

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

Closed
wants to merge 1 commit into from

Conversation

tronical
Copy link

Building for a BeaglePlay with meta-ti yields a multi-config build, where some of the images built are for the regular (glibc) based Linux, and some images are for bare-metal environment.

In that bare-metal environment, TARGET_OS is set to "eabi":

meta/conf/distro/include/tclibc-baremetal.inc:TARGET_OS:arm = "eabi"

This makes meta-rust-bin abort fatally.

This patch proposes a more graceful handling by skipping such recipes, instead of aborting the entire build, including the images where TARGET_OS is set to Linux. This also appears to be inline with how other recipes in oe-core handle this.

Building for a BeaglePlay with meta-ti yields a multi-config build,
where some of the images built are for the regular (glibc) based Linux,
and some images are for bare-metal environment.

In that bare-metal environment, TARGET_OS is set to "eabi":

    meta/conf/distro/include/tclibc-baremetal.inc:TARGET_OS:arm = "eabi"

This makes meta-rust-bin abort fatally.

This patch proposes a more graceful handling by skipping such recipes,
instead of aborting the entire build, including the images where
TARGET_OS is set to Linux. This also appears to be inline with how other
recipes in oe-core handle this.
@tronical
Copy link
Author

Whoops, I see this duplicates #202 and ends up with exactly the same change by accident :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant