[ANNOUNCEMENT] New package: windows-default-manifest-6.4-1

[ANNOUNCEMENT] New package: windows-default-manifest-6.4-1

[Corinna Vinschen]

Hi folks,


I just uploaded windows-default-manifest-6.4-1.

This adds the OS GUID for Windows 10 to the default manifest file.

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.

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.4 == Windows 10).


Keep calm and carry on,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] New package: windows-default-manifest-6.4-1

[Andrew Schulman]

> 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?

Thanks, Andrew


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] New package: windows-default-manifest-6.4-1

[Corinna Vinschen]

[-- 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 --]