[MacPorts] #67628: Any reason we do not have wxWidgets-3.1 port?
MacPorts
noreply at macports.org
Wed Jun 14 19:25:30 UTC 2023
#67628: Any reason we do not have wxWidgets-3.1 port?
---------------------------+--------------------
Reporter: barracuda156 | Owner: (none)
Type: request | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.8.1
Resolution: | Keywords:
Port: wxWidgets |
---------------------------+--------------------
Comment (by mojca):
According to https://github.com/macports/macports-
ports/commit/15a8f434cad82f465ddb7977d4dcb26d686540fe the version 3.1.2
apparently requires at least 10.8 SDK.
I haven't been paying much attention lately, so I'm no longer sure whether
10.11+ is in fact exact or not, though I would be somewhat surprised if
you would be able to build 3.1 on 10.5 either without non-trivial
patching. It's often not that the framework really needs those new
versions, but they want to add a cool new feature and it's extra work
(with no significant number of users) to keep compatibility for ancient
macOS versions. Very often it's just an unconditionally added function
call from a a newer SDK.
I don't expect super significant differences between 3.1 and 3.2. A
package that works with 3.1 should probably work with very little (or no)
effort with 3.2 as well. But neither of the two will build out-of-the-box
on 10.5.
(I would slightly prefer if we didn't have to introduce another
"development package" for this, but in case we would need to ...)
--
Ticket URL: <https://trac.macports.org/ticket/67628#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list