[MacPorts] #56107: make kchmviewer build again, respecting "our" build settings

MacPorts noreply at macports.org
Sat Mar 24 08:54:33 UTC 2018

#56107: make kchmviewer build again, respecting "our" build settings
  Reporter:  RJVB        |      Owner:  mojca
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:  fixed       |   Keywords:  haspatch
      Port:  kchmviewer  |

Comment (by RJVB):

 To be precise, `${configure.dir}` and `${build.dir}`, and no, they are not
 created automatically.

 The cmake PG creates the former (and thus normally the latter too) as the
 first thing in its pre-configure block. I missed that yesterday :-/

 So yes, a feature (or pull!) request to ascertain that ${configure.dir}
 exists before starting the port (pre)configure code would be welcome IMHO,
 idem for ${build.dir} and the build code.

 After all, this happens with ${destroot.dir}, no?

 Of course that still leaves us with the current situation for a certain
 time, until the change makes it to a released "base" version and onto all
 user systems (I'd never support a change that forces users to upgrade
 MacPorts itself before being able to apply what could be a minor port

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

More information about the macports-tickets mailing list