From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] New package: windows-default-manifest-6.4-1
Date: Sun, 26 Oct 2014 10:31:00 -0000 [thread overview]
Message-ID: <20141026103126.GT20607@calimero.vinschen.de> (raw)
In-Reply-To: <gn5o4adb4id8adln63poindv9n1i1p0249@4ax.com>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
On Oct 25 17:33, Andrew Schulman wrote:
> > This package contains nothing but a default application compatibility
> > manifest, which gets linked in by GCC by default, and which is supposed
> > to claim compatibility with the latest Windows versions available at the
> > time.
> >
> > Adding such a manifest got necessary due to a change in Windows 8.1. On
> > earlier OS versions, applications without manifest were treated as
> > compatible with the current OS. Starting with Windows 8.1, an
> > executable without manifest is treated as being compatible only with the
> > oldest supported OS version of the OS compatibility layer.
> >
> > That means, all applications without manifest are running in a Window
> > Vista compatibility layer on Windows 8.1. This affects all Cygwin
> > executables to date. By adding the default manifest to newly built
> > packages, we're slowly getting to run our executables with full OS
> > compatibility.
>
> I'm sorry, can you please remind me: Is there anything I have to do to
> include the new manifest? Or is it enough just to rebuild the executable
> once this package is installed?
Just rebuilding is sufficient.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-10-26 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:56 Corinna Vinschen
2014-10-25 21:33 ` Andrew Schulman
2014-10-26 10:31 ` Corinna Vinschen [this message]
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=20141026103126.GT20607@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).