New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARM64 Native Compilation support #17288
Comments
|
If i read this right, this is GN: https://gn.googlesource.com/gn/ "GN is a meta-build system that generates build files for Ninja." In turn, here is Ninja: https://ninja-build.org/ "Ninja is a small build system with a focus on speed. It differs from other build systems in two major respects: it is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible." If I were to start on this I'd make a stab at getting Ninja to build, but as @jkleinsc notes, this may not really be necessary depending on what you are doing. |
Electron is based on Chromium, which does not itself make any concerted attempt to be buildable on ARM hosts. All ARM-based Chromium (and Electron) builds are cross-compiled from x64 hosts. You're welcome to take on this challenge, but I suspect there's a long road ahead of you if you want to build Electron on an ARM host! |
@nornagon @vielmetti @jkleinsc I do agree that both Electron & Chromium doesn't have native compiling support over ARM64 architecture. And Yeah, I do agree that I have a long road ahead of me but the journey would be easier if you guys can help me out in figuring out ways to achieve successful compilation over ARM64. Regards, |
Hi,
I am trying to compile Electron for my Native ARM64 based machine but I am not able to get proper steps which should be followed for this architecture.
Can you please let me know whether:
I am really interested to work in direction of getting Electron run over ARM64 architecture, which will also benefit a lot of other communities too.
Looking forward to quick help from your side.
Regards,
The text was updated successfully, but these errors were encountered: