Update README.md

[gchatelet]

Change Quickstart section to match new default value for testing.

[Mizux]

should use ```sh

[Mizux]

As general comment (open to debate !)

0. I would move -H before -B aka tuple "source, build_dir" or "input, output" seems more natural to me.

1. -H. is an hidden option maybe we should advertise -S. even if only in "recent" CMake.
   src: https://cmake.org/cmake/help/latest/release/3.13.html#command-line (introduction to -S. and official -B)
   src: https://cmake.org/cmake/help/latest/release/3.14.html#command-line (--verbose)

2. Your command are Linux specific maybe we should try to provide a more neutral code block for our MacOS and Windows community.

• also ninja is not always installed and again on macos you'd want ot use xcode while on windows you'd stick to VisualStudio (which also have cmake builtin support since at least VS 2017)
  src: https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio/

My proposal (for 0,1,2):

cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release
cmake --build build --config Release

note1: --config Release is needed for multi config generator (like Visual Studio, Xcode and ninja-multiconfig) and noop for make/ninja generator
note2: the default target all is OK otherwise you have --target ALL_BUILD for VS and XCODE and all on make/ninja IIRC
note3: technically -DCMAKE_BUILD_TYPE=Release is ignored for multi config generator and you should use -DCMAKE_CONFIGURATION_TYPES="Debug;Release" if you want to restrict the default list being Debug, Release,RelWithDebInfo and MinSizeRel
src: https://cmake.org/cmake/help/latest/variable/CMAKE_CONFIGURATION_TYPES.html

3. Simply add a note about using -G to change the default generator ?
   note: if you use -G without argument cmake will fail with an "usage" message listing all available generator on your host system ;)
   e.g. on my gLinux (* is the default one, chosen by CMake)

%cmake -G
CMake Error: No generator specified for -G

Generators
  Green Hills MULTI            = Generates Green Hills MULTI files
                                 (experimental, work-in-progress).
* Unix Makefiles               = Generates standard UNIX makefiles.
  Ninja                        = Generates build.ninja files.
  Ninja Multi-Config           = Generates build-<Config>.ninja files.
  Watcom WMake                 = Generates Watcom WMake makefiles.
  CodeBlocks - Ninja           = Generates CodeBlocks project files.
  CodeBlocks - Unix Makefiles  = Generates CodeBlocks project files.
  CodeLite - Ninja             = Generates CodeLite project files.
  CodeLite - Unix Makefiles    = Generates CodeLite project files.
  Eclipse CDT4 - Ninja         = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.
  Kate - Ninja                 = Generates Kate project files.
  Kate - Unix Makefiles        = Generates Kate project files.
  Sublime Text 2 - Ninja       = Generates Sublime Text 2 project files.
  Sublime Text 2 - Unix Makefiles
                               = Generates Sublime Text 2 project files.

4. For testing I would use

cmake --build build --config Release --target test

BUT with a note for windows/xcode user to use target RUN_TESTS (win) and RUN_TEST (xcode) respectively...

src:

[gchatelet]

Thx a lot for the suggestions.
I'll update the patch with a new version and we can discuss from here.

[Mizux]

LGTM