bump cli11 version

CMakeLists.txt

@@ -109,8 +109,7 @@ if( BUILD_CLI_UTILITIES )
   set( CLI11_SINGLE_FILE OFF CACHE INTERNAL "Don't use single file CLI11")
   FetchContent_Declare( cli11
     GIT_REPOSITORY https://github.com/CLIUtils/CLI11
-    GIT_TAG        291c58789c031208f08f4f261a858b5b7083e8e2 # v2.3.2
-    PATCH_COMMAND patch -N CMakeLists.txt < ${CMAKE_SOURCE_DIR}/cli11.patch || true
+    GIT_TAG        88e9bb17418ee730817d5942894d99a4bdd78fb3 # v2.4.0
   )
   FetchContent_MakeAvailable(cli11)
 

README.md

@@ -20,6 +20,22 @@ This combination gives SPERR flexibility to compress targetting different qualit
 2) peak signal-to-noise ratio (PSNR), and 3) point-wise error (PWE).
 The name of SPERR stands for **SP**eck with **ERR**or bounding.
 
+## Quick Build
+SPERR requires 1) a working C++ compiler and 2) CMake tools to build. On a Unix-like system,
+the build steps are the following:
+
+```bash
+git clone https://github.com/NCAR/SPERR.git # clone the repo
+mkdir SPERR/build                           # create the build directory
+cd SPERR/build                              # enter the build directory
+cmake ..                                    # Linux: use cmake to configure the project (with OpenMP)
+cmake -DUSE_OMP=OFF ..                      # Mac: use cmake to configure the project (OpenMP disabled)
+make -j 8                                   # build the project
+ctest .                                     # run unit tests, which should have 100% tests passed
+```
+
+After a successful build, the executables (CLI tools) are kept in the `./bin` directory.
+
 ## Documentation
 
 SPERR documentation is hosted on Github [Wiki](https://github.com/NCAR/SPERR/wiki) pages. To get started, one might want to