|
From: Biswapesh C. <bis...@tc...> - 2003-04-16 06:15:10
|
Hi Is there any reason why the calltree skin (http://kcachegrind.sourceforge.net/) is not included by default with valgrind ? Seems darn useful to me :-) Thanks in advance, and regards, -- Biswa. |
|
From: Nicholas N. <nj...@ca...> - 2003-04-16 08:05:47
|
On 16 Apr 2003, Biswapesh Chattopadhyay wrote: > Is there any reason why the calltree skin > (http://kcachegrind.sourceforge.net/) is not included by default with > valgrind ? Seems darn useful to me :-) We had to draw the line somewhere w.r.t the number of skins to include in the default distribution. It's kind of arbitrary. N |
|
From: Josef W. <Jos...@gm...> - 2003-04-16 08:58:01
|
On Wednesday 16 April 2003 08:21, Biswapesh Chattopadhyay wrote: > Hi > > Is there any reason why the calltree skin > (http://kcachegrind.sourceforge.net/) is not included by default with > valgrind ? Seems darn useful to me :-) There are various reasons for external skins: * No synchronized release cycle necessary. The skin interface version is independent from Valgrind version. Thus, my current calltree skin should work even with V 3.0 if there's no major change in the skin interface. * Check if all requirements for external skins are met with a Valgrind release. If there's no external skin, we can't find problems. * Any addition to V core maps directly to more maintance work for core developers. I'm quite happy with the current situation. Regarding the second item, I still have some issues: * V should install vg_skin.h (and all its dependents) together with valgrind.h. This at least would make it possible to adjust compilation of an external skin to various V skin interface versions. At the moment, I ship my own vg_skin.h (a copy). Thus I have to ship 2 packages, one for interface 1.2 (used till Valgrind 1.9.5) and one for interface 2.0 (current CVS), if I want to support both. * How to integrate external skin documentation into V documentation? Has anyone an idea for this? Perhaps an index update script to be run at skin installation? We could use the valgrind script itself for this: "valgrind --update-docindex". This should search for all <prefix>/share/doc/valgrind/*_main.html and generate a start page. Josef > > Thanks in advance, and regards, |
|
From: Nicholas N. <nj...@ca...> - 2003-04-21 22:30:02
|
On Wed, 16 Apr 2003, Josef Weidendorfer wrote: > * V should install vg_skin.h (and all its dependents) together with > valgrind.h. This at least would make it possible to adjust compilation of an > external skin to various V skin interface versions. At the moment, I ship my > own vg_skin.h (a copy). Thus I have to ship 2 packages, one for interface 1.2 > (used till Valgrind 1.9.5) and one for interface 2.0 (current CVS), if I want > to support both. So you just want vg_skin.h (and its dependents) to be installed in $prefix/include/valgrind/ -- is that enough? Is this only necessary because of the two interface versions? Hopefully the interface won't change much in the future... > * How to integrate external skin documentation into V documentation? Has > anyone an idea for this? Perhaps an index update script to be run at skin > installation? We could use the valgrind script itself for this: "valgrind > --update-docindex". This should search for all > <prefix>/share/doc/valgrind/*_main.html and generate a start page. Hmm, sounds complicated. Not that I can think of anything better, but it feels like there should be a neater solution. Does external skin documentation even need to be integrated...? N |