Re: [Valgrind-users] Why not calltree

[Nicholas N. <nj...@ca...>]

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