Native support for Apple Silicon (ARM64 architecture) #46299
Comments
|
It would be great indeed! Any news on this? |
|
Just FYI: Rosetta2 is claimed to be REMOVED in OSX 11.3 beta 3 update in certain countries. I guess M1 owners will run QGIS in QEMU very soon. |
|
I want to see QGIS run natively on the M1 Ultra with a Mac Studio. |
|
Is there anyone who can provide remote access to a M1 mac may be it's better to donate a M1 😊 |
|
AWS provides M1 Mac instances: https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-ec2-m1-mac-instances-macos/ |
|
But there are python performance issues on M1: https://developer.apple.com/forums/thread/695963 |
|
@tsmcgrath this is not a generic python issue - but rather a issue with numpy. Python in general is actually really fast on a M1 - the issue is that the default numpy wheels seem to ship with a slow numerical library. This can be fixed by compiling numpy from source. So this should not be a blocker. |
|
Any news/progress on this? Native M1 QGIS is something I would very much like to have. |
|
Just to add to this, I find QGIS quite slow to start and use on an M1 Mac as it is running under Rosetta. Native support would be very much appreciated. |
|
M1 multiprocessing support would be very, very great. Especially with large datasets, qgis will often not repsonding because 100% CPU usage :/ |
|
In MacOS 13 Ventura Rosetta is not installed by default. QGIS still can be launched after installing it from command line: |
|
Rosetta 2 is not installed by default on Monterey either, it gives the user the option to install it when you try to launch an intel binary. Seems Ventura is getting additional translation support for intel binaries running within a linux VM as well, so it is hardly showing signs of going away. |
|
Native apple silicon build would be great to have! Is this on the roadmap? |
|
+1 for Apple Silicon M1 native support |
|
Edit: Turns out it is possible to run QGIS natively on M1 via MacPorts. See the discussion below, particularly this comment which gives a good idea of the steps required. Note that I'm not affiliated with QGIS, but was curious about M1 support. tl;dr: QGIS needs to move to Qt 6. When that is done, native M1 support should From looking around Github issues:
Donations to QGIS partly go towards funding these kinds of grants. |
|
Well, I do have QGIS 3.26.2 running natively on my M1 MacBookPro. Everything is installed from source using MacPorts |
|
Just FYI if you use Asahi Linux on M1 macs QGIS runs natively out of the box. |
Interesting. I guess I should have said "native M1 builds probably won't show up on QGIS.org until after the Qt 6 transition". Good to know MacPorts is an option. It was hard to find official info on the state of Qt 5's support for M1. All I turned up was a blog post which mentions at the very end:
Sounds scary 😅 |
Would you like to share it? I think it is not easy to build qgis from source? |
Actually the latest QGIS comes with the packages. If you want to run the LTR you can go to https://aur.archlinux.org/packages/qgis-ltr and click download from the snapshot of the build, after you unzip you go to that directory, edit the PKGBUILD file and change the architecture from Of course you need to install asahi linux first. |
|
For information, the only part of QT5 that doesn’t compile on M1 is Scintilla. We’re stuck at 2.13.1 currently, but that’s not a dealbreaker. Does Qt6 uses Metal for 3D display? |
No, qgis requires OpenGL right now -- even for qt 6 builds. |
Any pointers for getting QGIS to install using MacPorts? I've tried installing with the -s option but the install fails because it can't build py310-pyqt5-scintilla (command execution failed). |
|
That’s exactly where the nub of the problem lies. I know there’s a way to install old versions, I’ll figure that out and post it here |
|
I can get the install past the error with pyqt5-scintilla by adding "use_xcode yes" to the portfile for py310-pyqt5-scintilla. Have now got it past all the dependencies but the QGIS build fails at 31%, still trying to figure that one out. |
|
Ah, nice, I knew there was a workaround, it had been discussed in the mailing list. I’m going to do that too, thanks for posting it. |
|
This is the output of my qgis build, any pointers would be appreciated. Not getting much more with the log file: % sudo port -sp install qgis3 And: % tail -20 main.log |
The connection between MacOS 15 and llvm-14 was just my assumption, as I successfully built QGIS a few weeks ago on MacOS 14, but could no longer build on my new machine which is running MacOS 15. Oh I agree, it can't be easy to maintain something as complex as QGIS with new os releases. Was just a polite note and asking if there were any alternative options. Thanks |
No worries, the best you could do to help fix this is reporting at https://trac.macports.org/newticket?port=qgis3 (and don’t forget to append the main.log). |
@nyalldawson I’ve planned this for some time, but never got to it. Is the some documentation regarding building QGIS with QT6? |
|
Someone from MacPorts responded to my question:
Indeed clang-14 is known to fail to build on macOS 15 so you can't use it
or anything that depends on it.
clang-18 and later build on macOS 15.
In this case, qgis3 depends on py312-llvmlite which depends on clang-14.
py312-llvmlite will need to use clang-18 or later for compatibility with
macOS 15.
Sent from Gmail Mobile
…On Mon, Sep 23, 2024 at 6:00 PM Nicklas Larsson ***@***.***> wrote:
@jcm36 <https://github.com/jcm36> I'd suggest asking the macports
maintainers to switch to a qt6 based build of qgis. Those should be fully
functional now, and fully compatible with Apple silicon chips
@nyalldawson <https://github.com/nyalldawson> I’ve planned this for some
time, but never got to it. Is the some documentation regarding building
QGIS with QT6?
—
Reply to this email directly, view it on GitHub
<#46299 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6MO3ORQYFD5ZZP2J4MA4LZYCFQLAVCNFSM5JDABK52U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZWHE2TSNRYG43Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Unfortunately the build failed when excluding the plugin_support312 option too. "Failed to build qt5-qtlocation: command execution failed." I guess the discussion here probably isn't the best place to get into - so I'll see if I can raise a ticket at MacPorts. [Edit]: Trac ticket already exists for qt5-qlocation: https://trac.macports.org/ticket/70477 |
|
Does anything in this discussion relate to Homebrew?
Note from upgrading Qgis with Sequoia:
qgis is built for Intel macOS and so requires Rosetta 2 to be installed.
You can install Rosetta 2 with:
softwareupdate --install-rosetta --agree-to-license
Note that it is very difficult to remove Rosetta 2 once it is installed.
Seems to work, but wouldn’t open old projects from app, had to click on the qgz file and it opened.
… On Sep 23, 2024, at 11:39 AM, Aidan Gibson ***@***.***> wrote:
Is this being worked on in any capacity? Thanks
—
Reply to this email directly, view it on GitHub <#46299 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABB5KHUQ7ZM7S7EEAUZA5DZX6EPJAVCNFSM5JDABK52U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZWG4YTONZRHE2Q>.
You are receiving this because you commented.
|
|
Just a note to confirm that I've successfully built AS-native QGIS3 on Sequoia with MacPorts, but only the base app - no plugins, with You have to install the ports The plugin ports all are still relying on clang 14 and will not be installable on Sequoia until that is fixed. |
Thanks @MaintenanceCosts |
|
On my computer the error message has changed now. The latest one is:
…---> Building qt5-qtlocation
Error: Failed to build qt5-qtlocation: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qtlocation/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe
there
is a bug.
Error: Processing of port qgis3 failed
Any updates on this topic?
On Wed, Sep 25, 2024 at 11:17 PM Okky Mabruri ***@***.***> wrote:
Just a note to confirm that I've successfully built AS-native QGIS3 on
Sequoia with MacPorts, but only the base app - no plugins, with
-plugin_support312.
You have to install the ports boost and boost181 (yes, both of them,
redundantly) before trying to build qgis3 in order for qt5-qtlocation to
build correctly.
The plugin ports all are still relying on clang 14 and will not be
installable on Sequoia until that is fixed.
Thanks @MaintenanceCosts <https://github.com/MaintenanceCosts>
Works for me on M2 Chip with macOS 15 (Sequoia):
port install boost boost181
port install qgis3 -plugin_support312
—
Reply to this email directly, view it on GitHub
<#46299 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6MO3PNMMNBZWD7YTU75ETZYN4EDAVCNFSM5JDABK52U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZXGU3TOMBZGI4A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
That is reported with https://trac.macports.org/ticket/70477 |
|
I tried building QGIS on my ARM MacBook, followed all the instructions, but gave up when I kept getting bombarded with warning about the many unsigned libraries the build tried to load in. All the dependencies the tar.gz has in it are available through either pip or Homebrew. EDIT: |
I have tried this one on my M3 air. However, after a while it stuck with the below error: Do you have any idea to fix this? |
I can confirm this worked for me on an M3 Macbook Pro. Great to have QGIS running on Apple Silicon again. Thanks! |
|
After two years or so without easy access to a Mac, due to my changing of job, I’m more or less back on line again.
Question: what Qt version do you use? Apparently Qt6 doesn’t work on the latest 10.15? So we’re still stuck with qt5?
Vincent
|
This looks to solve the issue - a pre-packaged installed for QGIS ARM64 Apple Silicon. Excellent. Thank you! |
Is that build "so unofficial"? I mean.. It is an opensource software.. Could it be "so official"? |
|
That build is basically packaging the conda version of qgis which is being maintained upstream. I use the conda version for quite a while now and while not ideal (and not something you can expect most people to use), it has been working quite well. I'd say I have more incompatibilities with plugins and the current QGIS python version than with the build itself. I imagine the reason it is not being promoted in the qgis website is because most people will not want to use the command line for conda, and because the qgis-conda-builder repository is not being actively maintained. |
|
Also, intel and silicon builds can coexist but I wouldn't recommend it. Partly because it seem unnecessary if it's the same version, but also because QGIS sometimes uses Env variables in the settings, and these would have to change depending on the architecture build (and you can't easily have different settings for the same QGIS3). |
|
@jcm What does one do with https://github.com/opengisch/qgis-conda-builder/. I'm not a conda user, but would like a native QGIS. In the mean time I'm trying This obviously is not what is desired. Thanks for any help |
|
I think the overall goal here should be is to offer a binary that one can just download from the offical website. Dealing with conda is way beyond the ability of most users. |
you download from the release section
i think that was the goal with the conda-builder. but somehow it was kinda abandoned after finishing it which is surprising b/c the QEP to do this was only approved as a special decision after it was first rejected and there was a bit of "backlash" (if you can call it that even) from macOS users frustrated by old libaries. I think it is the goal but nobody seems to care enough to create a proper en par solution.... |
|
I feel I need to chime in here since there seems to be a bit of confusion going on. As for the other implementations:
The binaries from qgis-conda-builder, as far as I'm aware, are all built from the conda-forge formula above and are up to date. They are simple installers and this should be the preferred method to use qgis natively on apple silicon for users that prefer a graphical user interface. Personally, it should also replace the macports link on qgis.org. We can, and should, refer to macports and conda builds in qgis.org, but they really serve a very different audience. So yes, it does seem abandoned, but it is working and new versions are released soon after they're published by QGIS, largely due to the fact it is feeding of the official conda-forge feedstock channel. I have not encountered major issues in the conda version (whether installed from conda, or the conda-builder binary). That does not mean they do not exist - they do, but these issues probably need to be solved upstream and have little to do with the actual packaging. I personally doubt we will see a properly maintained Apple Silicon version before QGIS v4, and I do wish the QGIS group would adopt a cross-platform packaging workflow. This worries me quite a bit. The migration from qgis 2 to 3 was not without headaches for plugin developers. With qt6 coming in QGIS v4, I imagine it will be even more complex. |
|
Amazing summary Joao, thanks! In summary, if you are not very technical leave your Mac aside and do your GIS work on a PC. This is what I do. Forget about loosing time trying to make it work, the bugs, etc. QGIS on a PC just works fantastic. It's a shame, but at the same time it's an open source software community, so you can't really expect the level of service from a corporate software solution. |
|
Thanks for the summaries. In my limited use of such things, Homebrew seems to be the preferred solution over MacPorts. I say that based on more libraries and apps offer Homebrew installations as a solution. Also can often just substitute |
@joaoponceleao Unfortunately that's not really the case. First, many users can't open it at all. Even if the the launch command can be given, the app still doesn't start. And even if it does, it's not an ARM64-native app so it still needs Rosetta to run.
This one actually works, thank you for mentioning it!! :) |
|
"To install it you just need to download the latest (or desired) release .pkg file for your architecture (arm64 for apple silicon) from https://github.com/opengisch/qgis-conda-builder/releases, and double click. It will install and you can run it. There will be an error when you open QGIS, but this can be ignored." Download path: https://github.com/opengisch/qgis-conda-builder/releases/download/3.40.1/QGIS-3.40.1-MacOSX-arm64.pkg When try to open QGIS 3.40.1 MacOSX.pkg: Tried Control Open too with same response. Sequoia. Can you verify this @joaoponceleao since it seems to contradict what you wrote? |
This is a problem since the last update of Sequoia. You have to go to System Preferences -> Privacy and Security and click open anyway. You can only do that immediately after the unsuccessful launch of an app.
Screenshot source and more details at: https://support.ujam.com/hc/en-us/articles/15955153878940-macOS-15-Sequoia |
|
The issue with any program not launching due to an "error" reported by MacOS is simply a security measure from Apple. Before Sequoia you had to right click and press open (sometime twice) on first launch to override. With Sequoia there are new security measures in place. To be frank, this is something that the QGIS.org should look into as all that is necessary is a paid Apple developer account to sign it, and if QGIS is going to be funding the packaging, than this should be part of the funds. This is only for the downloaded pkg binaries. Using conda from the terminal is fine, and you can easily create an icon and launcher for it using automator if you like. There are still issues with some tools, but these are issues that come and go on Windows as well so it's something that needs to be looked upstream. Personally, if you want an easy to use system, I would just download and install the intel version from the qgis.org website and run it under Rosetta. That one is quite stable. If you want a little bit more performance or need to install python dependencies, than the conda arm version may be better. |
and others
Feature description
A build of QGIS that runs natively on M1 Macs would be great to see.
https://doesitarm.com/app/qgis/
Additional context
No response
The text was updated successfully, but these errors were encountered: