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

MacPorts noreply at macports.org
Wed Jan 6 15:51:18 PST 2016


#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 ryandesign@…):

 Why is it more important to know what cmake command was used to configure
 than it is to know what command was used to configure any other port not
 using the cmake portgroup? In other words: If this enhancement is to be
 implemented, wouldn't it make more sense to do it in MacPorts base for all
 ports, not in the cmake portgroup only for ports that use cmake?

 The next question would be: why is it more important to know what
 configure command was used than it is to know what build or destroot
 command was used? Should this be done for all phases, not just the
 configure phase?

 You can of course get this information from the main.log file already, but
 I imagine you're requesting this because you often retry port builds
 without cleaning first, which overwrites the original log.

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


More information about the macports-tickets mailing list