The default manifest file is used to workaround a bug in the Windows
version reporting API. The manifest file needs to be updated for every
Windows release, and all programs relinked to take effect.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin
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.
ty 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
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
On 25/06/2014 11:21, Corinna Vinschen wrote:
On Jun 25 11:00, Marco Atzeri wrote:
On 25/06/2014 10:12, Corinna Vinschen wrote:
Hi folks,
Did you read the comments in the 2nd link I sent with my announcement?
There are more unhappy devs...
I read. Very stupid broken behavior and also very d
On Jun 25 11:00, Marco Atzeri wrote:
>
> On 25/06/2014 10:12, Corinna Vinschen wrote:
> >Hi folks,
> >
> >
> >I just uploaded windows-default-manifest-6.3-1.
> >
> >This new package contains nothing but a default application
> >compatibility manif
On 25/06/2014 10:12, Corinna Vinschen wrote:
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
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
On 5/21/2014 21:19, Ken Brown wrote:
>>
>> For the default manifest to get going we also need the patcha new GCC
>> with Nick's patch from
>>
>>https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01378.html
>>
>> Is that easily backportable to GCC
uilt version of binutils, which doesn't
provide a default manifest, because of the problem I reported here:
http://cygwin.com/ml/cygwin/2014-04/msg00199.html
I'll update binutils ASAP.
For the default manifest to get going we also need the patcha new GCC
with Nick's patch from
ause I
> >currently have to use a self-built version of binutils, which doesn't
> >provide a default manifest, because of the problem I reported here:
> >
> > http://cygwin.com/ml/cygwin/2014-04/msg00199.html
>
> I'll update binutils ASAP.
For the de
01387.html
> https://sourceware.org/bugzilla/show_bug.cgi?id=16790#c9
> https://sourceware.org/bugzilla/show_bug.cgi?id=16807#c8
>
>I'm not trying to rush any maintainers, but I'm asking because I
>currently have to use a self-built version of binutils, which doesn't
>
e.org/bugzilla/show_bug.cgi?id=16807#c8
I'm not trying to rush any maintainers, but I'm asking because I
currently have to use a self-built version of binutils, which doesn't
provide a default manifest, because of the problem I reported here:
http://cygwin.com/ml/cygwin/2
he current binutils, I end up with an
> >executable that won't run after it's stripped (at least on x86_64). I
> >traced this to the fact that emacs-w32 comes with its own manifest. My
> >understanding is that the emacs-w32 manifest should take precedence over
> &g
ter it's stripped (at least on x86_64). I
>traced this to the fact that emacs-w32 comes with its own manifest. My
>understanding is that the emacs-w32 manifest should take precedence over
>the Cygwin default manifest, but something's going wrong in this case.
>
>Here&
emacs-w32 comes with its own manifest. My
understanding is that the emacs-w32 manifest should take precedence over
the Cygwin default manifest, but something's going wrong in this case.
Here's a simple test case to illustrate the problem, using a slight
modification of the resource f
16 matches
Mail list logo
