Opened 12 years ago
Last modified 4 years ago
#35745 assigned update
Port for for kcachegrind 0.7.1
Reported by: | rwc@… | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | mp@…, dstaple@…, cdeil (Christoph Deil), trolin421, bob@…, alex@…, cjones051073 (Chris Jones), cooljeanius (Eric Gallager), NicosPavlov, devernay (Frédéric Devernay) |
Port: | kcachegrind |
Description
This is the portfile for the latest release of kcachegrind. The previous release 0.4.6 used the old kdelibs3. This version now uses qt4. I've tested it on my Mountain Lion system only.
Attachments (4)
Change History (31)
Changed 12 years ago by rwc@…
comment:1 Changed 12 years ago by mf2k (Frank Schima)
Keywords: | portfile removed |
---|---|
Type: | submission → update |
Version: | 2.1.2 |
Please supply a unified diff of the current portfile so we can easily see the changes you have made.
Changed 12 years ago by rwc@…
Attachment: | portfile.diff added |
---|
Diff between versions of the portfile
comment:4 follow-up: 5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | haspatch added |
---|---|
Owner: | changed from macports-tickets@… to ryandesign@… |
Status: | new → assigned |
This new port installs "qcachegrind", not "kcachegrind". Would it therefore make sense to rename the port to "qcachegrind"?
comment:5 Changed 12 years ago by rwc@…
Replying to ryandesign@…:
This new port installs "qcachegrind", not "kcachegrind". Would it therefore make sense to rename the port to "qcachegrind"?
I left it kcachegrind as the original project is still named kcachegrind and most uses are familiar with kcachegrind. But I agree that it is confusing since the installed app is qcachegrind.
comment:6 follow-up: 8 Changed 12 years ago by dstaple@…
comment:8 follow-up: 9 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to dstaple@…:
kdelibs3 doesn't build on Lion or Mountain Lion, so right now many users can't install kcachegrind
Correct. That is why we want to update kcachegrind to a version that works with Qt 4, as per this ticket.
comment:9 follow-up: 14 Changed 12 years ago by dstaple@…
I installed your Portfile in a local repository and can verify that it works on my system with OS X 10.8.2 and Xcode 4.5.2.
Replying to ryandesign@…:
Replying to dstaple@…:
kdelibs3 doesn't build on Lion or Mountain Lion, so right now many users can't install kcachegrind
Correct. That is why we want to update kcachegrind to a version that works with Qt 4, as per this ticket.
comment:14 Changed 12 years ago by dstaple@…
After having used this version of kcachegrind for several months, I can now say that it doesn't work very well on my OS X 10.8.2 system after all. It "works" somewhat: it launches, doesn't crash, and gives some useful results. However, CPU time is falsely attributed to function calls that never occur. This happens all the time with the software that I'm profiling. I haven't spent a lot of time figuring out the exact circumstances that make the bug occur, but I could do that if someone is maintaining the port and wants the info.
Replying to dstaple@…:
I installed your Portfile in a local repository and can verify that it works on my system with OS X 10.8.2 and Xcode 4.5.2.
Replying to ryandesign@…:
Replying to dstaple@…:
kdelibs3 doesn't build on Lion or Mountain Lion, so right now many users can't install kcachegrind
Correct. That is why we want to update kcachegrind to a version that works with Qt 4, as per this ticket.
comment:16 Changed 12 years ago by cjones051073 (Chris Jones)
Note that KDE4's version of kcachegrind is provided as part of kdesdk, so there is little point updating this port to KDE4.
Chris-Jones-Macbook-Pro ~ > sudo port contents kdesdk4 Password: Port kdesdk4 contains: /Applications/MacPorts/KDE4/cervisia.app/Contents/Info.plist /Applications/MacPorts/KDE4/cervisia.app/Contents/MacOS/cervisia /Applications/MacPorts/KDE4/cervisia.app/Contents/MacOS/cervisia.shell /Applications/MacPorts/KDE4/cvsaskpass.app/Contents/Info.plist /Applications/MacPorts/KDE4/cvsaskpass.app/Contents/MacOS/cvsaskpass /Applications/MacPorts/KDE4/cvsaskpass.app/Contents/MacOS/cvsaskpass.shell /Applications/MacPorts/KDE4/kapptemplate.app/Contents/Info.plist /Applications/MacPorts/KDE4/kapptemplate.app/Contents/MacOS/kapptemplate /Applications/MacPorts/KDE4/kapptemplate.app/Contents/MacOS/kapptemplate.shell /Applications/MacPorts/KDE4/kapptemplate.app/Contents/Resources/kapptemplate_SRCS.icns /Applications/MacPorts/KDE4/kcachegrind.app/Contents/Info.plist /Applications/MacPorts/KDE4/kcachegrind.app/Contents/MacOS/kcachegrind /Applications/MacPorts/KDE4/kcachegrind.app/Contents/MacOS/kcachegrind.shell <snip>
Chris
comment:19 Changed 11 years ago by mp@…
Installing kdesdk4 just to get kcachegrind brings in a *lot* of other deps... So what's the plan?
comment:20 Changed 11 years ago by cjones051073 (Chris Jones)
Personally, I still see no point any longer in a separate port. The KDE project has decided to ship kcachegrind with kdesdk, its not up to MacPorts to second guess that. The moment you install anything KDE4 in MacPorts that brings in a lot of dependencies, so I don't see that as a particular issue to be honest.
Changed 11 years ago by raimue (Rainer Müller)
Attachment: | Portfile.2 added |
---|
kcachegrind @0.7.4 (standalone)
Changed 11 years ago by raimue (Rainer Müller)
Attachment: | hi32-app-kcachegrind.png added |
---|
comment:22 Changed 11 years ago by raimue (Rainer Müller)
I attached kcachegrind @0.7.4 to be used as a standalone port. I added a conflicts line with kdesdk4, of course it should be added vice-versa when this is committed.
This port version is working in some way, however, it still has some problems. At least on my system, all icons seem to be missing.
comment:23 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | NicosPavlov iakoder added |
---|---|
Owner: | ryandesign deleted |
comment:24 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | devernay added; iakoder removed |
---|
comment:25 Changed 5 years ago by raimue (Rainer Müller)
Cc: | raimue removed |
---|
comment:26 follow-up: 27 Changed 5 years ago by tobypeterson
Ok to close? We now have ports for qcachegrind and kcachegrind4.
comment:27 Changed 4 years ago by cooljeanius (Eric Gallager)
Replying to tobypeterson:
Ok to close? We now have ports for qcachegrind and kcachegrind4.
I'd assume so, but let's wait another month or so for the original reporter to confirm.
Portfile for kcachegrind 0.7.1