Put short flags first in help message so everything lines up better and they are easier to discover.

dilijev · dilijev · commit 403765699e37 · 2016-05-16T13:20:26.000-07:00
diff --git a/build.sh b/build.sh
@@ -20,15 +20,15 @@ PRINT_USAGE() {
     echo "  build.sh [options]"
     echo ""
     echo "  options:"
-    echo "    --cxx             : Path to Clang++ (see example below)"
-    echo "    --cc              : Path to Clang   (see example below)"
-    echo "    --debug, -d       : Debug build (by default Release build)"
-    echo "    --help, -h        : Show help"
-    echo "    --icu             : Path to ICU include folder (see example below)"
-    echo "    --jobs, -j        : Multicore build (i.e. -j=3 for 3 cores)"
-    echo "    --ninja, -n       : Build with ninja instead of make"
-    echo "    --test-build, -t  : Test build (by default Release build)"
-    echo "    --verbose, -v     : Display verbose output including all options"
+    echo "        --cxx         : Path to Clang++ (see example below)"
+    echo "        --cc          : Path to Clang   (see example below)"
+    echo "    -d, --debug       : Debug build (by default Release build)"
+    echo "    -h, --help        : Show help"
+    echo "        --icu         : Path to ICU include folder (see example below)"
+    echo "    -j, --jobs        : Multicore build (i.e. -j=3 for 3 cores)"
+    echo "    -n, --ninja       : Build with ninja instead of make"
+    echo "    -t, --test-build  : Test build (by default Release build)"
+    echo "    -v, --verbose     : Display verbose output including all options"
     echo ""
     echo "  example:"
     echo "    ./build.sh --cxx=/path/to/clang++ --cc=/path/to/clang -j=2"
