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
2
Games / Re: Please test - OpenTTD v12.1
« on: July 12, 2025, 10:18:15 pm »
As I mentioned, all of the OS2 specific code was removed before the release of OpenTTD 14. This has just the vare minimum changes needed to make it compile.

Did music work in older releases?

3
Games / Re: Please test - OpenTTD v12.1
« on: July 12, 2025, 08:59:58 am »
one complication - https://github.com/OpenTTD/OpenTTD/pull/11018

In spite of the above, I got an openttd.exe with 14.1. BUT for me, it just gives an empty black window. Nothing obvious from enabling a debug log. Perhaps an SDL2 issue?

Anyhow, don't expect muc, but https://smedley.id.au/tmp/openttd-14.1-os2-20250712.zip

4
Programming / Re: Qt6 Application Testing
« on: July 06, 2025, 10:34:38 pm »
A process dump might be useful...

5
Networking / Re: SMB server Linux and ArcaOS
« on: July 03, 2025, 09:08:59 am »
Rings a bell about being a bug in ndpsmb.dll, I would try with https://smedley.id.au/tmp/ndpsmb-3.7.3-samba411-20220108.zip

6
Networking / Re: SMB server Linux and ArcaOS
« on: July 02, 2025, 10:44:46 am »
What Samba client are you using?

7
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?

8
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..

9
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.....

10
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....

11
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.

12
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....

13
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

14
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?

15
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 ???

Pages: [1] 2 3 ... 170