- User Since
- Apr 18 2015, 12:24 AM (272 w, 6 d)
Jan 10 2020
I may be misunderstanding this, but if Qt builds against a 10.13 target and we build frameworks against 10.12, is there any chance of breakage?
I can't think of any immediate problems since it should just mean Qt can use new APIs and no longer uses old deprecated ones.
Jan 5 2020
Nov 28 2019
Sep 26 2019
I originally tried to make the qt5 version installed by homebrew usable for KDE frameworks (e.g. find syntax files etc.) Currently you have to manually create symlinks in $HOME to /use/local/ to allow applications to find stuff. See https://github.com/KDE-mac/homebrew-kde/blob/master/tools/do-caveats.sh
Aug 5 2019
Jun 8 2019
Jan 8 2019
Sorry, was busy with other stuff so completely forgot about this. I'll update this soon.
Oct 23 2018
Makes sense, I didn't think about multiple languages being set when I wrote that code.
Sep 19 2018
Looks good to me.
Sep 14 2018
I haven't tried the QtSDK parts yet, but the blacklist seems to work.
Sep 13 2018
I can confirm that this fixes the build for me.
Pick a name that shows that it is a boolean
Add missing newline
Build using autotools on non-Windows systems since that is the supported way.
Ah yes of course I didn't think about that. How about self.subinfo.options.configure.defaultAutoreconfIncludes = False? So far the only thing that was necessary is to not add the default include path.
I have needed this for 3 packages now (libunistring, libtasn1 and aqbanking). Do we really need to override the project aclocal files with the ones from the craftroot? According to the mailing list message prefix/share/aclocal will be searched automatically.
Sep 12 2018
I guess the other option is to just use the autotools build for linux/mac?
I found https://github.com/acmepjz/djvulibre with cmake build system, should we be using that instead?
Sep 11 2018
Sep 10 2018
Fix typo in comment
Sep 9 2018
According to http://doc.qt.io/qt-5/supported-platforms.html the minimum version is 10.11 so this should be fine.
As long as we update this version whenever Qt doesn't build keeping it in sync shouldn't be too difficult.
I also don't think it would be a problem if the minimum supported macos version for other software is lower than the Qt minimum.
Sep 5 2018
Sep 4 2018
Sep 3 2018
Aug 28 2018
It should be easy to detect whether we are in a bundle or not. I can also check if the current executable is below qtpaths --install-prefix and if so add $(qtpaths --install-prefix)/share.
Aug 25 2018
Remove debug echo