Chatterino v2.5.2 (next release) will be the last to support Qt5

[pajlada]

We are nearing the release of Chatterino v2.5.2. We intend that release to be the last release that officially supports building with Qt5. This means we'll stop testing Qt5 builds, and we'll remove some code that we've retained in Chatterino specifically to build on Qt5.
If this is a problem for you or your package, let us know here.

Concerns

• Mac build guide still refers to Qt5
  This was updated & fixed in dev: Default building with Qt6 on all platforms #5716

[ashugg]

I haven't tried to follow the instructions yet, but it looks like BUILDING_ON_MAC.md needs an update. It refers to Qt 5.

[Mm2PL]

Which versions of Qt6 can we compile with? Debian 12 (current LTS, from backports repo) has 6.4.2, latest being 6.8.0. Is this a problem?

[Nerixyz]

Which versions of Qt6 can we compile with? Debian 12 (current LTS, from backports repo) has 6.4.2, latest being 6.8.0. Is this a problem?

If Debian and Ubuntu don't fix their Qt version, then we need 6.5.3 or later (#5517 (comment)). One might be able to use libc++ as an alternative. 6.5 is a decent requirement (all overviews) – 6.6 only adds some overloads for std::chrono afaik.

[pajlada]

6.4.3 is the latest version to easily support macOS 10.15, I'd like to support that for another release

[Nerixyz]

6.4.3 is the latest version to easily support macOS 10.15, I'd like to support that for another release

We don't build for that version. Our builds require at least macOS 14.0 right now and even a year ago, we required 13.0:

$ curl -LsSo c2.dmg https://github.com/Chatterino/chatterino2/releases/download/v2.5.1/Chatterino.dmg
$ 7z x c2.dmg
$ otool -l Chatterino2/chatterino.app/Contents/Frameworks/libssl.1.1.dylib
[...]
Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 1
    minos 13.0
      sdk 13.3
   ntools 1
     tool 3
  version 857.1
[...]
$ otool -l Chatterino2/chatterino.app/Contents/Frameworks/libboost_random-mt.dylib
[...]
Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 1
    minos 14.0
      sdk 14.4
   ntools 1
     tool 3
  version 1053.12
[...]
$ rm -rf Chatterino2
$ curl -LsSo c2.dmg https://github.com/Chatterino/chatterino2/releases/download/v2.4.5/Chatterino.dmg
$ 7z x c2.dmg
$ otool -l Chatterino2/chatterino.app/Contents/Frameworks/libssl.1.1.dylib
[...]
Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 1
    minos 13.0
      sdk 13.3
   ntools 1
     tool 3
  version 857.1
[...]
$ otool -l Chatterino2/chatterino.app/Contents/Frameworks/libboost_random-mt.dylib
[...]
Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 1
    minos 13.0
      sdk 13.0
   ntools 1
     tool 3
  version 820.1
[...]

It's not that it's impossible to support 10.15 now, it's that after more than one year, no one complained that builds for 10.15 were missing.

[Felanbird]

We don't build for that version. Our builds require at least macOS 14.0 right now and even a year ago, we required 13.0:

wat dis

[Nerixyz]

wat dis

Just because the build is named that way doesn't mean it runs on that version (the macOS build is mostly opaque). I could also create a Chatterino-WindowsXP.zip. Even though the libraries say they require newer versions, the loader doesn't seem to check this.

Since there are no usage statistics on macOS, we can't say how many people are using each version (Apple stopped changing its user-agent). The argument I heard was "I know people on 10.15 and there's no urgency".

[Felanbird]

There's 1 guy in the discord who constantly informs us when we break the 10.15 build, so as far as I know it currently still works

cc: #5483

[ashugg]

wat dis

Just because the build is named that way doesn't mean it runs on that version (the macOS build is mostly opaque). I could also create a Chatterino-WindowsXP.zip. Even though the libraries say they require newer versions, the loader doesn't seem to check this.

Since there are no usage statistics on macOS, we can't say how many people are using each version (Apple stopped changing its user-agent). The argument I heard was "I know people on 10.15 and there's no urgency".

Can confirm the 10.15 nightly is working on my 10.15.7 system (where it is very welcome)

[Nerixyz]

Can confirm the 10.15 nightly is working on my 10.15.7 system (where it is very welcome)

Does the other nightly version work too? I don't know which Qt version this builds on because it's not built in CI.

[pajlada]

Does the other nightly version work too?

Last we checked, no

I don't know which Qt version this builds on because it's not built in CI.

6.4.3 is the latest version to easily support macOS 10.15, I'd like to support that for another release

[Nerixyz]

I don't know which Qt version this builds on because it's not built in CI.

6.4.3 is the latest version to easily support macOS 10.15, I'd like to support that for another release

So the Qt version of that build is 6.4.3 and this does not run on macOS 10.15? Why do we want to bump support to that version if these builds don't run on the desired version?

My intention with the previous question was to see if Qt imposes a hard requirement on the macOS version in that they use newer APIs or if it's a soft one (like what we have with Chatterino today) where they only set the deployment target but don't use newer APIs.

[pajlada]

So the Qt version of that build is 6.4.3 and this does not run on macOS 10.15? Why do we want to bump support to that version if these builds don't run on the desired version?

My intention with the previous question was to see if Qt imposes a hard requirement on the macOS version in that they use newer APIs or if it's a soft one (like what we have with Chatterino today) where they only set the deployment target but don't use newer APIs.

I build two mac versions

• Chatterino-10.15.dmg - Built with Qt 6.4.3 - works on 10.15
• Chatterino.dmg - Built with Qt 6.7.0 - does not work on 10.15

When I last experimented with builds, Qt 6.4.3 was the last one I could confirm worked on 10.15