-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qt6-qtcreator: new port #26740
qt6-qtcreator: new port #26740
Conversation
Notifying maintainers: |
39ee8e2
to
97b1aa7
Compare
this doesn't seem right. You commented on another PR that the version you're updating the port here uses Qt6; so that should certainly not be called "qt5-...". |
@reneeotten , as I see, Qt Creator 7.0.0 is based on Qt 6.2.3 and only uses the cmake build system, so Qt Creator 6.0.2 is the latest qt5-qtcreator. |
97b1aa7
to
1911491
Compare
1911491
to
be44b6d
Compare
be44b6d
to
688c8b4
Compare
@reneeotten Hi, I'm not sure I did everything right. This PR no longer a port update. So, it will be new port, port fix or can be closed (and there will be separate PR)? I also update the qt creator version from 14.0.2 to 15.0.0 (it was released recently) |
I will try and take a look at this in the weekend. |
688c8b4
to
fc2de9e
Compare
This looks good, I'm ok merging it, but I'd like to get a second opinion from @reneeotten who's kinda the new qt maintainer/expert around here. Edit: thanks for this, BTW - I haven't been able to get qtcreator working until this port - I think the other version was just to old for my setup. |
Description
Portfile has been updated for the new Qt Creator version:
Type(s)
Tested on
macOS 15.1 24B83 x86_64
Xcode 16.1 16B40
Verification
Have you
port lint --nitpick
?sudo port test
?sudo port -vst install
?