[MacPorts] #49925: KF5 : PortGroup and initial ports (frameworks)

MacPorts noreply at macports.org
Mon Aug 15 00:39:25 PDT 2016


#49925: KF5 : PortGroup and initial ports (frameworks)
--------------------------+------------------
  Reporter:  rjvbertin@…  |      Owner:  mk@…
      Type:  submission   |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+------------------

Comment (by rjvbertin@…):

 I've been following this from a distance while on holidays.

 Sadly I've never really looked at how the MSWin QStandardPaths (QSP) class
 is implemented and what kind of paths it returns compared to what it
 "should" return for MSYS2. I've never really used MSYS2 but from what I
 remember it aims to do similar things as Cygwin but without or with much
 less overhead (and without a dedicated runtime DLL) (?).

 That said, yes, I do think your best bet would be to patch Qt like we did.
 I must admit that my first reaction was that our patches will be so
 different that there's little to "collaborate" on. On second thought there
 might be a reason. It is my intention to try and get our patch into Qt.
 The chances to that should increase if other platforms can also benefit
 from a modified/extended QSP class that 1) allows applications to be build
 such that they use appropriate paths instead of the "native" ones while 2)
 the default way of building code still yields the default, "native" paths.

 I should add that someone submitted a patch for Qt review that allows
 something like this for the writable paths, using the `qt.conf` file. If
 that sounds interesting but not familiar, please don't hesitate to remind
 me in a couple of days so I can dig up the link.

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


More information about the macports-tickets mailing list