Cygport and auto-manifestize compatibility manifest

Corinna Vinschen corinna-cygwin@cygwin.com
Wed Nov 20 16:48:00 GMT 2013


On Nov 20 17:26, Achim Gratz wrote:
> Corinna Vinschen writes:
> >   - Call the helper application, which basically works like this:
> >
> >       LoadLibrary("dummy.exe");
> >       FindResource(CREATEPROCESS_MANIFEST_RESOURCE_ID, RT_MANIFEST);
> >       LoadResource(...)
> >       LockResource(...)
> >       BeginUpdateResource("tcsh.exe")
> >       UpdateResource(RT_MANIFEST,CREATEPROCESS_MANIFEST_RESOURCE_ID,...)
> >       EndUpdateResource(...)
> >
> >    - The resulting executable actually worked and was treated as a
> >      Windows 8.1 executable.
> >
> >    If this hack is done after stripping, but before adding the
> >    .gnu_debuglink section, it could run automatically and all newly
> >    produced executables would be *finally* compatible with latest
> >    Windows versions.
> 
> Is that something that could be run during autorebase or bolted on to
> peflags perhaps?

Well, perhaps.  I'm just not sure it's the right thing to do it at
postinstall time.  I mean, it's not impossible, obviously, but it's
a lot of stuff per executable and running this for a few thousand .exe
files could take some time.

We would also have to make sure that the sections with long section
names are recreated after adding the .rsrc section, which is something
I don't quite see how to accomplish, right now.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20131120/9af877a9/attachment.sig>


More information about the Cygwin-apps mailing list