Ticket #45701

Crosser-2.5

Open Date: 2022-09-24 00:57 Last Update: 2022-10-29 18:39

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
3

Details

Ticket for tracking progress toward switching to crosser-2.5.

It seems we need this in a quick schedule. Meson based builds of Qt6 programs are currently not working with crosser-2.4 ( #45511 got postponed, and Qt6-client build fails ). Things seem to work with the crosser-2.5 development version.

---

Blocker:

- _WIN32_WINNT redefinition: #45860

---

Preferably fixed first:

- winbuild.sh not clearing old build directory (affects usability of docker build): #45865
- meson installer_cross builds not creating langstat files (affects especially docker builds where langstat files are never created outside meson build): #45858

---

Related:

- I'm bringing in containerized build system for freeciv crosser-based builds, to be first introduced with crosser-2.5 support. Docker usage in general first talked about in #44924

Ticket History (3/14 Histories)

2022-09-24 00:57 Updated by: cazfi
  • New Ticket "Crosser-2.5" created
2022-10-05 11:04 Updated by: cazfi
Comment

Reply To cazfi

It seems we need this in a quick schedule.

One thing to concentrate immediately when I get releasing 3.0.4 out of the way.

2022-10-14 19:25 Updated by: cazfi
  • Details Updated
2022-10-14 19:25 Updated by: cazfi
  • Details Updated
2022-10-15 04:07 Updated by: cazfi
Comment

Reply To cazfi

It seems we need this in a quick schedule. Meson based builds of Qt6 programs are currently not working with crosser-2.4 ( #45511 got postponed, and Qt6-client build fails ). Things seem to work with the crosser-2.5 development version.

That's the case in Debian Testing / Bookworm that I normally use. However, with a docker container built around stable Ubuntu Jammy LTS (22.04), also crosser-2.4 works. That doesn't much reduce the urgency, though. Nightly builds are currently failing as they run on Bookworm too - they should be switched to use stable containers, but that's not likely to happen in a quicker schedule than releasing crosser-2.5.

2022-10-15 20:34 Updated by: cazfi
  • Details Updated
2022-10-21 05:14 Updated by: cazfi
Comment

Reply To cazfi

That doesn't much reduce the urgency, though. Nightly builds are currently failing as they run on Bookworm too - they should be switched to use stable containers, but that's not likely to happen in a quicker schedule than releasing crosser-2.5.

Fun stuff. That machine that is supposed soon to do nightly builds with crosser-2.5 & all the related stuff encounters various "internal compiler errors" and system header confusions when testing current crosser-2.5 & co there. In supposedly very similar setup (bookworm & same tool versions in use) everything is working.

2022-10-21 05:20 Updated by: cazfi
Comment

Reply To cazfi

Fun stuff. That machine that is supposed soon to do nightly builds with crosser-2.5 & all the related stuff encounters various "internal compiler errors" and system header confusions when testing current crosser-2.5 & co there. In supposedly very similar setup (bookworm & same tool versions in use) everything is working.

And on that very setup all crosser-2.4 builds last night seem to have passed: https://files.freeciv.org/packages/windows/testing/cazfi/installer_cross/nightly/
So it's not like the installation there would be totally broken.

2022-10-25 05:26 Updated by: cazfi
Comment

Dockerfile & related scripts to build crosser-2.5 based freeciv Windows Installers now at https://files.freeciv.org/tools/docker-containers/building/crosser-build-2.5.tar.xz

Just note that current freeciv code expects crosser-2.4, not crosser-2.5 (this very ticket is about changing that), and also fix from #45860 is needed in freeciv.

2022-10-25 08:25 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Resolution Update from None to Accepted
2022-10-29 18:39 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

Please login to add comment to this ticket » Login