From: "Cygwin gengetopt co-Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: New: gengetopt 2.23
Date: Wed, 04 Aug 2021 10:14:37 -0600 [thread overview]
Message-ID: <20210804101437.25240-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
Generates a function to parse and validate command line options.
The missing x86 package has now been added to the Cygwin distribution.
The following package has been added to the Cygwin distribution:
* gengetopt 2.23
Reads an interface description file, and writes a file containing a
command-line parser function.
Generates a C function that calls the getopt_long function to parse
command line options, to validate them, fill a struct, or output a
usage message.
Can also generate functions to save command line options into an rc
file, and to read command line options from an rc file.
Handles long options starting with '--' and short options starting with
'-' followed by one character, without parameters and with 11 types of
parameters (including flag, int, double, string, and function call)."
For more information see the project home page:
https://www.gnu.org/software/gengetopt/
or the repo README:
https://git.savannah.gnu.org/cgit/gengetopt.git/tree/README
Please see below or read /usr/share/doc/gengetopt/NEWS after installation
for details of the latest features:
https://git.savannah.gnu.org/cgit/gengetopt.git/tree/NEWS
Version 2.23
* Gengen and gengetopt are required when building from git.
When building from tarball, everything works like it did before.
* To mimic behaviour of coreutils, version string is no longer part of
--help, and usage is printed before purpose in --help
* Use singular (`[OPTION]...`, `[FILE]...`) instead of plural
(`[OPTIONS]...`, `[FILES]...`)
* Fix spelling of `--unnamed`. `--unamed` still provided for backwards
compatibility.
* Drop IRIX compatibility
reply other threads:[~2021-08-04 16:20 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=20210804101437.25240-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@cygwin.com \
--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).