From 7fee3f3695f0066cad5c9fe98752efb2f4252af8 Mon Sep 17 00:00:00 2001 From: Henry Fredrick Schreiner Date: Sat, 11 Feb 2017 10:38:52 -0500 Subject: [PATCH] Move to using clang 3.5 --- .travis.yml | 2 ++ README.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 3fc5c0d..6897ba1 100644 --- a/.travis.yml +++ b/.travis.yml @@ -14,6 +14,7 @@ matrix: - ubuntu-toolchain-r-test packages: - clang-3.5 + env: COMPILER=3.5 - compiler: gcc addons: apt: @@ -33,6 +34,7 @@ matrix: install: - python -c 'import sys; print(sys.version_info[:])' - if [ "$CXX" = "g++" ]; then export CXX="g++-$COMPILER" CC="gcc-$COMPILER"; fi +- if [ "$CXX" = "clang++" ] && [ "$TRAVIS_OS_NAME" = "linux" ]; then export CXX="clang++-$COMPILER" CC="clang-$COMPILER"; fi - DEPS_DIR="${TRAVIS_BUILD_DIR}/deps" - CMAKE_URL="https://cmake.org/files/v3.7/cmake-3.7.2-Linux-x86_64.tar.gz" - cd "${DEPS_DIR}" diff --git a/README.md b/README.md index ec8dd90..b9d09e3 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ The following attributes are what I believe are important in a CLI parser librar * 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.7+ (such as GCC 4.8 on CentOS 7) or above, or Clang 3.4+. (3.5 stdlib is required to build googlemock test) Works on Linux and MacOS. +* Work with GCC 4.7+ (such as GCC 4.8 on CentOS 7) or above, or Clang 3.5+. (3.4 only fails because of tests, googlemock does not support it.) Works on Linux and MacOS. * Well tested using Travis. * Good help printing (in progress). * Standard idioms supported naturally, like grouping flags, the positional seperator, etc. -- libgit2 0.21.4