zerodave
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
you are indeed correct, it is
I also should have said Q1 of 2024 instead of Jan 2024, as that's where it currently sits on the Github roadmap, according to @Steve-Glass from Github: https://github.com/github/roadmap/issues/819 I'll poke around with self-hosted runners if only for increasing my own knowledge, but I completely agree with your thinking. The costs would seemingly be enormous with 10-20 builds per day. I've got a local running copy of
macos-latest-xlarge for the M1 Mac (arm64) -- I misread that article and thought they had made a change moving the M1 arm64 to large, when in fact they made the old 12-core x86_64 which was -xlarge the new -large --confusing, no đŸ˜…?I also should have said Q1 of 2024 instead of Jan 2024, as that's where it currently sits on the Github roadmap, according to @Steve-Glass from Github: https://github.com/github/roadmap/issues/819 I'll poke around with self-hosted runners if only for increasing my own knowledge, but I completely agree with your thinking. The costs would seemingly be enormous with 10-20 builds per day. I've got a local running copy of
waspc on my M1 Max so I can play with it on my dev platform, and all my prod/staging infrastructure is Linux, so I'm all happy.
Thanks for the engagement on this topic (and for Wasp!). I learned a bunch looking into this.41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
and a final option:
5. Investigate and cross-compile
waspc on the existing macos-latest runner to arm64 and build both x86_64 and arm64 arch binary bundles on the existing runner. It is definitely possible to x-complile arm64 on x86_64, but I am fairly sure the cabal test functionality can't test the non-native arch. Then have the current runner build both macOS archs and build the two separate .tgz bundles.41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
@martinsos after some research, I could patch the yaml to add
macos-latest-large alongside macos-latest which will build against an arm64 M1 Mac, but... these are beta, and only available as large runners which are paid by the minute and not included in the monthly minutes of a regular Github plan. reference: https://github.com/actions/runner-images/issues/8439
Potential options to move forward:
1. If paid minutes are an option, I can patch the waspc-ci.yaml and installer.sh and test CI with the new paid runners building a wasp-macos-arm64.tar.gz bundle
2. Wait until January 2024 when the macos-latest will become GA and arm64 per the above issue #8439
3. Investigate adding Circle CI (https://circleci.com/open-source/) to the CI pipeline for macOS arm64 as they give 30,000 Mac M1 credits for free to OpenSource projects
4. Create a temporary branch (or fork) for Wasp on macOS arm64 and test CI via CircleCI above41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
@martinsos yes -- that all makes sense to me now and following your train of thought was helpful. Thanks for the info on the Github actions. The binary that is pre-built for MacOS is the x86_64 version of Mac which is the old Intel Mac (I have several of those as well). The Mac OS/x86_64
waspc binary will not run without Rosetta compatibility (x86 for arm64) which is a bit of a horror show performance-wise as it is a processor emulator for the new chips to run the old architecture.
I will have some time to dig deeper on this tonight. I may be able to create a PR for the particular modifications to the yaml Actions/Workflow files. This will give me an interesting opportunity to learn more about GH Actions. I've modified installer.sh to detect x86_64 vs. arm64 macOS and to download the proper package, now I just need to get the workflow building it (if possible)41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
Also per your suggestion, tagging @miho for visibility
41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
FYI it was a bit of a bear to get LLVM@13 to go on MacOS Sonoma 14.1, but I got it figured out. I assume the arm64 binaries are all portable, but would need @kd240 and/or others with M1/M2/M3 hardware to perhaps test
41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
@matijash I updated
installer.sh to accomodate x86_64 and arm64 versions of MacOS (ready to submit the PR) -- now I just need to create the wasp-macos-arm64.tar.gz bundle41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
obviously I could simply list the files in
wasp-macos-x86_64.tar.gz and replace/move my wasp-cli to waspc -- but I suspect it's more complicated than that.41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
@matijash Okay, so I have it built for arm64 and works as well as the command -- that said, I may need some help figuring out how to package a bundle. I can rewrite the script to accomodate arm64 if one of the devs can help guide me on creating the tar.gz
41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
Thanks! Matija. Assuming I can get it to build, I could possibly build a waspc for arm64 and submit it as a PR
41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
I'm on a M1 max mac studio -- if I can help or contribute or test anything, please let me know. I'm not sure if anything besides just the wasp build process needs x86, but I'm not super excited about installing Rosetta if I can possibly avoid it.
41 replies
WWasp-lang
•Created by flmxyz on 7/17/2023 in #đŸ™‹questions
MacOs Error.
@matijash very new to the community (~30 secs :) is there a roadmap item for M1/M2/M3 support for Wasp? just read your note to @kd240 about needing to install rosetta
41 replies