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 - Dave Yeo

Pages: [1] 2 3 ... 322
1
Programming / Re: Qt6 Development
« on: Today at 07:52:49 am »
Mount U: under Ubuntu and do it? Probably have to do it as root, or do a chown first.
Maximize memory under OS/2 and try again. Maximum VIRTUALADDRESSLIMIT and don't load the WPS and minimize what else is loaded, also a small JFS cache., no HPFS or FAT32. I started running OS/2 on a 386 with 4MB's of ram. I had it tuned to run pretty good, didn't run the WPS for a long time until I upgraded to 8 MB's of ram.

I managed to get the checkout to complete using ACPI /MAXCPU=1

Good, something to remember.

2
Programming / Re: Qt6 Development
« on: Today at 06:26:39 am »
Thanks Dave, that will give some clues.... Are you able to raise an issue in the qt6-base-os2 repo?

Ok, I think the issue is that the files in https://github.com/bitwiseworks/qtbase-os2/tree/master/mkspecs/features/os2 are missing in Qt6

I tried adding features/os2, no change. Then I tried using the whole features/ from Qt5, still no change.

3
Programming / Re: Qt6 Development
« on: Today at 06:25:18 am »
Mount U: under Ubuntu and do it? Probably have to do it as root, or do a chown first.
Maximize memory under OS/2 and try again. Maximum VIRTUALADDRESSLIMIT and don't load the WPS and minimize what else is loaded, also a small JFS cache., no HPFS or FAT32. I started running OS/2 on a 386 with 4MB's of ram. I had it tuned to run pretty good, didn't run the WPS for a long time until I upgraded to 8 MB's of ram.

4
Applications / Re: RPM Repository: IBM OS/2 Toolkit.
« on: Today at 03:43:59 am »
I'd assume the same code. Wonder if one has debug data?

5
Applications / Re: RPM Repository: IBM OS/2 Toolkit.
« on: May 23, 2024, 11:54:09 pm »
Lxlite?
With the toolkit som.dll.
Code: [Select]
6-30-99  7:17p       133,593    124 a---  som.dll

[H:\tmp]lxlite som.dll
┌[ lxLite ]───────────────────────────────────┬[ Version 1.3.9 ]┐
├ Copyright 1996,97 by FRIENDS software       ├    All rights   ┤
├ Copyright 2001,03 by Max Alekseyev          ├     reserved    ┤
├ Copyright 2008-10 by OS/4 team              ├                 ┤
├ Copyright 2011    by Steven H. Levine       ├                 ┤
├ Copyright 2017-23 by bww bitwise works GmbH └─────────────────┘
├ The file som.dll contains 1932 bytes in non-resident names table
├                     som.dll initial: 133593 final: 93250 gain: 30.2%
├┤Total gain: 40343 bytes

 6-30-99  7:17p        93,250    124 a---  som.dll

Time stamp might be off due to zip or such screwing up the timezone
Edit: ignore what I said about the timestamp, possible it was rebuilt for the release with /exepack:2 which does similar to lxlite

6
Have you looked at the resulting config.log? Have you double checked that your environment is correctly setup? Seems some of that stuff should be quoted and set exeext doesn't work due to the small case.
Code: [Select]
[W:\]set exeext=.exe

[W:\]set exeext=

[W:\]

Perhaps convert to sh as config.site,
Code: [Select]
export 'LDFLAGS=-Zomf -Zhigh-mem -Zmap -Zbin-files -Zargs-wild -Zargs-resp'
etc.
config.site goes in %PREFIX%\share, usually \usr\local\share\config.site

7
Programming / Re: Qt6 Development
« on: May 21, 2024, 12:26:05 am »
I have seen this before,  but not consistently - does qmake have any debug switches  that may highlight the differences? looks like '-d' might do it...

Ok, the dooble build that worked was due to having a stray .qmake.stash in the tree. It contains the QMAKE_CXX stuff and was created by Qt5. Sure enough running qmake-qt5 first, then qmake[-qt6] works, so a work around.
Further investigation shows where things go wrong but trying to trace the various variables has been a failure.

Qt6
Code: [Select]
DEBUG 1: L:/QT6-6.2.X/mkspecs/features/toolchain.prf:64: finished 'else' branch
DEBUG 1: L:/QT6-6.2.X/mkspecs/features/toolchain.prf:66: entering loop for v over
DEBUG 1: L:/QT6-6.2.X/mkspecs/features/toolchain.prf:66: done looping
DEBUG 1: L:/QT6-6.2.X/mkspecs/features/toolchain.prf:76: evaluating test function "cache"
DEBUG 1: L:/QT6-6.2.X/mkspecs/features/toolchain.prf:76: calling built-in cache(QMAKE_CXX.COMPILER_MACROS, "set stash")

Qt5
Code: [Select]
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:64: finished 'else' branch
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:66: entering loop for v over "# 1 \"W:/usr/lib/qt5/mkspecs/features/data/macros.cpp\"" "# 1 \"<built-in>\"" "# 1 \"<command-line>\"" "# 1 \"W:/usr/lib/qt5/mkspecs/features/data/macros.cpp\"" "QT_COMPILER_STDCXX = 201402L" "# 26 \"W:/usr/lib/qt5/mkspecs/features/data/macros.cpp\"" "QMAKE_GCC_MAJOR_VERSION = 9" "QMAKE_GCC_MINOR_VERSION = 2" "QMAKE_GCC_PATCH_VERSION = 0"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:66: loop iteration "# 1 \"W:/usr/lib/qt5/mkspecs/features/data/macros.cpp\""
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:66: entering block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: NOT
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: evaluating test function "contains"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: calling built-in contains(v, "[A-Z_]+ = .*")
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: test function returned false
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: AND
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: flow control statement 'next', aborting block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: loop iteration "# 1 \"<built-in>\""
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: entering block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: NOT
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: evaluating test function "contains"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: calling built-in contains(v, "[A-Z_]+ = .*")
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: test function returned false
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: AND
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: flow control statement 'next', aborting block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: loop iteration "# 1 \"<command-line>\""
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: entering block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: NOT
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: evaluating test function "contains"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: calling built-in contains(v, "[A-Z_]+ = .*")
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: test function returned false
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: AND
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: flow control statement 'next', aborting block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: loop iteration "# 1 \"W:/usr/lib/qt5/mkspecs/features/data/macros.cpp\""
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: entering block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: NOT
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: evaluating test function "contains"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: calling built-in contains(v, "[A-Z_]+ = .*")
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: test function returned false
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: AND
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: flow control statement 'next', aborting block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: loop iteration "QT_COMPILER_STDCXX = 201402L"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: entering block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: NOT
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: evaluating test function "contains"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: calling built-in contains(v, "[A-Z_]+ = .*")
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: test function returned true
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: AND
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:67: skipped flow control statement 'next'
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:69: evaluating test function "eval"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:69: calling built-in eval("QT_COMPILER_STDCXX = 201402L")
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf: entering block
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:69: QT_COMPILER_STDCXX := 201402L
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:69: leaving block, okey=true
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:69: test function returned true
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:70: v := QT_COMPILER_STDCXX
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:71: evaluating test function "isEmpty"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:71: calling built-in isEmpty(QT_COMPILER_STDCXX)
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:71: test function returned false
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:71: AND
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:71: skipped test function "error"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:73: evaluating test function "cache"
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:73: calling built-in cache(QMAKE_CXX.QT_COMPILER_STDCXX, "set stash", QT_COMPILER_STDCXX)
Info: creating stash file L:\work\dooble-dry\obj\.qmake.stash
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:73: test function returned true
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:74: QMAKE_CXX.COMPILER_MACROS := QT_COMPILER_STDCXX
DEBUG 1: /@unixroot/usr/lib/qt5/mkspecs/features/toolchain.prf:74: leaving block, okey=true
...

8
Programming / Re: Qt6 Development
« on: May 19, 2024, 11:03:54 pm »
Finding a weird error trying to build my tree, same error I had before.
Building from dooble works as expected, run qmake ../dooble.pro results in a message about QtCharts and a makefile. Whereas from dooble-dry, failure.
Code: [Select]
[L:\work\dooble\obj]qmake ../dooble.pro
Project MESSAGE: The QtCharts module has been discovered.

[L:\work\dooble\obj]cd ..\..\dooble-dry\obj

[L:\work\dooble-dry\obj]qmake ../dooble.pro
L:/QT6-6.2.X/mkspecs/features/toolchain.prf:76: Variable QMAKE_CXX.COMPILER_MACROS is not defined.
Project ERROR: failed to parse default search paths from compiler output

Weird. The dooble.pro files are identical, same environment.

9
Programming / Re: Qt6 Development
« on: May 19, 2024, 10:38:45 pm »
Thanks Dave! Working good here, also with new block list. One thing I notice with this one I didn't see before: at 'Settings'->'Web'-> 'Spell Checkers' there is a warning: 'en_US.bdic cannot be accessed!'. That file is available in the 'qtwebengine_dictionaries' directory and it worked with the 12/25/2023 version. Does it need to be updated or something?

Regards,

Yes, something is not right. First this build is from the Dooble upstream repository rather then mine which I forked from the Bitwise repository. Maybe some missed patches? I'll update my repository and do more of a proper release later.
Here, I had to create the qtwebengine_dictionaries directory under obj/ where I built and launched the new build. While this changed the error, it changed it to something like "could not access /en_CA.bdic" and after copying en_CA.bdic to the root, the warnings went away.
I investigate after syncing repositories.

10
Programming / Re: Qt6 Development
« on: May 19, 2024, 08:29:21 pm »
Updated dooble_filter.txt and dooble_accepted_or_blocked_domains.txt from todays pull.

11
Programming / Re: Qt6 Development
« on: May 19, 2024, 08:17:07 pm »
Latest from Paul ran fine here, using Qt6Widge.dll it seems.
Here's a new build. I'll do a better one later.
Weirdly the build could not find most libs until I ran emxomf on them and then renamed them to remove the _dll. At least now the build works here.
Edit: this is todays pull
Edit2: fix so dooble_settings.db is stored correctly instead of in the root.
Patch,
Code: [Select]
diff --git a/Source/dooble_main.cc b/Source/dooble_main.cc
index c8a22672..7fce9c2f 100644
--- a/Source/dooble_main.cc
+++ b/Source/dooble_main.cc
@@ -278,7 +278,6 @@ int main(int argc, char *argv[])
   QDir::setCurrent("/Applications/Dooble.d");
 #endif
   QString dooble_settings_path("");
-  dooble::s_application = new dooble_application(argc, argv);
 #if defined(Q_OS_WIN)
   auto bytes(qgetenv("DOOBLE_HOME").trimmed());
 
@@ -369,6 +368,12 @@ int main(int argc, char *argv[])
 
   dooble_settings::prepare_web_engine_environment_variables();
 
+  /*
+  ** Create the application after environment variables are prepared.
+  */
+
+  dooble::s_application = new dooble_application(argc, argv);
+
   /*
   ** Create a splash screen.
   */

Weird that this is needed.

12
Utilities / Re: K File Wizard
« on: May 19, 2024, 12:55:24 am »

BTW, kfw.exe runs also if KCRYPTO.DLL is in /usr/lib directory  .

/usr/local/lib is usual for DLLs that aren't managed by the package manager.

13
Applications / Re: Archive tool problem
« on: May 06, 2024, 08:01:38 am »
The list of Available Warpin packages is empty - I have yet to see this ever populated.

Here, the list of available Warpin packages is pretty full. Likely I have the correct URL entered as given on the testers list some time back. Unluckily I can't share it and it has been long enough that I'm not even sure of that.

14
Applications / Re: Archive tool problem
« on: May 06, 2024, 03:32:15 am »
You could try moving x:\sys\apps\anpm\repo_1.wir out of the way with ANPM closed and retry.
Almost sounds like a bigger problem with your wordpro problem as well, hopefully not hardware.

15
Programming / Re: ClassiCube porting thread
« on: May 05, 2024, 05:26:24 pm »
There's %LIBC_THREAD_MIN_STACK_SIZE% to specify the minimum stack size for new threads. Default is 4096 bytes.
Seems there's a flag too but can't remember it.

Pages: [1] 2 3 ... 322