Opened 14 years ago
Closed 14 years ago
#29024 closed update (fixed)
qt4-creator-mac: update to 2.1.0
| Reported by: | tvb377@… | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | haspatch | Cc: | trojanfoe@… |
| Port: | qt4-creator-mac |
Description (last modified by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez))
patch for Portfile and updated patchfile for sources attached.
Attachments (2)
Change History (11)
Changed 14 years ago by tvb377@…
| Attachment: | patch-remove_build_types.diff added |
|---|
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | mcalhoun@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to mcalhoun@… |
| Summary: | upgrade qt4-creator-mac to 2.1.0 → qt4-creator-mac: update to 2.1.0 |
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Note that the initial revision for a new version should be 0.
Changed 14 years ago by tvb377@…
| Attachment: | qt4-creator-mac.Portfile.patch added |
|---|
same patch with revision 0
comment:4 follow-up: 5 Changed 14 years ago by trojanfoe@…
Can anyone tell me why Macports doesn't use 2.1 instead of 2.0.1 anyway, given how long ago it was released?
I am suffering from Force-Quits with 2.0.1 and I suspect it's related to the code parsing used in creator to provide the equivalent of 'IntelliSence' (in MSVC terms).
comment:5 follow-up: 6 Changed 14 years ago by trojanfoe@…
Replying to trojanfoe@…:
Can anyone tell me why Macports doesn't use 2.1 instead of 2.0.1 anyway, given how long ago it was released?
I am suffering from Force-Quits with 2.0.1 and I suspect it's related to the code parsing used in creator to provide the equivalent of 'IntelliSence' (in MSVC terms).
Apologies: It was released March 1st 2011, which isn't 'long ago'.
comment:6 follow-up: 8 Changed 14 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
| Description: | modified (diff) |
|---|---|
| Status: | new → assigned |
Replying to trojanfoe@…:
Replying to trojanfoe@…:
Can anyone tell me why Macports doesn't use 2.1 instead of 2.0.1 anyway, given how long ago it was released?
I am suffering from Force-Quits with 2.0.1 and I suspect it's related to the code parsing used in creator to provide the equivalent of 'IntelliSence' (in MSVC terms).
Apologies: It was released March 1st 2011, which isn't 'long ago'.
The only delay is the fact that I am trying to track down a bug in which creator does not find the header files in the standard locations.
For example, iostream is underlined and given a warning that it can not be found.
After I fix the problem, I will test it and commit the update.
Sorry for the delay.
comment:7 Changed 14 years ago by eborisch (Eric A. Borisch)
Is this perhaps an upstream bug? (I know that bug is for linux, but perhaps it should be *nix) ... sounds like the exact same issue.
If it is, I'd say go ahead and upgrade to 2.1 (the patches applied here worked fine for me to build and run) -- the editor has the underline warnings, but (my) projects compile fine. Much less of an issue than the force-quits (in 2.0.1) reported above.
comment:8 Changed 14 years ago by trojanfoe@…
Replying to mcalhoun@…:
The only delay is the fact that I am trying to track down a bug in which creator does not find the header files in the standard locations.
For example, iostream is underlined and given a warning that it can not be found.After I fix the problem, I will test it and commit the update.
Sorry for the delay.
I seem to remember that the same problem existed in 2.0.1? I cannot see now as I have switched to 2.1 via my local macports repo, and I think it's *much* better than 2.0.1 (it seems quicker and has a class viewer). Being able to see standard header files would be a great addition as well though :)
comment:9 Changed 14 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed in r78078.
updated source patch