Feature Request - ARM64 support

[NeomMob]

We are starting now to see some new devices from Microsoft using ARM64 architecture. I am wondering if there is a forecasted support for them.

[kpreisser]

See also dotnet/winforms#2053 and dotnet/wpf#1817 for the progress of Windows ARM64 support in .NET Core, including WinForms and WPF.

[amaitland]

I personally have no plans to support Win ARM64, I don't own a suitable device.

For background.

• There are no builds on http://opensource.spotify.com/cefbuilds/index.html not clear if there will be any publicly available.
• From what I can tell CEF support (probably Chomium in general) for building Win ARM64 is still in it's early stages.
  • https://bitbucket.org/chromiumembedded/cef/issues/2773/windows-add-arm64-build-support
  • `https://bitbucket.org/chromiumembedded/cef/pull-requests/266
• I'm not sure Chrome has actually released an official version, so it's likely too early to look at from a stability point of view.

[amaitland]

Someone else is welcome to take responsibility for adding and supporting Win ARM64. An ongoing commitment would be required.

[amaitland]

According to https://bitbucket.org/chromiumembedded/cef/issues/1990/linux-add-arm-build-support#comment-55787851 ARM64 builds will be available on the Spotify build server.

Update My mistake, that's the Linux ARM builds. Details for building on Windows are still in the works https://bitbucket.org/chromiumembedded/cef/issues/2840/wiki-add-windows-on-arm-building

[amaitland]

Official Windows ARM64 builds starting with M88 will be available shortly from https://cef-builds.spotifycdn.com/index.html#windowsarm64.

As per https://bitbucket.org/chromiumembedded/cef/issues/2773/windows-add-arm64-build-support#comment-59706180

This is blocked on the linker errors when attempting to compiler CefSharp.Core.Runtime targeting .Net 5.0 (required for ARM64). As reported in #3284 (comment) which I've confirmed as being a problem.

2>MSVCMRTD_netcore.LIB(mstartup.obj) : error LNK2022: metadata operation failed (80131195) :
2>MSVCMRTD_netcore.LIB(mstartup.obj) : error LNK2022: metadata operation failed (80131195) :
2>MSVCMRTD_netcore.LIB(mstartup.obj) : error LNK2022: metadata operation failed (80131195) :
2>LINK : fatal error LNK1255: link failed because of metadata errors

The CefSharp.BrowserSubprocess.Core project compiles successfully, it's less complicated though, it's possible there's just a linker setting that's causing the problem or we might need to raise an issue with Net 5 Team.

[amaitland]

For anyone interested in tacking this it looks like the first build is up on https://cef-builds.spotifycdn.com/index.html#windowsarm64

First step would be working out how to generate libcef_dll_wrapper.lib

Currently https://github.com/cefsharp/cef-binary/blob/master/build.ps1 downloads, builds and packages the x86/x64 versions, it should be possible (haven't tried obviously) to extend this to download, build and package the arm64 target binaries.

[kpreisser]

This is blocked on the linker errors when attempting to compiler CefSharp.Core.Runtime targeting .Net 5.0 (required for ARM64). As reported in #3284 (comment) which I've confirmed as being a problem.

Note that switching to net5.0 might not actually be necessary for supporting arm64 in CefSharp. With cef.sdk 88.1.2 that includes the ARM64 versions of libcef.lib and libcef_dll_wrapper.lib (from cefsharp/cef-binary#90), I was able to successfully compile CefSharp.Core.Runtime and CefSharp.BrowseSubprocess.Core after adding arm64 as platform target, and confirmed with dumpbin.exe /headers that the produced DLLs (ijwhost.dll, CefSharp.Core.Runtime.dll, CefSharp.BrowserSubprocess.Core.dll) are actually ARM64 DLLs.

I still need to check whether building a CefSharp WinForms/OffScreen app for win-arm64 with .NET 5.0 and running it on a Windows 10 on ARM machine actually works (WPF is not yet supported for win-arm64).