Is the project still in need of a maintainer/developer?
Is there enough of a user base and interest out there to be worth the work?
It’s a bit hard to tell.
Regards…
Is the project still in need of a maintainer/developer?
Yes, we are looking for motivated and talented people.
Is there enough of a user base and interest out there to be worth the work?
What do you mean? There are quite a few users and its the only opensource compositor available, so yes, it will be worth a lot!
I’ll break a Mac out of the closet and check out the build situation.
1 Like
Tried building on MacOS using Homebrew to manage everything and just know that the guide for building is a little out of date and is currently broken with Homebrew. Would recommend using MacPorts as that is the suggested config.
I do have a version with some updates for Catalina but since I was never able to get it working I didn’t submit a PR for it.
Thanks for the heads up Shrinks99.
I know how crazy build environments can be if something is packed with other third party source, lots of opportunities for endless (and difficult to satisfy) dependencies, or feature/performance problems like you hit with something like FFmpeg.
Hopefully you have better luck than I do! You can find my version of the guide here though your mileage may vary. If you run into any problems or find that anything I’ve done is incorrect (I’m not really a programmer 
) please let me know along with additions if you have anything to fix. Would like to get the build guide updated so that others have an easier time contributing!
@Shrinks99 feel free to make a PR with your changes to the guide.
homebrew is not playing nicely with older systems and software: my 2010 MBP can only run up to 10.13, and just got deprecated by homebrew, when MacPorts still supports 10.4! Qt4 for homebrew was maintained by Carter Sande (cartr@github) until recently, but maybe it’s broken now. And I can’t seem to be able to get Qt4 from cartr/qt4 on my MBP 2018 running Big Sur.
MacPorts brings more support for everything we need an more, plus they are more open to contributions when you want to fix something for an older system or library.
@Shrinks99 I saw the changes in you github. Actually the correct spelling for Apple’s desktop OS is macOS, not MacOS:
- it was “Mac OS” until Mac OS 9
- it was “Mac OS X” from Mac OS X 10.0 to Mac OS X 10.7
- it was “OS X” from OS X 10.8 to OS X 10.11
- it is now “macOS”, since macOS 10.12
1 Like
Looks like I’ve gotta adjust some capitalization! Hopefully I’ll get around to this on my winter break, admittedly I’ve kinda been holding off on trying it again until everyone gets around to the QT 5.12 update.
Also don’t get me wrong, I’m in no way against MacPorts. Homebrew is just my package manager of choice and I really don’t want to install two different ones. One thing they tend to specifically not do is maintain old / deprecated versions of software though so I can see how that poses an issue. Another thing this guide is missing for Homebrew users is that they need to install pyenv because Homebrew only maintains the latest version of python and you’ll need to switch to a different one than is installed with the system.
I have Python 2 from hombrew: brew install python@2
But they will very probably remove it pretty soon (because it’s officially deprecated).
Already gone, must be a previous install.
Which Mac? Does it have AMD gpu?