|
From: Olly B. <ol...@su...> - 2006-06-01 10:48:55
|
On 2006-05-30, Nicholas Nethercote <nj...@cs...> wrote: > Behdad, I can think of three possible ways of incorporating valgrind.h: > > 1. copying it directly into a C file (clearly silly) > 2. making a local copy in your project and #include'ing that > 3. #include'ing the installed copy from $INSTALL/include > > Number 3 is the intended method. Are you doing number 2? It's not clear to > me because if you do number 3 I don't see why you should have problems with > version mismatches between valgrind.h and the Valgrind program. The manual explicitly recommends method 2, and has for ages. See: http://valgrind.org/docs/manual/manual-core.html which says: You are encouraged to copy the valgrind/*.h headers into your project's include directory, so your program doesn't have a compile-time dependency on Valgrind being installed. The Valgrind headers, unlike the rest of the code, are under a BSD-style license so you may include them without worrying about license incompatibility. If the magic sequence needs to be changed, perhaps valgrind should issue a warning when it sees the old sequence, at least for the next few releases? Cheers, Olly |