What's the status of apple M1/arm64 support?

[spencerkohan]

Is there a plan to do a release of VSCodium which is native to M1, or else a universal binary? It looks like VSCode is already supporting this, is it on the roadmap for VSCodium?

[stripedpajamas]

Since VSCode is already supporting it, it's on the roadmap for VSCodium. If GH Actions has support for Darwin+arm, it should be really simple. Haven't had a chance to look into it yet.

[heracek]

There is no support in GitHub Actions yet 😢: actions/runner-images#2187

[stripedpajamas]

Yeah we will need to wait for GH Actions support; suggest 👍-ing the linked issue.

[djthread]

VSCode 1.54+ has M1 support now! Super looking forward to the VSCodium update :)

Edit: Yay I'm on 1.54.2 now \o/

[jiserra]

I downloaded 1.54.2 and the Architecture still says "Intel"… what I'm missing?

Edit: Yay I'm on 1.54.2 now \o/

[daiyam]

@jiserra M1 is not available on github actions. Microsoft must be using a mac mini to build its project.

[ayan-iiitd]

Can someone please clarify if the latest build is on arm or not? confused by the two comments -

VSCode 1.54+ has M1 support now! Super looking forward to the VSCodium update :)

Edit: Yay I'm on 1.54.2 now \o/

I downloaded 1.54.2 and the Architecture still says "Intel"… what I'm missing?

[daiyam]

VSCodium is built with GitHub actions which don't support M1 yet.
VSCode is built on their own servers. They must be using mac mini to build the M1 version. Bigger team. Bigger budget.

[leonardodino]

A related project is using GitHub actions to compile Chromium from source to arm64-macos.

The builds takes more than a day tho 👀 Hopefully vscodium is using a pre-built electron as base? 🤔

[djthread]

oh snap, indeed, i spoke too soon - sorry.

[gytisrepecka]

The builds takes more than a day tho 👀 Hopefully vscodium is using a pre-built electron as base? 🤔

Does Electron already support M1 (aarch64)?

[togethereveryday]

Let´s say I have a M1 machine, what would be necessary to build VS Codium? My status: I have a machine, I have basic programming skills in front end web development. Is it difficult if one has never done it?

[LukeChannings]

@togethereveryday

Have a read of the GitHub Actions workflow for your OS - here. That's where I'd start.

[daiyam]

@togethereveryday If you want to build VSCodium manually, you can run the script build/build_macos.sh. You might have to edit it to change targeted architecture.

[theotheroracle]

i'm a bit confused as to why i was pinged, i didn't comment on this issue and i don't have an m1 mac .

[daiyam]

@theotheroracle Sorry, it's my mistake. Bad autocomplete and I haven't rechecked...

[theotheroracle]

Oh ok, no worries

[rolimans]

Was able to build for the M1 on my machine. Changed the environment variable VSCODE_ARCH to arm64 and installed jq using brew install jq then ran ./build/build_macos.sh. ;)

[jiserra]

I had to modify a couple of packages on package.json, but I finally could build it!

[tibeer]

If anybody is lazy, you can use the binary from my fork: https://github.com/tibeer/vscodium
This is compiled on my M1 Mac. I try to keep it updated.

[Tarnyko]

If anybody is lazy, you can use the binary from my fork: https://github.com/tibeer/vscodium
This is compiled on my M1 Mac. I try to keep it updated.

Thanks @tibeer , this is definitely appreciated!

[im-AMS]

If anybody is lazy, you can use the binary from my fork: https://github.com/tibeer/vscodium
This is compiled on my M1 Mac. I try to keep it updated.

I actually tried running, and it says “VSCodium.app” is damaged and can’t be opened. You should move it to the Bin.

[melgu]

I actually tried running, and it says “VSCodium.app” is damaged and can’t be opened. You should move it to the Bin.

This is because of Gatekeeper restrictions as the app isn't signed. You can execute the following to remove the quarantine attribute.

sudo xattr -r -d com.apple.quarantine /Applications/VSCodium.app

[tortuetorche]

If anybody is lazy, you can use the binary from my fork: https://github.com/tibeer/vscodium
This is compiled on my M1 Mac. I try to keep it updated.

Hi @tibeer,

Thank you for these M1 ARM64 builds 👍
Just one question, why your builds since VSCodium 1.57.0 are way more bigger than the classic Darwin x64 builds (~105 MB VS ~260 MB)?
Can you manage to shrink them a bit, please?

Have a good day,
Tortue Torche

[tibeer]

If anybody is lazy, you can use the binary from my fork: https://github.com/tibeer/vscodium
This is compiled on my M1 Mac. I try to keep it updated.

Hi @tibeer,

Thank you for these M1 ARM64 builds 👍
Just one question, why your builds since VSCodium 1.57.0 are way more bigger than the classic Darwin x64 builds (~105 MB VS ~260 MB)?
Can you manage to shrink them a bit, please?

Have a good day,
Tortue Torche

@tortuetorche interesting, I never noticed. Further discussion/resolving should be done here: tibeer/vscodium#2

[MohamedElashri]

I think this can be added to official project as now Big sur is available on github actions. See here.

[daiyam]

@MohamedElashri Thx for the info. I will take a look.

[MohamedElashri]

I think it is just a trivial change now in macos.yml action config. Just change VSCODE_ARCH: "x64" to VSCODE_ARCH: "arm64" and build will go fine. I tried on a fork action-run and these are the binaries for latest tag

[Alitejawi]

No news on a supported version of arm arch through the default VSCodium project?

[MohamedElashri]

Unless Github add mac m1 VMs to Github action, nothing will change.

But you don't need that anyway, clone the repo and build VSCodium on your machine and everything will work following this comment.

Edit: it just takes less than 6 minutes to build from source on mac m1

[bashilias]

build it your self. Here is a guide: https://ilias.sh/posts/build-vscodium-on-darwin-arm64/

[macserv]

Unless Github add mac m1 VMs to Github action, nothing will change.

@MohamedElashri, if you have a moment, could you please explain why this is the case? It seems like other Xcode and Electron projects are able to build on Intel-based Macs/VMs and produce a "Universal" application which can run natively on either architecture.

Thanks!

(edit: tagged the wrong contributor, apologies!)

[daiyam]

@macserv Yes, it seems to be possible but we need somebody to be able make a working PR. Since I can't test it, I won't make it... But anybody is free to make it 😉

[arixmkii]

It seems like other Xcode and Electron projects are able to build on Intel-based Macs/VMs and produce a "Universal" application which can run natively on either architecture.

For VSCodium situation is a bit different, because you need to build it the same way the upstream is built. And looks like they first build archives on different platforms and after this combine into universal app:
https://github.com/microsoft/vscode/blob/bc71f7a3438fae0edced4ed91bc9429a72cdb416/build/azure-pipelines/darwin/product-build-darwin.yml#L150

I tried to do it on M1 Mac (building for both architectures on that host) and this didn't work. I will try do build x64 on Intel Mac later and then compose universal on M1 some time later.

So, to get fully functional universal app, not only the build targets will have to be adjusted, but the whole CI workflow should include additional steps (fetching intermediate artifacts from different build agents).

[berkaybakacak]

Changed the environment variable VSCODE_ARCH to arm64, installed all dependencies then ran ./build/build_macos.sh. And it gave me error: ./build/build_macos.sh: line 8: arm64: command not found

[codeluggage]

@berkaybakacak

Changed the environment variable VSCODE_ARCH to arm64, installed all dependencies then ran ./build/build_macos.sh. And it gave me error: ./build/build_macos.sh: line 8: arm64: command not found

It built ok for me on macOS 12.2.1 after changing to arm64 like this:

SHOULD_BUILD=yes CI_BUILD=no OS_NAME=osx VSCODE_ARCH=arm64 . build.sh

on https://github.com/VSCodium/vscodium/blob/master/build/build_macos.sh#L8

and then running the build as VSCODE_ARCH=arm64 ./build/build_macos.sh

[berkaybakacak]

@codeluggage I replaced my node version with a correct version (it wasn't the correct version) and typed the entire command you gave (I didn't write the "VSCODE_ARCH=arm64" part before) and it worked. I don't know if it was because of my node version or because I typed the command incompletely, but thanks a lot.

[ferben]

Is there official release date VSCodium prebuilt binaries for Apple Silicon?

[daiyam]

I've discover that MacStadium offers free vm for open source project. I will try it and setup the workflow.
I would need help from to test the final binaries on M1.

[ferben]

You can build arm64 binary on x86_64 too. You need only Xcode 12.5 or 13.
Only for testing you need Apple Silicon hardware.

[y-mx-b]

You could just build a universal binary too, couldn't you? Not really much of a reason to split the releases by architecture if a universal binary build works.

[daiyam]

I already tried to make to make an arm64 binary by using macOS 11 but the dependencies were still x86. Since I can't test, it's kinda hard for me to find the issue, if it's possible...
With M1 vm, I would somewhat more sure that the binary would be more successful.
But I would welcome any PR that would build the arm64 binary on the existing vm of GitHub!

[jakenvac]

I'm free to test M1 binaries by the way. I've just built the latest version of code this morning. I'm also putting together a brew script that will build and install locally.

[berkaybakacak]

https://drive.google.com/file/d/12dvGL8rbV7wP880Gc_cuvlwjiDTHw4P_/view?usp=sharing

Here. I built arm64 version on my M1 Air, macOS 12.2.1

[matthewess]

Changed the environment variable VSCODE_ARCH to arm64, installed all dependencies then ran ./build/build_macos.sh. And it gave me error: ./build/build_macos.sh: line 8: arm64: command not found

It built ok for me on macOS 12.2.1 after changing to arm64 like this:

SHOULD_BUILD=yes CI_BUILD=no OS_NAME=osx VSCODE_ARCH=arm64 . build.sh

on https://github.com/VSCodium/vscodium/blob/master/build/build_macos.sh#L8

and then running the build as VSCODE_ARCH=arm64 ./build/build_macos.sh

This works for me on my M1 Pro, macOS 12.3.1. What can I do to contribute to getting these binaries hosted with the other releases? I'd really love to make the M1 build available on Nixpkgs.

e: included an unnecessary @ mention at first, sorry about that 😅
e2: didn't realize it's likely still blocked on actions/runner-images#2187
e3: for anyone looking for something somewhat reproducible: https://gist.github.com/matthewess/9e9d758c31ebe26024df301befd2da06

[daiyam]

Hi all, the macOS arm64 binary is finally available. Please provide any feedback if it's working or not. Thx
Do the universal version needed? Since we are dev, we know which arch we are using.

[jakenvac]

yeah I would say don't worry about the universal version. I don't think people buy an m1 mac for dev work without knowing what they're buying 👍🏻

[MohamedElashri]

Hi all, the macOS arm64 binary is finally available. Please provide any feedback if it's working or not. Thx
Do the universal version needed? Since we are dev, we know which arch we are using.

I have replaced my built arm64 version by the selfhosted generated version on the repo and so far it is working without any problems.

[tibeer]

@daiyam for completeness: Can you post the link to the binary which should be tested? It's neither here: https://github.com/VSCodium/vscodium/releases nor here: https://github.com/VSCodium/vscodium/tags

[daiyam]

It's in: https://github.com/VSCodium/vscodium/releases/tag/1.66.2

• https://github.com/VSCodium/vscodium/releases/download/1.66.2/VSCodium-darwin-arm64-1.66.2.zip
• https://github.com/VSCodium/vscodium/releases/download/1.66.2/VSCodium.arm64.1.66.2.dmg

[tibeer]

Sorry, my fault. Thought this was outdated since Github flags this as "released this 16 days ago". Besides the issue that the app is still blocked by default (can be fixed sudo xattr -r -d com.apple.quarantine /Applications/VSCodium.app), it works fine:

[daiyam]

@tibeer For the quarantine, yep, I'm in the process to update the README and the website.

[AwlsomeAlex]

(can be fixed sudo xattr -r -d com.apple.quarantine /Applications/VSCodium.app), it works fine:

sudo isn't required to clear the quarantine flag. Was able to get it working without sudo.

[AwlsomeAlex]

If you want to learn more about why you need to clear the quarantine flag on Apple Silicon builds, take a look at this Apple Platform Security Document.

Specially under Unsigned x86_64 code:

A Mac with Apple silicon doesn’t permit native arm64 code to execute unless a valid signature is attached.

For binary compatibility, translated x86_64 code is permitted to execute through Rosetta with no signature information at all.