This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Cygport and auto-manifestize compatibility manifest
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 20 Nov 2013 09:47:05 -0500
- Subject: Re: Cygport and auto-manifestize compatibility manifest
- Authentication-results: sourceware.org; auth=none
- References: <20131120132853 dot GN2936 at calimero dot vinschen dot de>
On 11/20/2013 8:28 AM, Corinna Vinschen wrote:
Apart from the fact that it would be nice if our linker would do this
automatically and transparently,
Or libtool, if you use it to link your exe? PTC...since $new-libtool is
pretty high on my to-do list.
It'd be better if there was an option to ld/gcc, of course -- but the
details would be rather complicated. You wouldn't want to invoke a
separate executable like windres b/c then your build recipe/makefile
would have to change. Best if $LD_FLAGS could be used... maybe
something hideously ugly like -w32-manifest-compat <file> [1] where
<file> is not a full XML manifest, but rather contains a list of GUIDs
[2], and ld/gcc autogenerates the manifest with just that stuff.
That way, if you manually create a manifest (for other purposes), you
could just /not/ use the new flag.
I know, SHTDI...
is that something we should do in
cygport for the time being?
[1] or comma-separated list of GUIDs? That'd get long and ugly, very fast.
[2] not OS names, b/c then (a) ld/gcc would have to "know" the
corresponding GUID, and (b) the GUID<->OS database would be out of date
and require a binutils/gcc patch every time Redmond released a new
service pack.
--
Chuck