Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Paul Smedley

Pages: [1] 2 3 ... 170
1
Games / Re: Please test - OpenTTD v12.1
« on: June 18, 2025, 11:13:36 am »
Probably...... based on older ports - does SDL1 or SDL2 work better?

2
Programming / Re: Qt6 Development
« on: June 09, 2025, 10:21:21 pm »
Qt5 and Qt6 can coeexist fine. My comment on DLL hell was more for mixing versions of Qt6..

3
Programming / Re: Qt6 Development
« on: June 09, 2025, 11:17:55 am »
In that case, do you think it will make sense to put Qt 6.2  on the Netlabs RPM?

It depends what the purpose/intent is. For getting an updated (but unstable) browser - then yes. If it's for compatibility with ported apps - I'm less sure. The DLL hell with 8.3 file names is real.....

4
Programming / Re: Qt6 Development
« on: June 07, 2025, 11:03:27 pm »
Hello Paul

First, sorry for this shameless request from my side, like if it easy.This is just a suggestion and I want to ask your opinion.

Since Qt6 has some LTS releases , how do you see the idea of trying to port "Qt 6.5.9" which is supported to 2026-03-30 and try to stabilize it (as much as possible this release), until something happens to version 6.8 which seem being hard to make it work. Or do you think it will be better to focus on 6.8 which is also a LTS release supported to 2019?

I want to see if we can finally go mainstream with Qt6 and put it on the RPM repository.

Regards

Qt 6.2 is/was also LTS..... that was the whole point of focussing on it...

Also, whilst 6.5.9 might be the most recent COMMERCIAL release, the opensource is still 6.5.6 (https://download.qt.io/official_releases/qt/6.5). I'm not entirely sure what the benefit would be of having the core Qt libs at 6.5, and trying to blend in a 6.2 webengine....

5
Internet / Re: Dooble releases-Qt6
« on: June 07, 2025, 01:48:02 am »
I'm using VIRTUALADDRESSLIMIT=2560
I marked every DLL to load code into high memory -- most were already so marked.

I think for some new machines, dooble-QT6 will be out of reach...

Yeah quite possibly. Even with the full 4gb, it's a challenge - with less than this visible to OS/2 - we're pretty much screwed.

6
Internet / Re: Dooble releases-Qt6
« on: June 06, 2025, 11:40:18 pm »
There was some upstream restructuring of DLL's in 6.8.x....

7
Programming / Re: GCC - updates
« on: May 25, 2025, 11:52:36 am »
GCC 14.3.0 was released a few days ago - OS/2 binaries at https://smedley.id.au/tmp/gcc-14.3.0-os2-20250525.zip

8
Programming / Re: Qt6 Application Testing
« on: May 12, 2025, 10:56:59 pm »
I think it is an old problem.
Phew! Can you describe how to reproduce?

9
Programming / Re: Qt6 Application Testing
« on: May 12, 2025, 10:04:10 am »
There's something seriously wrong with code pages and perhaps icu. Using dooble-qt6, simply opening it, displaying the release notes and closing it results in this,
Code: [Select]
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KS_C_5601-1987 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KSC_5601 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias 5601 maps to EUC-KR already, but someone is trying to make it map to cp1363
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias windows-949 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias KS_C_5601-1989 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias csKSC56011987 maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias korean maps to cp1363 already, but someone is trying to make it map to EUC-KR
[107:19:0511/115608.818000:ERROR:text_encoding_registry.cc(139)] alias iso-ir-149 maps to cp1363 already, but someone is trying to make it map to EUC-KR

As far as I can see, the release notes are straight ASCII.
I've also seen errors related to ICU.
For Mozilla, had to re-add cp850 at one point when they cleaned up the codepage section.
Doing the same with dooble-qt5 results in no messages to stdout/stderr
Another observation is here, going to github often sees dooble-qt6 close pretty quick. Redirecting stdout/stderr (dooble 2>&1 | tee dooble.log) sees dooble display the pages. Timing issue I assume.

Is this a new problem with the latest build or ???

10
Programming / Re: Qt6 Application Testing
« on: May 08, 2025, 10:50:14 pm »
What I'm wondering is whether there is an equivalent Qt5 Webengine to 6.2.6 and how to merge it.
Trying to clone Qt5 from the official sources, init repository fails,

In short....
Qt 6.2.6 - https://github.com/psmedley/qt6-webengine-os2/blob/main/CHROMIUM_VERSION
Code: [Select]
Based on Chromium version:                                      94.0.4606.126
Patched with security patches up to Chromium version:           104.0.5112.81

Qt 5.15.19 (latest tag at https://github.com/qt/qtwebengine/blob/5.15.19/CHROMIUM_VERSION
Code: [Select]
Based on Chromium version:                                      87.0.4280.144
Patched with security patches up to Chromium version:           135.0.7049.95

So the latest 5.15 version is older than what we have. We could however, try and cherry-pick the security fixes.

11
Programming / Re: Qt6 Application Testing
« on: May 08, 2025, 10:45:17 pm »
Yes, this one seems to work as well as the previous working version - with the same limitations (mostly occasional random system hangs). Any thought on trying to build the 6.2.12 version of webengine?

I'm currently stuck on 6.2.8 - which is the same webengine that came as part of Qt 6.4.x. The code compiles, but pretty much any site with javascript crashes. Any newer than 6.2.8 and we hit the webengine that came with Qt 6.5 - and we encounter https://github.com/bitwiseworks/node-os2/issues/1 where Dmik and I both got stuck at basically the same crash.

So in short, No.

12
Programming / Re: Qt6 Application Testing
« on: May 08, 2025, 01:14:33 am »
Bugger....I guess something in gcc 15 is triggering this. Will investigate over the next few days. On the plus side, I didn't get any out of memory failures building with 2 jobs.

FWIW sample exceptq.txt attached.

Lookingback through my emails, this seems to be an alignment issue - the joys of our aout object format......

Thankfully, it seems I fixed this in the Qt 6.4.x code with https://github.com/psmedley/qt6-webengine-os2/commit/d2b464fdc27bf23b1891ba63c1f5c00cd5b7a88c I knew the trp looked familiar....

Yep, with https://smedley.id.au/tmp/qt6-6.2.12-qtwebengine-6.2.6-os2-20250508.zip at least os2world.com loads ok :)

13
Programming / Re: Qt6 Application Testing
« on: May 07, 2025, 12:22:41 pm »
I do plan on rebuilding the webengine with GCC 15, but this may take a few days - depending how many times the build machine runs out of memory.

The build went surprisingly smoothly. (link removed) contains a rebuilt webengine from Qt 6.2.6.

Unfortunately, on my machine at least, I'm getting a 'Limit access fault' with simplebrowser.exe and dooble just closes.

<sigh> life wasn't meant to be easy. Will investigate tomorrow, but curious if it's something local (I've installed a bunch of yum updates recently)

14
Programming / Re: Qt6 Application Testing
« on: May 07, 2025, 10:12:14 am »
Thanks Paul - every QT6 app I've tried works just fine with this build! Haven't tried any examples yet though...

Thanks David, there weren't significant changes between 6.2.11 and 6.2.12, so I wouldn't expect behaviour to be too different.

15
Programming / Re: Qt6 Application Testing
« on: May 05, 2025, 10:58:47 am »
Webengine is unchanged from the January release, but the remaining Qt6 components are updated to Qt 6.2.12 LTS. https://smedley.id.au/tmp/qt6-6.2.12-qtwebengine-6.2.6-os2-20250505.zip This is also built with GCC 15.1.0

I do plan on rebuilding the webengine with GCC 15, but this may take a few days - depending how many times the build machine runs out of memory.

Pages: [1] 2 3 ... 170