On 27/10/2015 19:35, Bill Somerville wrote:
On 27/10/2015 18:54, Richard Shaw wrote:
> 1. The change from ${MAKE_EXECUTABLE} to $(MAKE)
How does this work? I note that it does work but I do not
understand who
or where $(MAKE) is being defined?
I think make defines it but I'm not 100% positive. I ran into this on
another project I was setting up external projects for.
Indeed make does set the make variable MAKE for recursive make calls
but that doesn't explain how the outer make invocation works. It seems
to be a chicken and egg issue.
I am worried that on systems where there is an unsuitable native
'make' and GNU make is likely to be present as 'gmake' this might
cause a problem.
I seems that the CMake ExternalProject module treats $(MAKE) specially
and uses it n a similar fashion to the same construct in make i.e. it
allows recursive make calls with command line arguments passed on to the
child. It is an undocumented feature but will remain so it is safe to use.
Richard, I will commit a change based on your suggestions and patch
shortly once I have resolved another issue. Thanks for the input.
73
Bill
G4WJS.
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
