1
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?
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
I think it is an old problem.Phew! Can you describe how to reproduce?
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.
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,
Based on Chromium version: 94.0.4606.126
Patched with security patches up to Chromium version: 104.0.5112.81
Based on Chromium version: 87.0.4280.144
Patched with security patches up to Chromium version: 135.0.7049.95
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 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.
Thanks Paul - every QT6 app I've tried works just fine with this build! Haven't tried any examples yet though...
Assertion failed: _UM_CRUMB_STATUS (crumb) == _UMS_FREE, file ./libc-0.1.13/src/emx/src/lib/malloc/ifree.c, line 30
Are you also updating Qt for C++20?I wsan't planning on it - just remove -Werror from the makefiles..Code: [Select]:/work/dooble-dry/Source/dooble.cc
In file included from L:/QT6-6.2.X/include/QtCore/qfuture.h:45,
from L:/QT6-6.2.X/include/QtCore/QtCore:92,
from L:/QT6-6.2.X/include/QtConcurrent/QtConcurrentDepends:3,
from L:/QT6-6.2.X/include/QtConcurrent/QtConcurrent:3,
from K:/work/dooble-dry/Source/dooble.cc:41:
L:/QT6-6.2.X/include/QtCore/qfutureinterface.h:451:37: error: template-id not al
lowed for constructor in C++20 [-Werror=template-id-cdtor]
451 | explicit QFutureInterface<void>(State initialState = NoState)
| ^~~~~
L:/QT6-6.2.X/include/QtCore/qfutureinterface.h:451:37: note: remove the '< >'
cc1plus.exe: all warnings being treated as errors
make: *** [Makefile:12688: temp/obj/dooble.obj] Error 1
OK I think I've found the root cause of this...