From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: windres broken
Date: Sat, 07 Jan 2017 14:01:00 -0000 [thread overview]
Message-ID: <56a896cf-4eea-1832-58c9-932be7868232@t-online.de> (raw)
In-Reply-To: <CAAXzdLWPtfyKB+YSNfhF=q45UhkwBMRm_BYznjd6=ku-H22=Pw@mail.gmail.com>
Am 07.01.2017 um 05:10 schrieb Steven Penny:
> 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
What version of windres is that? That same command works just fine,
here (from package binutils-2.25-4 on cygwin64).
> The syntax above is shown here:
>
> http://cygwin.com/cygwin-ug-net/windres.html
That's just an example, and for actual documentation it points to GNU
binutils documentation. So if anything, this example could be wrong,
but if there's really something wrong, you should take this up with the
binutils people.
> Yet the command just prints usage instead of doing the thing.
Well, strictly speaking, according to that syntax, the above command
_is_ wrong. -o myapp.res is an option, and as such it should have come
_before_ the [input-file] argument, myapp.rc. But like I said, the
problem does not reproduce here.
> This command works:
>
> windres myapp.rc myapp.res
Well, FWIW that one does follow the syntax.
--
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
prev parent reply other threads:[~2017-01-07 14:01 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
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 [this message]
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=56a896cf-4eea-1832-58c9-932be7868232@t-online.de \
--to=hbbroeker@t-online.de \
--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).