Hello Dominik,

I don't use oprofile, so I'm afraid I can't help you with that. For the KDE 
build process, have you taken a look at
 http://techbase.kde.org/Development/CMake/Addons_for_KDE
("Buildtypes" seems relevant to you)?

However I'd like to suggest an alternative: Have you tried valgrind/callgrind 
already?
 valgrind --tool=callgrind kreversi
-> this runs kreversi in callgrind. No recompilation of the application is 
required.
Callgrind emulates a CPU, so it will run a *lot* slower, but the profiling 
information is (for CPU profiling) usually very dependable and reproducible.
Once you close the application, a file callgrind.out.<pid> is written to the 
current directory which can be opened by kcachegrind and gives you a 
callgraph. You can play around with the settings there ("Relative" and 
"Relative to Parent" are usually helpful, both on and off).

Note that callgrind is not suited for profiling stuff that runs on the graphic 
cards (most OpenGL calls).

Greetings
Andi

On Sunday 31 July 2011, Dominik Raddatz wrote:
> Hi Everyone,
> 
> on my netbook kreversi plays too slow. To see where it spends too much time
> I want to profile it with gprof.
> Oprofile does work, but it doesn't tell me whether functions are called too
> often or are running too slow.
> 
> Therefore I need to specify -pg to the compiler.
> 
> Where do I have to do that using the "default cmakekde"-script?
> There is a local CMakeCache.txt, but it doesn't seem to be used.
> 
> Where can I see which compiler options were actually being used for which
> file?
> 
> How do I invoke targets other than default (like debug or profile) as
> mentioned in the documentation?
> 
> Is there documentation describing in more detail how the KDE build process
> works and which files are accessed in which order?
> 
> Thanks
> Dominik

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<