![]() so using features like the start workbench won't work because they rely on qtwebengine which is dependent on qt5 which qt5 never fully supported m1 processors, maybe that has changed but i haven't fully looked in to. and i don't qt5 supports apple aarch64 ie m1 procs. The major limitations at this time i believe are that freecad doesn't support qt6 (that i'm aware of) i think there's a forum thread about that. I'm choosing to build on big sur because once i get a working build on big sur and it can run on macos high sierra and newer with the issues ironed out i'll attempt to circle back around and see if i can build a native arm build of FreeCAD.app using the same big sur vm. as i'm more interested (when i have available time) to build on big sur and make certain the release will run on macos high sierra (10.13) and newer. that is something i haven't tested myself yet. if you have an m1 mac then you should □ be able to run the FreeCAD.app bundle that i'm distributing via the homebrew-freecad tap via Rosetta 2. since the builds are built on macos mojave they will run on any version of macos mojave and newer. ![]() Presently i'm using a macos vm to build and distribute the macos FreeCAD.app mac app bundles hosted on the homebrew-freecad tap. this has proven more difficult than i had originally planned, but have made some recent headway. ![]() and the time that i do have, i've been spending it working on getting a freecad build built on a big sur box and being able to distribute a FreeCAD.app bundle that will run on macos 10.13 to the latest version. I was recently granted access to a m1 machine, but my time has been limited. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |