-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple Silicon / ARM builds #19
Comments
It's getting closer. The instructions linked below (except replace step 2's |
Can you provide any build instructions? |
Best luck I've had building on M1/arm Mac has been with these instructions. I built successfully as recently as last week. https://github.com/oursland/FreeCAD-Build-Notes |
tried to generalize it (and obviously replace paths/urls/names accordingly), but I failed. What do you do instead of the following command:
|
That command works for me. My base directory structure is as follows:
And all the directories and files are created and layered in as so:
May I suggest joining the FreeCAD Discord? A number of helpful people there. |
I thought these instruction would help me build preprocess_cancellation tool (which is what I'm looking for), not freecad. |
Sorry about that. |
Not that familiar with python, but I did find the following: https://www.baeldung.com/linux/python-binary
|
The current binary is an Intel/AMD and as such runs in emulation mode on modern Apple machines and cannot run on Linux ARM machines.
It would be great if this was built for x86 and ARM targets.
I had a go in a fork and I had problems with the 'poetry' tool used by this project, however using standard pip I was able to install the updated packages that provide ARM compatibility without issue.
I've attached my (local) macOS / Apple Silicon ARM build to this issue in case anyone else wants the binary.
The build when compared to the Intel binary, the ARM binary is 70%~ smaller and processes gcode - and more importantly - processes gcodes around 3x faster on average in my tests.
The text was updated successfully, but these errors were encountered: