Re: about Qt 5.x and OS X 10.6
On Mar 20, 2015, at 4:46 PM, René J.V. Bertin rjvber...@gmail.com wrote: So I am now exploring an option that may be a bit unusual: OS-specific port versions. Nothing as fancy as it seems: for OS X 10.6 users port:qt5-mac-devel will appear to be at 5.3.2 and for all other users it will appear to be at 5.4.x . I'm aware that this could set precedence It wouldn't; the ld64 port used to do this until very recently. vq Sent from my iPhone ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: about Qt 5.x and OS X 10.6
On Saturday March 21 2015 12:08:03 Craig Treleaven wrote: Just one data point, but the next version of MythTV (0.28) is going to require Qt 5.2 at a minimum. Their reasoning: Well, there is already a Qt 5 in MacPorts. Except that until now installing it conflicts with port:qt4-mac ... So I think if we can support Qt 5.3 on OS X 10.6, that would be ideal. Of course it still remains The current port:qt5-mac is Qt 5.3.2 . The fact it doesn't co-install with Qt 4 is just one of its issues, but it *should* build on 10.6 . I solved the co-installability issue, then migrated the port to 5.4.x and resolved other issues as I ran into them. I'm now looking into backport that to Qt 5.3.2, as said ideally with if/else constructs in a unique Portfile. That's proving to be more of a challenge than I thought and I haven't yet managed to put the finger on the difference that causes my build to fail. I've been breaking out the directory-diff tools in what's a nice stress-test of those very tools (given the size of a Qt source tree ...) OTOH, Core2 Duo macs can run OS X 10.7 so the door is open for them to support Qt 5.4, I suppose. AFAIAC the argument is not just whether a system can run a newer OS version. It's been only a few months now that I'm running 10.9; until mid december 2014 I was under 10.6.8 simply because 1) it worked just fine and fast 2) I had no reason to upgrade and 3) I had a good reason not to: Rosetta and a couple of licenses for PPC versions of Adobe software I'm not going to renew as long as I have a way to keep running the versions I already own. R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: about Qt 5.x and OS X 10.6
On 22 Mar 2015, at 3:00 am, macports-users-requ...@lists.macosforge.org wrote: Just one data point, but the next version of MythTV (0.28) is going to require Qt 5.2 at a minimum. Their reasoning: Well, there is already a Qt 5 in MacPorts. Except that until now installing it conflicts with port:qt4-mac ... So I think if we can support Qt 5.3 on OS X 10.6, that would be ideal. Of course it still remains The current port:qt5-mac is Qt 5.3.2 . The fact it doesn't co-install with Qt 4 is just one of its issues, but it *should* build on 10.6 . I’ve got 5.3 and 5.4 running from the Qt installer digression: what a pain to install like 12 hours each for a customer 1 installed the licensed version, boy complete install in an hour ie you pay you get fast downloads Why can’t / doesnt macports do what Qt does - a complete directory for each install eg for me /opt/Qt5.3 /opt/Qt5.4 the only file I *need* to access is qmake. I guess the versions of designer and creator need to be wellKnown too. James ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
about Qt 5.x and OS X 10.6
Hello, As you know I've been investing quite a bit of work in bringing Qt 5.4.x to MacPorts, and to make Qt 5 co-installable with Qt 4. In fact, I started with the latter, and then moved on to the former. And in that 2nd step I completely forgot that Qt 5.4.x no longer build on OS X 10.6 (and earlier). I don't like the idea of holding off on Qt 5.4 for the sake of SL (much as I love it), nor do I like the idea of dropping Qt 5 support for SL (because I love it too much for that :)) So I am now exploring an option that may be a bit unusual: OS-specific port versions. Nothing as fancy as it seems: for OS X 10.6 users port:qt5-mac-devel will appear to be at 5.3.2 and for all other users it will appear to be at 5.4.x . I'm posting this on macports-users (instead of ~-dev) to see if 1) this is a viable and acceptable approach (for the core devs) and 2) an appreciated approach (for the users). I'm aware that this could set precedence, because it might well be that Qt 5.5 will no longer build on OS X 10.7 (and 5.6 on 10.8 and so forth). As far as I'm concerned this approach allows me to centralise portfile development and maintenance in a single file. I foresee to re-evaluate the situation when Qt 5.5 is released; if necessary I'll create a qt53-mac port for SL and move Qt 5.4.x to the legacy fallback code in the qt5-mac port, but that's not the only option to keep the main portfile complexity in check. Thanks, R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
