|
From: Josef W. <Jos...@gm...> - 2006-06-13 18:16:54
|
On Tuesday 13 June 2006 19:49, Tom Hughes wrote: > In message <Pin...@pe...> > Michael E Locasto <me...@co...> wrote: > > > On Tue, 13 Jun 2006, Eric Li wrote: > > > > > Actually, what I meant was instructions for writing a new Valgrind tool. > > > > http://www.valgrind.org/docs/manual/writing-tools.html > > The instructions are generally fine, but 4.2.5 is assuming you are > working with a source checkout and developing a tool that is part of > valgrind itself. > > It's a bit confusing because 4.2.4 suggests that a normal source > release would work. > > There should probably be separate instructions for developing a > separate tool that wouldn't be part of the valgrind build process > and would build against a source release. Regarding the build environment for this, it is probably the best to strip out the relevant parts of callgrind 10.1 for this (see http://kcachegrind.sourceforge.net/callgrind-0.10.1.tar.bz2) This would be the configure.in and the Makefile.am's. It should be easy to make it work with VG 3.2.0 (if it not already is). I suppose that the problem with VG biarch-installation and external tools still exist: the configure process of the external tool can only find out the compile/link options for the main arch config. Would it be a good idea to provide lackey also as external tool? Josef |