Useful to know, thank you.
BTW, given it worked, why wasn’t it merged as a fallback for Leopard and
Tiger? We can make a legacy port from the one you had, if Cocoa is
preferable to X11 (even if not, it does not hurt to have both and let the
user choose).
What Macports has now – setting
As I recall, 2.08 built with his patches, but did not actually work, using the
cocoa interface. This was about 5 years ago, so you’d have to find the ticket.
I kept the last version that DID work in Leopardports.
If you believe that using sdl2 via x11 will allow some port requiring a newish
P. S. I wonder now if the current SDL2 gonna build with X11 backend and Cocoa
off. Given that upstream concentrated efforts on skillfully breaking Cocoa
beyond repair, everything else might be intact.
On Jul 20, 2023 07:15 +0800, Ken Cunningham ,
wrote:
> As far as I know, we don't have any
Of course, we could also make a separate -legacy port using 2.0.9, for example
(last version miniupnp patched was 2.0.8 but we know 2.0.9 builds and likely
gonna work), but it will be disappointing to having wasted many hours on 2.0.22
without a positive outcome LOL
There is also no harm in
That was my point: X11 does not require violating sources much. What does is
essentially one file: SDL_cocoamodes.m. It is used by cocoa video, otherwise it
is not built.
I did not have to throw chunks of code away, aside of cocoa video case (which
still fails to build so far). And miniupnp
As far as I know, we don't have any ports that use SDL2 via X11/Xquartz. All
the ports use the Cocoa interface.
The modifications that were made to SDL2 by miniupnp to run on Tiger and
Leopard were fairly extensive, to an older version of SDL2, but they worked to
allow a number of ports that
libsdl 2.0.22 (our Snow Leopard port) builds on PowerPC with unoffensive
fixes, however I had to disable cocoa video and joystick for that.
They are likely fixable (though no idea whether and how they gonna work),
but at least cocoa video gonna require a massive rewrite – or perhaps
falling back
