Opened 5 years ago
Closed 4 years ago
#60061 closed update (fixed)
wesnoth: update to 1.14.13
Reported by: | l2dy (Zero King) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | wesnoth |
Description
wesnoth seems to have been updated (port version: 1.12.6, new version: 1.14.11)
Change History (5)
comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Status: | assigned → accepted |
---|
comment:2 Changed 4 years ago by cooljeanius (Eric Gallager)
Cc: | cooljeanius added |
---|
comment:3 Changed 4 years ago by cooljeanius (Eric Gallager)
note that updating would also fix the build failures I'm currently seeing with 1.12.6
comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | wesnoth: update to 1.14.11 → wesnoth: update to 1.14.13 |
---|
I tried building 1.14.13 using my in-progress Portfile, and though the build succeeds, the app does not do anything when it is launched.
Wesnoth supports multiple build systems. The Portfile has been using the cmake build system, but the official Mac builds use the Xcode project. I should probably try to use that, but it is designed to use separately built copies of all the libraries they use and to embed them inside the application bundle, which of course we wouldn't want to do for MacPorts, so it may take some work to dismantle and re-mantle what they're doing.
comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
I tried to update wesnoth to 1.14.something back when that was first released. It took hours, because wesnoth takes so long to build and it took several iterations because I had to fix several things. In the end it built but did not run properly and I put it aside. Maybe the situation has improved by now; I should recheck.