Opened 10 years ago
Closed 8 years ago
#47329 closed update (fixed)
update: qt5-creator-mac
Reported by: | RJVB (René Bertin) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | qt5-creator-mac |
Description
I've updated port:qt5-creator-mac to 3.3.2, and gave it a -devel subport that currently builds 3.4.0.398 . It's been tested with my qt5-mac-devel port (Qt 5.4.1 or 5.3.2 on OS X 10.6) but might build against the current port:qt5-mac too.
Port files are in github: https://github.com/RJVB/mp-port-repository/tree/master/devel/qt5-creator-mac
Attachments (4)
Change History (11)
Changed 10 years ago by RJVB (René Bertin)
Attachment: | 2QtCreators.png added |
---|
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Instead of referring us to your github repository, you should attach your unified portfile.diff and any new or updated patchfiles to this ticket so that we can see what changes you are proposing. One change I see, for example, is that you are disabling the universal variant, with the comment "no point in building this one universal really, nowadays". At this time we still want to support universal builds in MacPorts. Any movement to change that policy should first be discussed and agreed upon on the macports-devel mailing list. If this port doesn't actually build universal successfully, that's another matter, and in that case, the comment above the universal_variant no
line should explain that, saying what error or problem occurs, referring to the upstream bug report or mailing list post where this is reported or discussed, etc.
comment:2 Changed 10 years ago by RJVB (René Bertin)
What I ought to have done I guess is first commit the current/stock port dir to my repository, and then make my changes. That way anyone could see the changes without additional work. Let me see how I can rectify that.
As to universal builds: I fully agree where libraries are concerned, for obvious reasons. For rather (and methinks equally) obvious reasons I don't see the point in building an IDE in universal mode, not any more than building vim or any other tool that doesn't install libraries for use by 3rd parties. Digia also no longer supports building in 32 bit mode and if memory serves me well it wasn't overly straightforward to build Qt 5.4 that way.
That said, I don't mind removing the disable, and I'll try to help if/when there are building issues, but I don't have the resources to maintain a universal Qt install to test it myself.
comment:3 Changed 10 years ago by RJVB (René Bertin)
comment:4 Changed 9 years ago by RJVB (René Bertin)
Creator 3.4.0 has been out for a while now: I bumped qt5-creator-mac to this version, and qt5-creator-mac-devel to the current git/head.
Changed 9 years ago by RJVB (René Bertin)
Attachment: | patch-missing-botan-headers.diff added |
---|
Changed 9 years ago by RJVB (René Bertin)
Attachment: | patch-coreplugin+CoreServices.diff added |
---|
Changed 9 years ago by RJVB (René Bertin)
Attachment: | qt5creatormac.diff added |
---|
comment:5 Changed 8 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Owner: | changed from macports-tickets@… to MarcusCalhoun-Lopez |
---|---|
Status: | new → accepted |
comment:6 Changed 8 years ago by RJVB (René Bertin)
This ticket is so old and I use Creator so little that we can just as well drop this.
comment:7 Changed 8 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Cc: | mcalhoun removed |
---|---|
Resolution: | → fixed |
Status: | accepted → closed |
Closing at reporter's request.
Qt creator is currently at the latest version.
qt-creator 3.4.0 Beta1 running in Cocoa and X11 mode