From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 3.3.1: Missing VersionInfo resource fields for cygwin1.dll
Date: Mon, 15 Nov 2021 10:20:32 +0100 [thread overview]
Message-ID: <YZImYL5xu5d1Fz7w@calimero.vinschen.de> (raw)
In-Reply-To: <a860b39c-8aa5-a111-8346-a47de2e158bd@SystematicSw.ab.ca>
On Nov 12 15:49, Brian Inglis wrote:
> On 2021-11-11 12:26, Marco Atzeri via Cygwin wrote:
> > On 11.11.2021 19:47, Hiya Z via Cygwin wrote:
> > > Upgraded to 3.3.x and noticed that the VersionInfo resource fields
> > > for all binaries under bin are blank (Properties->Details from
> > > Explorer). Is this by intent or a miss?
> > > It is breaking my application installer that relied on version check for
> > > cygwin1.dll.
>
> > Binaries should not have VersionInfo, only cygwin1.dll had it.
> > Not checked on 3.3.x
>
> Confirmed missing from cygwin.dll 3.3.0 64 and 32 bit and present up to at
> least 3.2.1. Also present in some other DLLs:
> cyg{asprintf,crypto,freetype,icons,iconv,lzma,ruby,ssl,unistring,usb,z}*.dll
Yeah, the version info resource isn't copied into the DLL for some
reason. This is probably related to the changes in the build system
using automake now. Something got lost in the transition...
Corinna
next prev parent reply other threads:[~2021-11-15 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 18:47 3.3.1: Missing VersionInfo resource for all executables/DLLs Hiya Z
2021-11-11 19:26 ` Marco Atzeri
2021-11-12 22:49 ` 3.3.1: Missing VersionInfo resource fields for cygwin1.dll Brian Inglis
2021-11-15 9:20 ` Corinna Vinschen [this message]
2021-11-12 20:59 ` 3.3.1: Missing VersionInfo resource " Hiya Z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YZImYL5xu5d1Fz7w@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).