Well, on the website it says the binary works on MacOS 10.10+, but this is clearly not the case.
Many users of your software are academics who don't know how to compile or install homebrew, or find that it's a hassle (needs maintaining and updating), or breaks things etc. Installing a simple binary was the natural option.
In my opinion, it would be far more valuable to have compatible binaries that people can use, rather than compiling against the latest QT and expecting users to compile or install other things that can break or need updating, maintaining etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
support for "legacy" systems is rather cumbersome since we support quite a number of different OS.
If someone provides a recipe to build it automatically on travis-ci, we can discuss, but otherwise no steps are taken. Using homebrew is not complicated at all. Otherwise you can update to a newer OSX version anyway.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't say I understand this decision. You bundle QT in the windows version and don't require windows users to install and maintain additional packages ... why not do the same for MacOS?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no decision not to support older OSX. The point is that using up-to-date tools, older OSX is not supported, basically declared obsolete. Supporting older versions is not easily achieveable using travis build environment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Screenshot: https://i.gyazo.com/17af8c529b365f6d0db7c85b95338847.png
lastest qt needs osx 10.12+
We don't offer other builds, but you can use homebrew without much trouble. (brew.sh)
Well, on the website it says the binary works on MacOS 10.10+, but this is clearly not the case.
Many users of your software are academics who don't know how to compile or install homebrew, or find that it's a hassle (needs maintaining and updating), or breaks things etc. Installing a simple binary was the natural option.
In my opinion, it would be far more valuable to have compatible binaries that people can use, rather than compiling against the latest QT and expecting users to compile or install other things that can break or need updating, maintaining etc.
support for "legacy" systems is rather cumbersome since we support quite a number of different OS.
If someone provides a recipe to build it automatically on travis-ci, we can discuss, but otherwise no steps are taken. Using homebrew is not complicated at all. Otherwise you can update to a newer OSX version anyway.
I have updated the minimum OSX version to 10.12 on the webpage
I can't say I understand this decision. You bundle QT in the windows version and don't require windows users to install and maintain additional packages ... why not do the same for MacOS?
There is no decision not to support older OSX. The point is that using up-to-date tools, older OSX is not supported, basically declared obsolete. Supporting older versions is not easily achieveable using travis build environment.