[Gammaray-interest] Fwd: building GammaRay on OS X

René J.V. Bertin rjvbertin at gmail.com
Thu May 28 18:27:55 CEST 2015


On Thursday May 28 2015 11:14:54 Volker Krause wrote:

> Right, the app bundle is not part of any official release yet and work in 
> progress (although there hasn't been much progress lately). It doesn't include 
> Qt yet for example, and more importantly there is still issues to address when 
> injecting into a target that bundles Qt itself.

Ok, I'll hold off installing the CLI app then until things get settled, but maybe on your end you could allow the app bundle executable to accept commandline arguments too. That shouldn't be hard, you'll just need to filter out that first -psn_* argument, if that's not done automatically already.


> features if you don't have that. And as I said, when moving to Qt5 (which you 
> want for newer OSX versions anyway), the problem goes away.

Good, I didn't understand it exactly like that, but that means I'll just forget about trying to get it to build with QPainter analysis under Qt4.

Why would I want Qt5 on newer OS X versions anyway? It's more evolved, but apart from that I have yet to see a single advantage as a user (I find it's slower to start up, and the fact you can no longer set global style/font preferences annoys me a lot).

> launcher/injector/injectorfactory.cpp, defaultInjectorFor*()
> 
> Looks like it prefers gdb over lldb if both are present. I'm fine with 
> reversing that order in general on OSX.

Is this change simple enough that I don't have to submit a patch through a heavy-handed mechanism as with Qt itself?

> > them, now that I know I should look for them (in the toplevel CMake file, I
> > hope)?
> 
> Yep, GAMMARAY_PROBE_ONLY_BUILD.

Great, thanks. It's actually so visible that I should have seen it myself when I scanned the file for options :-/
Is the KDE plugin part of a Qt-specific probe (as would make sense), or not?

Cheers,
René


More information about the Gammaray-interest mailing list