From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001964] New: ConfigTool - Patch to add a manifest when compiled as a native Windows application
Date: Fri, 28 Mar 2014 14:52:00 -0000 [thread overview]
Message-ID: <bug-1001964-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001964
Bug ID: 1001964
Summary: ConfigTool - Patch to add a manifest when compiled as
a native Windows application
Product: eCos
Version: CVS
Target: All
Architecture/Host Other
OS:
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Patches and contributions
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: andy@xylanta.com
CC: ecos-patches@ecos.sourceware.org
Created attachment 2496
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2496&action=edit
Patch to add a manifest when compiled as a native Windows application
Following on from the patch in 1001963 (ConfigTool built as a native Windows
application using MinGW), it appears that in order to use the Cygwin tools for
building the application needs to be running with administrator rights. This
patch adds a manifest to the resources requesting these rights. Tested on
Windows-7 64-bit compiling with TDM-GCC 4.8.1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-03-28 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 14:52 bugzilla-daemon [this message]
2014-03-28 14:52 ` [Bug 1001964] " bugzilla-daemon
2014-03-28 16:52 ` bugzilla-daemon
2014-05-22 12:11 ` bugzilla-daemon
2014-05-22 12:12 ` bugzilla-daemon
2014-05-22 12:13 ` bugzilla-daemon
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=bug-1001964-104@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.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).