ARM64 Windows Support

[justrach]

Current behavior

Emulated in 32 bit windows emulator

Expected behavior

A native build would be great since Electron recently added 64 bit support for ARM64 :)
Load in ARM64, however, it loads in the emulation layer, leading to a lack of battery loss.

Steps to reproduce

Are the binaries open to compile it for ARM64, so that there can be unofficial releases.

Environment

ARM64 for Windows10

Desktop/Web

• Boost Note.next version: 0.9.0
• OS version and name: Windows 10

---

IssueHunt Summary

Backers (Total: $20.00)

• boostio ($20.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[Rokt33r]

I don't have an arm64 windows pc. But I'm sure that adding arm64 to arch should work. Do you think you can test the building?

1. Add arm64 to here https://github.com/BoostIO/BoostNote.next/blob/master/package.json#L250-L253
2. Create .env file and set BOOST_HUB_BASE_URL=https://boostnote.io.
3. Run these scripts

npm run build:electron
npm run prepack

Then you will get an executable so you can run it in your pc.

[justrach]

Hi, yes it works

-> Tested on M1 Mac w the M1 Chip.. Is there a way to fix that?

However, there are signing issues, but I believe that is due to the unofficial port that we would be building is that right?

[Rokt33r]

@justrach Thanks for testing then we should provide build for arm64 too.

Tested on M1 Mac w the M1 Chip.. Is there a way to fix that?

electron-userland/electron-builder#5426 seems electron builder is supporting the apple silicon chip so I think we can try the same trick on M1 Mac.

[issuehunt-oss]

@boostio has funded $20.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[nguyenjustin214-lab]

/attempt #647

I found the Windows build config still only targets x64 and ia32. I am adding arm64 to the Electron Builder Windows target list in package.json, keeping the change scoped to packaging so the existing x64 and ia32 outputs remain unchanged.

Local validation so far:

• config check confirms the Windows target arch list is now ["x64", "ia32", "arm64"]
• npm ci --ignore-scripts
• npm test
• git diff --check

Transparency: AI-assisted with Codex; I reviewed the diff and validation output before submitting.