From 73d5837a0b057a8870ddcb7c4e4f1940e240f90f Mon Sep 17 00:00:00 2001 From: Henry Fredrick Schreiner Date: Sun, 19 Feb 2017 16:59:42 -0500 Subject: [PATCH] Adding info to readme --- CHANGELOG.md | 1 + README.md | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5ceba074..87fc05ac 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,7 @@ * Added `require_subcommand` to `App`, to simplify forcing subcommands. Do not "chain" with `add_subcommand`, since that is the subcommand, not the master `App`. Untested. * Added printout of ini file text given parsed options, skips flags. * Support for quotes and spaces in ini files +* Support for Windows (added Appveyor) (Still use `--` syntax) ## Version 0.4 diff --git a/README.md b/README.md index 45f98d63..98fb0e36 100644 --- a/README.md +++ b/README.md @@ -14,9 +14,9 @@ An acceptable CLI parser library should be all of the following: * Easy to include (i.e., header only, one file if possible, no external requirements): While many programs depend on Boost, that should not be a requirement if all you want is CLI parsing. * Short Syntax: This is one of the main points of a CLI parser, it should make variables from the command line nearly as easy to define as any other variables. If most of your program is hidden in CLI parsing, this is a problem for readability. -* C++11 or better: Should work with GCC 4.7+ (such as GCC 4.8 on CentOS 7) or above, or Clang 3.5+. (Note: for CLI11, Clang 3.4 only fails because of tests, googlemock does not support it.) -* Work at least on Linux and MacOS. -* Well tested using Travis. +* C++11 or better: Should work with GCC 4.7+ (such as GCC 4.8 on CentOS 7) or above, or Clang 3.5+, or MSVC 2015+. (Note: for CLI11, Clang 3.4 only fails because of tests, googlemock does not support it.) +* Work on Linux, MacOS, and Windows. +* Well tested using Travis (Linux and Mac) and [Appveyor](https://ci.appveyor.com/project/HenrySchreiner/cli11) (Windows). * Clear help printing. * Standard shell idioms supported naturally, like grouping flags, a positional separator, etc. * Easy to execute, with help, parse errors, etc. providing correct exit and details.