|
From: Konstantin S. <kon...@gm...> - 2009-12-29 10:55:06
|
Hi Valgrind devs, First question: Valgrind installation contains include files, which makes me think that it is possible to build valgrind tools w/o having the valgrind sources. However, with the current version of valgrind, it does dot work: include/valgrind/pub_tool_basics.h includes "config.h", which is not a part of valgrind installation. Can that be fixed? Second question: Building valgrind tools requires passing quite unusual and system-dependent flags to gcc and ld. When building valgrind tools in the usual way, these flags are generated by automake/configure. Is there a simple way to guess these flags from the valgrind installation tree? Third question: Few of the valgrind public headers are not C++-able. Can that be fixed? Here is what I need to build my valgrind tool in C++. cxx.patch: the patch valgrind_cxx_test.cc: the test Linux: g++ -Itrunk/inst/include/valgrind -Itrunk -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -m32 valgrind_cxx_test.cc -c g++ -Itrunk/inst/include/valgrind -Itrunk -DVGA_amd64=1 -DVGO_linux=1 -DVGP_amd64_linux=1 -m64 valgrind_cxx_test.cc -c Mac g++ -Itrunk/inst/include/valgrind -Itrunk -DVGA_x86=1 -DVGO_darwin=1 -DVGP_x86_darwin=1 -m32 valgrind_cxx_test.cc -c If you build the test w/o the patch, you will see why the patch is required. Thanks and happy New Year! --kcc |