|
From: Josef W. <Jos...@gm...> - 2005-11-21 16:39:49
|
On Monday 21 November 2005 16:59, Josef Weidendorfer wrote: > On Monday 21 November 2005 11:37, Dirk Mueller wrote: > > callgrind doesn't install properly because of ultra ugly install hacks that > > forget to create the target dir. attached patch removes that code. > > Ah, thanks. That is a lot better. > > > I'm still not too happy about callgrind, now it installs a callgrind.html > > into /usr/share/doc/valgrind - either it should be part of valgrind, then it > > is allowed to install there, or it should install its documentation > > into /usr/share/doc/callgrind. the current mixture doesn't make distributors > > happy. > > Hmm... Callgrind is an external plugin for Valgrind, so the binary (previously the > shared lib) of course has to be installed into Valgrinds path. Why should this be > different for the documentation (e.g. the include file installs into the same path). > The documentation was always installed into this path with Callgrind 0.9.x. > > So what is the exact problem? To separate VG and external tools: What about a TOOL_PATH variable, similar to PATH, which is searched for a matching tool by the VG launcher? Callgrind's configure would distinguish between --prefix and --vgprefix, i.e. you can do ./configure --vgprefix=/usr --prefix=$HOME How does this sound? Josef |