qt6: Add initial qt6 ports #12676
qt6: Add initial qt6 ports #12676
Conversation
|
thanks @jhoyt4 for this! I started myself two weeks ago or so using the |
I took a similar approach - this versions should be close to qt5 with pieces removed (especially the docs code) to get an initial Portfile / qt6 group working.
Again correct and intentional. Not everything works out of the box and some of the modules have new / updated dependencies. I worked on a handful to show proof of concept figuring more can be added later.
Yep - that was not a fun piece to figure out. Thankfully the cmake 1.1 group is close to what was needed to get the modules compiling. Thanks for the help! I'd be very happy to look at/factor in whatever work you've done (or vice versa have you modify your work and I close this PR). |
|
It looks like QT just dropped QT6.2.1, so I'll be updating this to that version. I'm also now struggling to compile qt6-qtbase - I uninstalled qt5 from my machine to test some issues and now it won't line. This PR certainly could use the WIP label... |
I'm happy to add the label. But you can also change the status of this to Draft, while you're making changes. That will prevent anyone from prematurely merging. Once you're done, change the status to Ready for Review. |
|
Those last two force pushes have fixed the build process (needed to force qt-base as a depend for all sub ports), updated the ports to 6.2.1, and removed an unnecessary opengl path patch (I should have removed it from the original submission as it didn't solve any real problem). Last night's push seems to have gotten everything through lint and build checks - so I think I'm close. Still happy to get more eyes on this if anyone has the time to test it further. |
Awesome! While my QT-related knowledge is a bit light, I'll try to take a closer look over the coming days. I'd encourage more QT-savvy folks to jump in as well, though. |
|
@jhoyt4 FWIW, I got an error trying to install it on my brand new Monterey/M1 Max laptop (main.log). That being said, this is my first time testing a new port, so I may well have messed up at some point. Here is what I did for reference:
Background: I'm on a mission to have PySide2 5.15.2 (or at least PySide6) run on Apple silicon. I've managed with the official Qt6 distribution built from source, but having that part sorted out by MacPorts would be great. |
@abey79 That should have got it running. The error you're seeing is similar to the one I saw a couple days ago that I resolved by removing "use Xcode" from the portfile. I wonder if Monterey has something new in the SDK that's causing the issue. The other thought is do you have qt5 installed? I uninstalled it on my x86 machine and things are compiling (...that being said, it's also installed on my M1 mini and things compile there as well...) |
|
@mascguy - it looks like I got everything through the lint and build process. Basic QT6 functionality seems to be working on my machines as far as I've tried tested. @kencu - any chance you have some spare cycles to look over the Portfile. You were a huge help last year when we got qt5 [mostly] working |
|
@jhoyt4 Not that I know what I'm doing, but I tried to add As for Qt5, I don't have installed (with MacPort, that is) because this fails. Here is the related error log, should it have any relevance. The errors are different though ( Edit: if this helps, I'm happy to make myself available for further Monterey testing in the coming days, including with a more "real time" interaction if needed/practical. |
|
@abey79 This probably isn't the right place to help you troubleshoot qt5 - take a look at this trac ticket https://trac.macports.org/ticket/63154. Also, it appears a PR was just issued for SDK12. I'll have to see if the new patch file can be grafted into this PR to help with qt6 issues. Also - just to verify, you have commandline tools installed? |
@jhoyt4 yeah totally. I just posted there in case it could have any relevance to this particular issue. Thanks for the pointer though.
You mean Xcode command line tools? Yes, I do have them installed.
It does. I could install qt6 successfully after updating. |
|
That last commit should fix a lot of issues for applications that use cmake to build. The main problem was that shifting to building moduls with cmake broke the Portfile's mechanism to symlink the lib/cmake files. |
|
Converting back to draft as I work through a TON of new dependency issues as I try to bring additional qt submodule features online The majority of these are induced by qtdeclarative trying to get qtquick working threading QtQuick through the rest of the ports |
|
I've been hammering away trying to resolve an issue where optional features in a TON of the modules fail to configure if QtQuick (installed by qtdeclarative) is available. This all started after I added qtshadertools which qtdeclarative automagically picks up as a dependency. My current thoughts are that I am going to remove qtshadertools from the portfile / dependencies to get things building / an initial cut at the Portfile ready for submission. This way we at least get some qt6 functionality (i.e. a default build) working and available. |
|
|
Assuming I just fixed the conflict with qt-base and the SQL-plugins (i.e. it gets through the lint and build checks), I'll be marking this "Ready for review" |
|
That rebaseline should pull in openssl 3, we'll see how this goes... |
Currently, there is an issue where the existance QtQuick induces an
error in most qt modules as they attempt to link against QtQuick
QtQuick is installed optionally by QtDeclarative if qtshadertools
is located.
…ensors, webchannel, and websockets qt6: configure flag and dependency clean up, add qtremoteobjects, qtsensors, webchannel, and websockets
… based build to better align with Qt's build guide
Additionally fix the cmake file patching mechanism to be recursive
… by the appropriate subports
@mascguy - followed your tip on the other PR to rebase [hopefully] the right way |
|
Looks like it built with openssl3. I also just finished building qt6-qtbase on macOS 12.0.1 21A559 arm64 / Xcode 13.1 13A1030d without any issues. |
Haven't scrutinized every line, but looks great overall! Are you ready for us to merge this? |
|
I think I'm ready for the merge - would still have liked another few sets of qt-saavy eyes on it. Either, way, I'll keep an eye on trac to help troubleshoot any tickets that pop up. |
|
@reneeotten @kencu - Any chance you two have some additional time to look over the Portfile before it gets merged? |
|
Could we please not add plugins for end-of-life versions of MariaDB (5.5, 10.1, maybe even soon-to-be EOL 10.2)? It would be easier to propose removing old versions of MySQL, MariaDB, etc. if there weren’t so many ports/variants still depending on them. |
There was a problem hiding this comment.
I believe qt6-qtbase as proposed is affected by https://trac.macports.org/ticket/62104: qtbase opportunistically enables Vulkan support if Vulkan headers are detected on someone’s system, which may lead to build failure. If others approve of the fix I proposed in #12837 (explicitly disable Vulkan support), I suggest incorporating it into qt6-qtbase as well. Although, it may be desirable to eventually explicitly enable Vulkan support.
Do not opportunistically enable Vulkan support (maybe it can be explicitly enabled later if desired) Fixes: https://trac.macports.org/ticket/62104
|
@chrstphrchvz - Done. I have removed the EOL database plugins, but if its still reported to be developed (i.e. mariadb-10.2, mysql5.7) I have left it in the portfile. @mascguy - should I squash all commits into one? I left them as multiple to help any reviewers understand what was changing while this was a WIP. |
I'm fine with leaving them as multiple commits, to maintain the history. Does anyone have an objection to that? |
|
The CI builds passed, so let's merge. Awesome work @jhoyt4! |
|
thanks @jhoyt4 ! I am sorry but haven't had the time to take a thorough look at this - will give it a spin myself locally and see if I can get some more things to build and/or if changes are needed. (The commits should have been squashed, or perhaps one for the PG and one for the |
As a note, an open GitHub pull requests shows all of the times when its branch was force-pushed, and all of the previous commits are still available. (I would still squash at least whenever there are changes which should be made simultaneously.) |
Description
Adds some initial QT6 capabilities / sub ports.
Additional subports will be added in future PR's - this PR is mainly to get an initial set of qt6 based sub ports working.
Happy to have another set of eyes on this for tips and/or help
Closes Ticket 62982
Type(s)
Tested on
macOS 11.6 20G165 x86_64
Xcode 13.0 13A233
AND
macOS 11.6 20G165 arm64
Xcode 13.0 13A233
Verification
Have you
port lint?sudo port test?sudo port -vst install?"tested basic functionality of all binary files?" - qt6 is rather expansive - saying that I could check all executables would be a stretch....