iOS Export failing - "Ahead-of-time compilation is not supported for the target framework"

Petey · August 17, 2024, 2:30am

Godot Version

4.3

Question

Hi All!

I’m having trouble exporting this project to iOS and getting this error -

NETSDK1207: Ahead-of-time compilation is not supported for the target framework. /usr/local/share/dotnet/sdk/8.0.401/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5)

If I rebuild a new project with the same contents it seems to work but I’d like to figure it out.
Does anyone know what might be causing that?

Thanks,
Pete

Moreus · August 17, 2024, 9:27am

I found this one

github.com/dotnet/runtime

NativeAOT library mode on iOS-like platforms

opened 02:20PM - 12 Jul 23 UTC

closed 08:57AM - 10 Jan 24 UTC

filipnavara

os-ios area-NativeAOT-coreclr

As documented in https://github.com/royalapplications/beyondnet/issues/34#issuec…omment-1632510996 there's a demand to get NativeAOT library mode working on iOS-like platforms. This is specifically for `net8.0` TFM and NOT the Xamarin `net8.0-ios` TFM which may run into similar issues but requires fixes in the Xamarin SDK. It currently requires a couple of workaround and we should look into fixing the underlying issues: - Linking step doesn't use correct `-sysroot`/`-target`. We currently bundle the apps through AppleAppBuilder in dotnet/runtime, and a custom bundler in Xamarin. However, for dylib builds the NativeAOT linker step on its own is mostly sufficient. We just need to specify proper `-target` (eg. `apple-arm64-ios11.0` or similar) and sysroot. The sysroot can be obtained through `xcrun`, or we can simply execute the whole linker using `xcrun -sdk iphoneos clang <options>` command to achieve the same result. - There's a conflict with the new `mobile-librarybuilder-experimental` workload which currently needs to be disabled with `_IsAppleMobileLibraryMode=false`. We should disable it automatically for NativeAOT publishing.

Petey · August 17, 2024, 11:14am

Yeah I saw that, but I couldn’t see a solution. It is closed though
It’s a bit strange that my new project with all the files copied across works fine. Is that a normal thing to do to “clean” a Godot project if it gets weird?

Moreus · August 17, 2024, 1:07pm

they mention compilation worked out which is here:

github.com/dotnet/runtime

.NET 8 RC1 fails to NativeAOT compile when targeting ios-arm64

opened 11:58AM - 13 Sep 23 UTC

closed 11:57AM - 16 Sep 23 UTC

lemonmojo

os-ios area-NativeAOT-coreclr

### Description Up until .NET RC1, NativeAOT compilation worked out of the box …when targeting `ios-arm64`. This requires adding `<PublishAotUsingRuntimePack>true</PublishAotUsingRuntimePack>` and `<LinkerArg Include="-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk" />` to the csproj. Everything else is pretty much standard fare. Now, since RC1, `dotnet publish` fails because of linking errors in `libicuuc.a` related to C++. As a workaround, one can add `<LinkerArg Include="-lc++" />` to the csproj like in the example below. ### Reproduction Steps Running `dotnet publish` against the following example csproj works fine because `-lc++` was re-added using a `LinkerArg` flag. Removing this line makes the build fail. ```xml <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net8.0</TargetFramework> <RuntimeIdentifier>ios-arm64</RuntimeIdentifier> <PublishAOT>true</PublishAOT> <PublishAotUsingRuntimePack>true</PublishAotUsingRuntimePack> </PropertyGroup> <ItemGroup> <LinkerArg Include="-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk" /> <LinkerArg Include="-lc++" /> </ItemGroup> </Project> ``` ### Expected behavior Compiles out of the box. ### Actual behavior Does not compile without adding `<LinkerArg Include="-lc++" />`. ### Regression? It did work in all .NET 8 previews until RC1. ### Known Workarounds Adding `<LinkerArg Include="-lc++" />` to the csproj. ### Configuration .NET 8.0.100-rc.1.23455.8 ### Other information _No response_

obraz
not sure but maybe we gonna wait for fix that in next .Net update?

Petey · August 17, 2024, 10:24pm

Oh cool, thanks! I’ll keep an eye out.