Re: [Valgrind-developers] Re: Release plan for Valgrind 3.0

[Nicholas N. <nj...@cs...>]

On Wed, 20 Jul 2005, Josef Weidendorfer wrote:

> 1) For which OS/ARCH should the external tool be compiled?
> I think I should use the OS/ARCH defined in the installed valgrind.pc file. Is
> this the correct way?

Sounds reasonable to me.


> Are installed header files specific for an installation or not?

I don't understand the question, sorry...


> 2) For the tool compilation check in configure, I use the headers from
> none/nl_main.c, i.e.
>
> #include "pub_tool_basics.h"
> #include "pub_tool_libcassert.h"
> #include "pub_tool_tooliface.h"

Sounds ok.


> I think that vex should install its public header files in the same directory
> as valgrind.

Yes, good point.


> Furthermore, I think that public header files of VG should not
> include any config.h.

Hmm, it looks like config.h was previously included only in core.h.  I'll 
investigate.


> PS: For cachegrind/cg-x86, I have an addition:

Thanks, I'll add it.

N