News for hackers. Stuff that matters.

A comment on Porting the Unity Engine to .NET CoreCLR. Parent comment

Re:Porting the Unity Engine to .NET CoreCLR by coldacid on Tuesday April 10, 2018 @09:57PM (#16807444)
IL2CPP had to be built anyway because of Apple's rules about interpreters in iOS apps. Unity can't just ignore that platform.
[ Parent | on HN ]
Re:Porting the Unity Engine to .NET CoreCLR by carussell on Tuesday April 10, 2018 @10:57PM (#16807689)
Xamarin ships for iOS. It does AOT compilation from CIL to native.
[ Parent | on HN ]
Re:Porting the Unity Engine to .NET CoreCLR by bananaboy on Tuesday April 10, 2018 @11:21PM (#16807780)
That's what Unity did before IL2CPP as well (not surprising of course since it was Mono). I think they didn't want to have to keep writing new native code generators for the AOT process for different architectures, which is why they went the IL2CPP route. That way they can generate the C++ code without worrying about what platform it's going to be running on and also take advantage of the C++ compiler's optimiser.
[ Parent | on HN ]