Hi Jakob,
On 12/15/2025 7:47 AM, Jakob Bohm via Cygwin wrote:
On 13/12/2025 00:16, Mark Geisert via Cygwin wrote:
[...]
Unfortunately the names of the DLLs haven't changed between 5.9.* and
5.15.18. One has to look at the update times to notice the problem:
~ cd /usr/bin
/usr/bin ls -ltr cygQt5*dll | tail
-rwxr-xr-x 1 Mark None 306195 May 28 2025 cygQt5OpenGL-5.dll*
-rwxr-xr-x 1 Mark None 1564179 May 28 2025 cygQt5Network-5.dll*
-rwxr-xr-x 1 Mark None 340499 May 28 2025 cygQt5PrintSupport-5.dll*
-rwxr-xr-x 1 Mark None 237587 May 28 2025 cygQt5Sql-5.dll*
-rwxr-xr-x 1 Mark None 289299 May 28 2025 cygQt5Test-5.dll*
-rwxr-xr-x 1 Mark None 4923923 May 28 2025 cygQt5Core-5.dll*
-rwxr-xr-x 1 Mark None 234003 May 28 2025 cygQt5Xml-5.dll*
-rwxr-xr-x 1 Mark None 1208851 May 28 2025 cygQt5XcbQpa-5.dll*
-rwxr-xr-x 1 Mark None 5338643 May 28 2025 cygQt5Gui-5.dll*
-rwxr-xr-x 1 Mark None 6160915 May 28 2025 cygQt5Widgets-5.dll*
/usr/bin cd /usr/lib/debug/usr/bin
/usr/lib/debug/usr/bin ls -ltr cygQt5*dll.dbg | tail
-rwxr-xr-x 1 Mark Administrators 18556839 Dec 5 16:12
cygQt5OpenGL-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 77383641 Dec 5 16:12
cygQt5Network-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 12359956 Dec 5 16:12
cygQt5PrintSupport-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 126305401 Dec 5 16:12
cygQt5Core-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 8077901 Dec 5 16:12
cygQt5Sql-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 8935879 Dec 5 16:12
cygQt5Test-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 56896442 Dec 5 16:13
cygQt5XcbQpa-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 3337397 Dec 5 16:13
cygQt5Xml-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 209244469 Dec 5 16:13
cygQt5Gui-5.dll.dbg*
-rwxr-xr-x 1 Mark Administrators 182191608 Dec 5 16:14
cygQt5Widgets-5.dll.dbg*
/usr/lib/debug/usr/bin
..mark
Protip: Properly built PE, NE, LE or LX format DLL and EXE files are
supposed to contain a
"Version information" structure, which specifies a textual file
description, copyright
information (such as "(C) year,year FSF Inc." and "LGPL 3.0+" as well as
computer
comparable binary version numbers in the form U16[4] { major, minor,
sub, patch } .
Thank you for your input. I used 'ls' because that showed the set of
most recently updated DLLs was precisely the set in the 1.15.18 test
build. It was faster to check a hunch this way than opening each file
individually through an Explorer GUI or PS script.
It didn't occur to me at the time, but the standard Cygwin tool
'cygcheck' could have provided me the similar information: the versions
of each package. So I already could get package-level and file-level
confirmations of my hunch.
The enhancement you suggest should ideally be applied Cygwin-wide. So
it might make sense to generate the Version Information structure with
our build tool 'cygport'. Patches would be thoughtfully considered. I
don't think there's an existing Cygwin mechanism for displaying such
structures, so that would have to be developed too.
..mark
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
