Add E2E tests for testing library mode builds for mobile
- Dominant language
- C#
- Stars
- 3.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
### Description
Mono and NativeAOT support building custom managed libraries for mobile platforms that do not rely on target OS specific framework. This is achieved by publishing the class library by using the general "non-OS-specific" target framework i.e. `net8.0` and the runtime identifier for a specific mobile platform e.g.: `dotnet publish -r ios-arm64`. For a given class library the toolchain will produce `libClassLib.dylib` which can be then referenced from the mobile application (more info can be found here: https://github.com/dotnet/runtime/blob/5b5d7919a6099c9ea0056eaa800d59f53b3d9fe1/docs/design/mono/mono-library-mode.md).
dotnet/runtime repo includes functional tests which are testing library mode support for mobile, but these tests do not test the actual end-to-end scenario.
- Option 1: To improve our test coverage and catch early any potential issues with this support, we should add appropriate test cases in this repository.
- Option 2: Expand the wasm build tests in dotnet/runtime and apply it to mobile workloads. More specifically something that would run against the latest official build on a schedule.
/cc: @steveisok
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.