This PR makes native depend on valgrind which I guess is reasonable as
valgrind should be used anyways. If you think it should rather be
opt-out or even opt-in let me know and I'll ifdef around it.
This PR makes native depend on valgrind which I guess is reasonable as
valgrind should be used anyways. If you think it should rather be
opt-out or even opt-in let me know and I'll ifdef around it.
I'd definitely be for opt-in. We don't have any autoconf yet, so users will definately stumble over "cannot find valgrind.h"....
Keep dependencies to a minimum.
Why do you think "valgrind should be used anyways"?
This PR makes native depend on valgrind which I guess is reasonable as
valgrind should be used anyways. If you think it should rather be
opt-out or even opt-in let me know and I'll ifdef around it.
I'd definitely be for opt-in. We don't have any autoconf yet, so
users will definately stumble over "cannot find valgrind.h"....
OK, I'll update the PR accordingly.
Keep dependencies to a minimum.
Why do you think "valgrind should be used anyways"?
Not using valgrind is like disabling compiler warnings, only worse
For me valgrind is about as much a dependency as a compiler is...