From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: Commit: Add default manifest resource for Cygwin & MinGW
Date: Thu, 27 Feb 2014 14:11:00 -0000 [thread overview]
Message-ID: <8738j4vedh.fsf@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
Hi Guys,
I am applying the patch below to add a default manifest in to the
final links performed by the Cygwin and MinGW targets. The manifest
is necessary in order for the linked binaries to be executed in a
Windows 8 environment.
The manifest is added using a linker script so that this feature will
be compiler-neutral. The resource merging code in the linker means
that if an application provides its own manifest then the default
manifest will be ignored.
Cheers
Nick
ld/ChangeLog
2014-02-27 Nick Clifton <nickc@redhat.com>
* configure.in (all_emul_extra_binaries): New variable. Populated
by invoking configure.tgt.
(EMUL_EXTRA_BINARIES): New substitution.
* configure: Regenerate.
* configure.tgt (target_extra_binaries): New variable. Set to
default-manifest.o for Cygwin and MinGW targets.
* Makefile.am (EMUL_EXTRA_BINARIES): New variable. Initialised
by the configure script.
(ALL_EMUL_EXTRA_BINARIES): New variable.
(default-manifest.o): New rule to build the default manifest.
(ld_new_DEPENDENCIES): Add EMUL_EXTRA_BINARIES.
(install-data-local): Add EMUL_EXTRA_BINARIES.
* Makefile.in: Regenerate.
* ld.texinfo: Document default manifest support.
* emulparams/i386pe.sh (DEFAULT_MANIFEST): Define.
* emulparams/i386pep.sh (DEFAULT_MANIFEST): Define.
* emultempl/default-manifest.rc: New file.
* scripttempl/pe.sc (R_RSRC): Include DEFAULT_MANIFEST, if defined.
* scripttempl/pep.sc (R_RSRC): Likewise.
ld/testsuite/ChangeLog
2014-02-27 Nick Clifton <nickc@redhat.com>
* ld-pe/longsecn-1.d: Allow for extra sections.
* ld-pe/longsecn-2.d: Likewise.
* ld-pe/longsecn.d: Likewise.
* ld-pe/secrel.d: Likewise.
[-- Attachment #2: ld.default-manifest.patch.xz --]
[-- Type: application/x-xz, Size: 3672 bytes --]
reply other threads:[~2014-02-27 14:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738j4vedh.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).