citrun

watch C/C++ source code execute
Log | Files | Refs | LICENSE

commit 485af6253a1b212a496843cb41726c29887f3ce1
parent a60eeb9d3839add537240c7acc3798f352e8f3ed
Author: kyle <kyle@0x30.net>
Date:   Sat, 12 Nov 2016 13:48:37 -0700

Jamrules: expand on comment about debug/release builds

Diffstat:
MJamrules | 8++++++--
1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/Jamrules b/Jamrules @@ -1,6 +1,10 @@ # -# Knowing the absolute path to citrun resources is necessary for -# instrumentation. If PREFIX is set, assume we're building a package. +# Knowing the absolute path to citrun resources is necessary because: +# - instrumented programs must be linked to the runtime library +# - the PATH compiler interception mechanism needs to remove itself from PATH +# +# If PREFIX is set we're building a package, so trust that will be the final +# (after installation) location. # if $(PREFIX) { echo ...build citrun-RELEASE on $(OS)... ;