-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support options like --config
--part
and --port
#1922
Comments
In PR #1698, I have replaced the While at it, I also added Quoting the FreeBSD man page for
We already have a Windows implementation of So The |
To actually answer the question: The downside to using |
getopt_long() seems to drop in pretty painlessly, and is already present in the windows getopt used by avrdude, and works on both macos and linux builds as well, so it should be pretty safe. (from the avrfreaks discussion): Then it was just a matter of replacing the getopt() call with one to getopt_long() (and adding the structure with the long form commands...) Everything else stayed the same!
That does leave a bunch of help text and error messages that contain only the short command forms... |
I created a post over at the Avrfreaks forum announcing that Avrdude v8.0 has just been released. The feedback was mixed (some pointing out that Avrdude is just a CLI tool and not a full-blown GUI, and thus not relevant in 2024), but @WestfW mentioned that the option flags (
-C
,-c
,-p
etc) could be difficult to remember, and having full-blown--flags
would be nice.Avrdude currently uses
getopt
, and this doesn't support--flags
. Instead, we'll have to useargp
.Are there any downsides to using
agrp
instead ofgetopt
?The text was updated successfully, but these errors were encountered: