Re: [MacPorts] #59085: mingw-w64 fails if called via another port that’s using the +universal variant

[MacPorts]

#59085: mingw-w64 fails if called via another port that’s using the +universal
variant
------------------------+----------------------
  Reporter:  Gcenx      |      Owner:  mojca
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:
      Port:  mingw-w64  |
------------------------+----------------------

Comment (by Gcenx):

 Wine versions prior to Wine-4.15 didn’t make use of {{{mingw-w64}}} so it
 would have been a none issue. Now wine is using {{{mingw-w64}}} to build
 multiple dll/exe file as native Windows binaries instead of fake dll files
 that linked to .so files that mapped to the native dylibs on macOS.

 I’m aware {{{mingw-w64}}} is the meta package I’m calling it directly due
 to needing all of it for compiling wine as universal.

 wine uses i686 components of mingw for 32Bit builds.
 wine64 uses x86_64 components of mingw for 64Bit builds.

 I don’t believe i686 would need to be compiled as universal since it’s a
 32Bit compiler and x86_64 is 64Bit, I’m mostly confused why macports seems
 to think it can’t install components of mingw-w64 due to my usage of
 +universal that’s required to build the full wine/wine64 port.

 As i also mentioned if I can add something into the {{{wine-devel}}}
 Portfile to not pass the +universal flag and works I take that, as if I
 installed {{{mingw-w64}}} before hand my Portfile works just fine

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