| Summary: | SDL 2.0.9 prebuilt binaries doesn't support i386 | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Alibek <a1ba.omarov> |
| Component: | *don't know* | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED WONTFIX | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | Keywords: | target-2.0.12 |
| Version: | 2.0.9 | ||
| Hardware: | x86_64 | ||
| OS: | Mac OS X 10.11 | ||
|
Description
Alibek
2018-12-16 22:43:53 UTC
(Sorry if you get several emails like this, we're marking a bunch of bugs.) We're hoping to ship SDL 2.0.11 on a much shorter timeframe than we have historically done releases, so I'm starting to tag bugs we hope to have closed in this release cycle. Note that this tag means we just intend to scrutinize this bug for the 2.0.11 release: we may fix it, reject it, or even push it back to a later release for now, but this helps give us both a goal and a wishlist for the next release. If this bug has been quiet for a few months and you have new information (such as, "this is definitely still broken" or "this got fixed at some point"), please feel free to retest and/or add more notes to the bug. --ryan. We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc). As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change! Thanks, --ryan. We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc). As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change! Thanks, --ryan. Hmm, so, Xcode 11 doesn't have i386 support. :/ It'll still compile C code (with a warning about x86 being unsupported), but it won't link it, as the 32-bit SDKs are gone. Also: macOS has required a 64-bit CPU since 10.7, has been warning about 32-bit apps since 10.13, and refuses to run them at all on 10.15. Apple hasn't sold a 32-bit CPU since 2006. I'm pretty sure the App Store rejects binaries that have a 32-bit Universal Binary option. I'm sad to say it, but I think it's probably time to mark this as WONTFIX; we had the same problem with the PowerPC transition...we kept SDL PowerPC-compatible for much longer than we were able to build it ourselves, so people that have the means can still compile it on old hardware and old build tools, and I think i386 just fell into that same category. (Sam, if you want to take heroic measures, though, go ahead and reopen this bug!) --ryan. |