[MacPorts] #64009: pg cmake-1.1: add option to formally override build.cmd, for Make-type builds

[MacPorts]

#64009: pg cmake-1.1: add option to formally override build.cmd, for Make-type
builds
---------------------------+----------------------
  Reporter:  mascguy       |      Owner:  mascguy
      Type:  enhancement   |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.1
Resolution:                |   Keywords:
      Port:  pg-cmake-1.1  |
---------------------------+----------------------

Comment (by RJVB):

 There is no caching of the original `build.cmd` value; it is simply set to
 `make`. This is done in the setter routine for `cmake.generator` and if
 that routine is also called for the default value of that variable, then,
 indeed, the port's choice of make flavour will get lost.

 Is it possible to guarantee that we'll always restore `build.cmd` to the
 value set by the Portfile. We could cache the build.cmd value, but the
 Portfile *could* for some reason set the cmake generator first to ninja
 and then back to make and set `build.cmd` set to, say, bsdmake, BETWEEN
 those two generator changes? Sounds like it would require a complicated
 bit of code unless we either call that "operator error" or introduce a
 dedicated variable...

 I still stand by my suggestion to use `gmake` instead of plain make if
 available - if of course there are no counterindications nor yet other
 alternative "make" (other than bsdmake, which doesn't appear to be used
 with cmake-based ports for now).

-- 
Ticket URL: <https://trac.macports.org/ticket/64009#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS