debug: make valgrind optional, disabled by default, not available for… #924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… armv6
Couple of issues now that valgrind is being built by default whenever
DEBUG=yes
(see #884):Building and running valgrind on armv6 probably wouldn't make any sense even if it was supported.
We definitely don't want to build with valgrind by default, it should be enabled only when required.
Building valgrind for RPi2 adds about 30MB, which isn't too bad, but should still be included only when required...
Adding
VALGRIND
option solves both #1 and #2.