|
From: Josef W. <Jos...@gm...> - 2005-06-29 22:37:26
|
On Tuesday 28 June 2005 12:11, Julian Seward wrote:
> - External tools: installing eg Callgrind could be more complex as it
> would have to be linked against libcoregrind.a at
> installation time, even if installing from RPMs.
I don't see real problems here. Finding the correct lib is similar to finding
the headers now.
Linking with valgrind at build time would make RPMs independent, i.e. a
callgrind installation could exist without valgrind at all or with another
valgrind release. Similar, currently I am forced to install into the same
prefix, as valgrind has to find the tool.
But actually, I do not see any big advantages or disadvantages regarding
external tools.
> Alternatively, adjust the core/tool interface so that multiple
> tools can be linked into the core all at once. This sounds
> attractive, and could save disk space.
For external tools you still have to provide the library to link against.
I.e. each external tools would get its own executable. As I am used to install
my wrapper script ("callgrind"), which would become the executable, AFAICS it
would not make a big difference.
Josef
>
> Comments? In particular, are there other bad consequences I haven't
> thought of? Also, [GregP] how would this play for making V work
> for MacOS ?
>
> J
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
|