Repository navigation
Consolidate Android cross-build setup for mono and coreclr #56622
Description
The cross-build in :/eng/ requires user to pass -cross argument to :/build.sh and set ROOTFS_DIR environment variable.
During the native build, it relies on setup done by the scripts under :/eng/common/cross. We have multiple examples in our platform matrix ({os}-{arch}) which make use of this infrastructure.
Android, however, is at the odds. For coreclr, it uses setup from :/eng/common/cross/build-android-rootfs.sh and :/eng/common/cross/toolchain.cmake, but for mono it uses a different setup. The impact is that:
The cross-build in
:/eng/requires user to pass-crossargument to:/build.shand setROOTFS_DIRenvironment variable.
does not hold for "Android on mono", due to which it requires us to add a few exceptions in the build infra and need us to remember about this exceptional case. Another down side is that the coreclr Android setup gets stale every now and then because no CI leg is exercising it.
I am opening this issue to discuss what can be done to consolidate Android build on mono and coreclr without losing any flexibility and still adapt to -cross / CrossBuild infrastructure.
Activity
am11 commentedon Jul 30, 2021
cc @akoeplinger, @fanyang-mono , @ViktorHofer, @janvorli
fanyang-mono commentedon Jul 30, 2021
Thanks for opening this issue. More discussions could be found from this PR #55641
Add NativeAOT build and runtime pack for linux-bionic
Add NativeAOT build and runtime pack for linux-bionic (#86781)
dotnet-policy-service commentedon Jan 30, 2026
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
This process is part of our issue cleanup automation.
dotnet-policy-service commentedon Feb 13, 2026
This issue will now be closed since it had been marked
no-recent-activitybut received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.