This is the mail archive of the
mailing list for the GCC project.
Re: RFA: x86 backend: Add default-manifest to Cygwin/MinGW links
- From: Kai Tietz <ktietz70 at googlemail dot com>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: Richard Henderson <rth at redhat dot com>, Jan Hubicka <hubicka at ucw dot cz>, Uros Bizjak <ubizjak at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, vinschen at redhat dot com, Kai Tietz <ktietz at redhat dot com>
- Date: Wed, 23 Apr 2014 10:59:29 +0200
- Subject: Re: RFA: x86 backend: Add default-manifest to Cygwin/MinGW links
- Authentication-results: sourceware.org; auth=none
- References: <87zjjcctpa dot fsf at redhat dot com>
2014-04-23 10:53 GMT+02:00 Nick Clifton <email@example.com>:
> Hi Guys,
> Please could I have permission to apply the patch below ? Ideally for
> both mainline and the 4.9 branch.
> The patch adds a file called "default-manifest.o" to the end of a
> final link command line for the Cygwin and MinGW targets. The file is
> only added if it can be found in the library search path(s), so the
> patch will have no effect if the file does not exist.
> The default manifest file contains a resource section (.rsrc) holding
> information necessary for the binary to be run under Windows 8. It is
> placed last on the linker command line so that a user provided
> manifest, if there is one, will take precedence over the default
> The manifest used to be automatically added by the linker, but this
> proved to be problematic as the linker is not good at selectively
> inserting binaries. The manifest itself is provided by a separate
> project which will have to become a new dependency for the Cygwin and
> MinGW projects.
Well, I am a bit concerned about the position of the manifest-object.
What will actually happen, if user specifies an user-specific
manifest-object. Will the default one, if present, be ignored, or
will it be still linked?