From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: windres broken
Date: Sat, 07 Jan 2017 13:47:00 -0000 [thread overview]
Message-ID: <63dfbb31-3cf1-c5a9-059a-4aa78fa7fcfc@cornell.edu> (raw)
In-Reply-To: <CAAXzdLWPtfyKB+YSNfhF=q45UhkwBMRm_BYznjd6=ku-H22=Pw@mail.gmail.com>
On 1/6/2017 11:10 PM, Steven Penny wrote:
> Something is wrong with windres:
>
> $ windres myapp.rc -o myapp.res
> Usage: windres [option(s)] [input-file] [output-file]
> The options are:
> -i --input=<file> Name input file
> -o --output=<file> Name output file
> -J --input-format=<format> Specify input format
>
> The syntax above is shown here:
>
> http://cygwin.com/cygwin-ug-net/windres.html
>
> Yet the command just prints usage instead of doing the thing. This command
> works:
>
> windres myapp.rc myapp.res
>
> However this shouldnt be needed as described by the man:
>
> -i filename
> The name of the input file. If this option is not used, then
> windres will use the first non-option argument as the input file
> name.
>
> This is a problem because Git itself uses the "input -o output" syntax, which
> should be working:
>
> http://github.com/git/git/blob/e05806d/Makefile#L1816-L1819
That syntax works for me. Are you sure you're using Cygwin's windres?
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-01-07 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 4:10 Steven Penny
2017-01-07 13:47 ` Ken Brown [this message]
2017-01-07 18:54 ` Steven Penny
2017-01-07 22:14 ` Ken Brown
2017-01-11 5:24 ` Steven Penny
2017-01-07 14:01 ` Hans-Bernhard Bröker
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=63dfbb31-3cf1-c5a9-059a-4aa78fa7fcfc@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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).