From e00ba23e4a52737c2782c55b77b9a27750ae0623 Mon Sep 17 00:00:00 2001 From: Henry Fredrick Schreiner Date: Wed, 1 Feb 2017 14:42:59 -0500 Subject: [PATCH] Adding test for GCC 4.7 --- .travis.yml | 8 ++++++++ README.md | 4 ++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/.travis.yml b/.travis.yml index 25a6ba0..bba555c 100644 --- a/.travis.yml +++ b/.travis.yml @@ -23,6 +23,14 @@ matrix: packages: - g++-4.8 env: COMPILER=4.8 + - compiler: gcc + addons: + apt: + sources: + - ubuntu-toolchain-r-test + packages: + - g++-4.7 + env: COMPILER=4.7 - compiler: clang addons: apt: diff --git a/README.md b/README.md index 63ec234..5408486 100644 --- a/README.md +++ b/README.md @@ -7,10 +7,10 @@ Why write another CLI parser? The following attributes were deemed most important in a CLI parser library: -* Easy to include (i.e., header only, one file if possible): While many programs depend on Boost, that should not be a requirement if all you want is CLI parsing. +* 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. * Work with GCC 4.8 (CentOS 7) or above, or MacOS Clang (C++11) -* Well tested +* Well tested using Travis * Good help printing (in progress) * Standard idioms supported naturally, like flags * Easy to execute, with help, parse errors, etc. providing correct exit and details. -- libgit2 0.21.4