[MacPorts] #50246: CMake PortGroup : generate a file in ${workpath} containing the complete cmake invocation

[MacPorts]

#50246: CMake PortGroup : generate a file in ${workpath} containing the complete
cmake invocation
--------------------------+--------------------------------
  Reporter:  rjvbertin@…  |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------------------

Comment (by rjvbertin@…):

 Sounds like the sort of thing I do all the time too. Do a search for port-
 redo-install-phase here on trac, it should lead you to the current version
 in my repo.
 It handles removing specific entries from the state file, but also updates
 its checksum so you stand less risk of losing the entire build dir.
 It is rarely required to remove the entire build.dir in my experience.
 Most of the time a cmake rerun will suffice; sometimes you'd better remove
 CMakeCache.txt first. The port-redo-install-phase `-configure` vs.
 `-configure-all` options implement those 2 approaches.

 There's also `port-active-variants` which helps not having to re-determine
 the current variants every time ;)

 {{{
 > port-redo-install-phase -configure|-configure-all [-build] [-destroot]
 foo
 > port -nvok {configure,build,destroot} `port-active-variants -echo foo`
 configure.optflags="..."
 }}}

 -n : don't touch anything else; -o : reduncant after port-redo* but let's
 take no risks; -k : idem, don't risk forgetting this one when editing the
 last command to do an install / upgrade --force ;)

 And sometimes I do a `port-edit-state foo` if I want to add or remove a
 variant.

 The only thing that still surprises me in all that is how long it took
 before I went ahead and wrote those utilities...

-- 
Ticket URL: <https://trac.macports.org/ticket/50246#comment:9>
MacPorts <https://www.macports.org/>
Ports system for OS X