-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Managed and Native RID discovery can resolve different RIDs #33069
Comments
Following components built successfully (with #31701 changes):
managed components of installer failed at the package step, due to the wrong RID ( |
@am11 do you know if there's still work left to do here? Asking as you spent quite a lot of time into consolidating RID logic on at least the managed side. |
Yes, this can be closed. :) The native RID continues to be calculated in For Android, currently it is working but the situation is not ideal as coreclr and mono are using different setups for Android. That requires us to add mysterious conditions and tweaks here and there to make things just work. I opened #56622 for discussion. The rootfs setup done by this script:
|
We currently have two methods of resolving the current build's RID. For native components, we use the
init_distro_rid.sh
script ineng/native
. This script supports discovering RIDs for not-officially-supported distros as well as discovering rids for cross-compilation.The managed RID discovery mechanism only supports discovering the host RID and then overriding it with a specific RID manually. @am11 reported that was causing him issues when building for android, where the native components built correctly for
android.28-arm64
but the managed components were looking forlinux-arm64
.The text was updated successfully, but these errors were encountered: