Ben, I think the problem is that some versions of purify are run by
putting purify in front of the final link line. Like this:
purify gcc -o foo foo.o
Yes. This is how it is done on Linux.
The instrumentation takes place a link time.
Running this:
purify foo
I believe this is how
On 10/14/2010 7:11 PM, Ben Boeckel wrote:
william.croc...@analog.com wrote:
Something like this is probably better (crudely adapted from something
like this for test executables from here[1]):
macro (purify exename)
add_custom_target(purify-${exename})
add_custom_command(
william.croc...@analog.com wrote:
> Hello:
>
> I needed to build a purified version of my test program.
> A search of the mailing list archives produced a number of
> options, but they all had drawbacks.
>
> I came upon the solution below which seems to work well.
> I introduce a new language "P
Hello:
I needed to build a purified version of my test program.
A search of the mailing list archives produced a number of
options, but they all had drawbacks.
I came upon the solution below which seems to work well.
I introduce a new language "PURIFY" for the purposes
of linking the purified ex
