Skip to content

Enable AppleAppBuilder to bundle applications compiled with NativeAOT #80910

New issue
New issue
Closed
#81711
Closed
Enable AppleAppBuilder to bundle applications compiled with NativeAOT#80910
#81711
Assignees
ivanpovazan
Labels
area-NativeAOT-coreclrfeature-requestos-iosApple iOS
Milestone
8.0.0

Description

@ivanpovazan
ivanpovazan
opened on Jan 20, 2023

Description

AppleAppBuilder build task currently only supports Mono as the default AOT compiler and runtime when creating application bundles.

Proposal

Extend AppleAppBuilder to support NativeAOT, as a second AOT compiler and runtime, when creating iOS application bundles.
This would enable building and running sample applications built with NativeAOT on iOS platforms, but also size and performance monitoring.

Activity

  1. ivanpovazan
    added
    feature-request
    os-iosApple iOS
    area-NativeAOT-coreclr
    on Jan 20, 2023
  2. ivanpovazan
    added this to the 8.0.0 milestone on Jan 20, 2023
  3. ivanpovazan
    self-assigned this
    on Jan 20, 2023

  5. am11 commented on Jan 20, 2023

    @am11
    am11
    on Jan 20, 2023
    Member

    It gets enabled when TargetPlatformIdentifier is set (not to be confused with TargetFrameworkIdentifier / TFI).

    e.g. <TargetFramework>net7.0-macos</TargetFramework> is same as:

        <TargetFramework>net7.0</TargetFramework>
    <TargetPlatformIdentifier>macos</TargetPlatformIdentifier>

    By setting TPI, .NET SDK imports WorkloadManifestTargetsLocator, which resolves Microsoft.macos.Sdk.net7 SDK, which further resolves Microsoft.NET.Runtime.MonoTargets.Sdk.net7 and then Xamarin.Shared.Sdk etc. Somewhere there in the SDK, we can check if '$(PublishAot)' == 'true' then e.g. skip importing WorkloadManifestTargetsLocator or something down the chain. There maybe some more changes required but that would be the starting point to ninja in the NativeAOT bits. 🥷

  6. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Feb 6, 2023

  7. ivanpovazan commented on Feb 7, 2023

    @ivanpovazan
    ivanpovazan
    on Feb 7, 2023
    MemberAuthor

    It gets enabled when TargetPlatformIdentifier is set (not to be confused with TargetFrameworkIdentifier / TFI).

    e.g. <TargetFramework>net7.0-macos</TargetFramework> is same as:

        <TargetFramework>net7.0</TargetFramework>
    <TargetPlatformIdentifier>macos</TargetPlatformIdentifier>

    By setting TPI, .NET SDK imports WorkloadManifestTargetsLocator, which resolves Microsoft.macos.Sdk.net7 SDK, which further resolves Microsoft.NET.Runtime.MonoTargets.Sdk.net7 and then Xamarin.Shared.Sdk etc. Somewhere there in the SDK, we can check if '$(PublishAot)' == 'true' then e.g. skip importing WorkloadManifestTargetsLocator or something down the chain. There maybe some more changes required but that would be the starting point to ninja in the NativeAOT bits. 🥷

    ^ @kotlarmilos I believe this would contribute to your SDK integration work

  8. ivanpovazan
    closed this as completedin #81711on Feb 7, 2023
  9. ivanpovazan
    added a commit that references this issue on Feb 7, 2023

    Enable AppleAppBuilder to bundle iOS applications built for NativeAOT…

    8642a21
  10. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Feb 7, 2023
  11. ghost locked as resolved and limited conversation to collaborators on Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-NativeAOT-coreclrfeature-requestos-iosApple iOS

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions