Port for for kcachegrind 0.7.1

[rwc@…]

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.

[rwc@…]

Portfile for kcachegrind 0.7.1

[mf2k (Frank Schima)]

Please supply a unified diff of the current portfile so we can easily see the changes you have made.

[rwc@…]

Diff between versions of the portfile

[rwc@…]

Added the diff as requested.

[mp@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

This new port installs "qcachegrind", not "kcachegrind". Would it therefore make sense to rename the port to "qcachegrind"?

[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.

[dstaple@…]

kdelibs3 doesn't build on Lion or Mountain Lion, so right now many users can't install kcachegrind:
#35478
#30314
I'm running OS X 10.8.1 with Xcode 4.4.1.

[dstaple@…]

Cc Me!

[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.

[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.

[cdeil (Christoph Deil)]

Cc Me!

[trolin421]

Cc Me!

[bob@…]

Can this be committed, please?

[bob@…]

Cc Me!

[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.

[alex@…]

Cc Me!

[cjones051073 (Chris Jones)]

Note that KDE4's versions 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

[cjones051073 (Chris Jones)]

Cc Me!

[cooljeanius (Eric Gallager)]

Cc Me!

[mp@…]

Installing kdesdk4 just to get kcachegrind brings in a *lot* of other deps... So what's the plan?

[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.

[raimue (Rainer Müller)]

kcachegrind @0.7.4 (standalone)

[raimue (Rainer Müller)]

Cc Me!

[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.

[tobypeterson]

Ok to close? We now have ports for qcachegrind and kcachegrind4.

[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.