From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: New package: windows-default-manifest-6.3-1
Date: Wed, 25 Jun 2014 08:36:00 -0000 [thread overview]
Message-ID: <20140625081218.GL1803@calimero.vinschen.de> (raw)
Hi folks,
I just uploaded windows-default-manifest-6.3-1.
This new 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.
This package is in the "Base" category, so it will be pulled in by
default. The version number reflects the OS kernel version supported
by this manifest (6.3 == Windows 8.1).
For reference:
* http://msdn.microsoft.com/en-us/library/windows/desktop/hh848036%28v=vs.85%29.aspx
It would be too nice if this change would be consistent throughout
all APIs. But no. GetVersionEx returns "Windows 8" as version:
* http://msdn.microsoft.com/en-us/library/windows/desktop/dn302074%28v=vs.85%29.aspx (note especially the user comments ;))
Live long and prosper,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
reply other threads:[~2014-06-25 8:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140625081218.GL1803@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-announce@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).