|
From: Bryan M. <om...@br...> - 2006-06-14 18:16:53
|
I second Nick's comment: Omega has been developed in a checked out valgrind source tree. I have added the files with "svn add" (even though I don't have write access to the repository) because then it's easy to share my changes with "svn diff > ~/omega_versionX.diff" and keep up to date with "svn update". Having the .diff files also allows me to revert back a version if I don't like the way something is going by doing another fresh checkout and then applying the patch and adding the files again. No, its not as nice as full access but its perfectly workable. www.brainmurders.eclipse.co.uk/omega.html (can't blame a man for trying :P) Bryan "Brain Murders" Meredith Nicholas Nethercote wrote: > On Tue, 13 Jun 2006, Josef Weidendorfer wrote: > >>>> 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? > > It might suit Eric to not do it as an external tool, but just do it within > the Valgrind tree. If he did want to do it as an external tool, he could > worry about the setup later. > > Eric, the docs in the manual are about 90% correct and up-to-date, judging > from a quick look. Also, a good place to look is the example tool Lackey > (lackey/*). You can copy its Makefile.am file, for example, and lk_main.c > is not too complex. > > I strongly recommend developing in a checked-out copy of the source tree, > not from a release. > > Nick > > > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |