PySide2 Python module found at /opt/homebrew/lib/python3.10/site-packages/PySide2. SHIBOKEN_PYTHON_LIBRARIES computed to value: '-undefined dynamic_lookup ' SHIBOKEN_PYTHON_INCLUDE_DIRS computed to value: ' Found Spnav: /opt/homebrew/lib/libspnav.dylib Found Boost: /opt/homebrew/lib/cmake/Boost-1.79.0/BoostConfig.cmake (found suitable version "1.79.0 ", minimum required is "1.55 ") found components: filesystem program_options regex system thread date_time OCE/OpenCASCADE shared libraries directory: /opt/homebrew/lib
OCE/OpenCASCADE include directory: /opt/homebrew/include/opencascade Sources: /Users/dirkolbrich/FreeCAD/freecad-source/src/CXX Headers: /Users/dirkolbrich/FreeCAD/freecad-source/src
Freecad for mac m1 install#
Detected Homebrew install at /opt/homebrew BUILD_START requires BUILD_WEB to be ON, but it is "OFF " BUILD_OPENSCAD requires BUILD_MESH_PART to be ON, but it is "OFF " BUILD_MESH_PART requires BUILD_SMESH to be ON, but it is " " I hope all this helps, and i wish i had unlimited amount of time to make this stuff happen unfortunately i don't so i try to get to things when i can. if you look at the freecad formula in the homebrew freecad tap you'll see where there is an option to disable the qtwebengine during the build so you may be able to build a native m1 FreeCAD.app bundle. or you can selectively disable certain features of freecad.
Freecad for mac m1 update#
so to get all the bells and whistles with freecad one would need to either get qtwebengine v5 working with m1 or update the freecad src to work with qt v6.2 as i believe that is the version that supports all the features of m1 procs. 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 kommentar(er)
