|
From: Tom H. <to...@co...> - 2005-11-15 17:55:04
|
In message <200...@gm...>
Josef Weidendorfer <Jos...@gm...> wrote:
> On Tuesday 15 November 2005 17:58, Tom Hughes wrote:
> > You can possibly do it with automake conditionals, though you may need
> > automake 1.7 for that - valgrind does that now though anyway. See any
> > of the tools for how noinst_PROGRAMS is defined.
>
> If have a target
>
> install-exec-local:
> $(INSTALL_PROGRAM) ./callgrind \
> $(DESTDIR)$(valdir)/@VG_ARCH@-@VG_OS@
>
> This should be done only for VG31.
> Is it enough to put
>
> if BUILD_FOR_VG30
> ...
> endif
>
> around it?
Probably. That's only an installation target though, presumably
somewhere there is a build target as well.
> > It's a horrid hack I use to build callgrind and valgrind all as part
> > of a single RPM so I have to patch callgrind to build against the
> > uninstalled version of valgrind in my build tree and not try and run
> > the installed valgrind to find out what version it is...
>
> Wow.
The reason I do it is because otherwise I have to build valgrind on
all the different systems then go round and install it before I can
build callgrind. I have a script to do builds across all our platforms
but not one to do installs so having to install valgrind before
building callgrind is a pain for me.
> Perhaps callgrinds configure should get an option
> --uninstalled-vg-path=...
> to compile against an uninstalled VG?
Attached is the patch I used for 3.0.1 with callgrind 0.10.0 that
adds a --with-source flag. Not sure if it works without that or not
as I never really tried it. It might well be a bit hacky as well...
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|