Re:How to create a Qt 5 ARM/Intel universal binary for Mac
by fiddlerwoaroof on Tuesday August 29, 2023 @12:14AM
(#37303507)
This is it an either/or: you can find the problem libraries and submit the work back upstream so you don’t have to maintain it. Then, for the upstream that don’t cooperate, fork temporarily until you find an alternative.
[ Parent
| on HN ]
Re:How to create a Qt 5 ARM/Intel universal binary for Mac
by nomel on Tuesday August 29, 2023 @01:10AM
(#37303755)
To their point, all of this is not trivial. You could just compile as x86 and be done with in in 5 minutes, assuming the performance hit is acceptable.
Re:How to create a Qt 5 ARM/Intel universal binary for Mac
by fiddlerwoaroof on Tuesday August 29, 2023 @06:24PM
(#37314926)
It’s not trivial, but it’s also not a long-term maintenance cost if upstream accepts the patch.
Re:How to create a Qt 5 ARM/Intel universal binary for Mac
by nomel on Wednesday August 30, 2023 @04:25PM
(#37328495)
> long-term maintenance cost if upstream accepts the patch
When they said "maintain", I read it as short term, doing this if and when for all libraries down the dependency chain. Or, compile as x86, and wait until external resources push for the support.