Updated -help message in clang-check.

[alexfh]

Summary

Provide more information on usage in -help

[klimek]

clang-check/ClangCheck.cpp

25

I think especially with the upcoming patch to allow other build system integration, I'd rather not call this cmake-output-dir. I think build-path is better, and having an explanation that mentions CMake as an example.

[alexfh]

Addressed comments.

[alexfh]

clang-check/ClangCheck.cpp

25

makes sense.
what about "If the path is\n"

"relative, the current working directory needs to be in the CMake source\n"	
"tree and the file must be in a subdirectory of the current working\n"	
"directory." part? can we make this eat any form of paths?

[alexfh]

Minor wording change

[alexfh]

Updated, resolved conflicts

clang-check/ClangCheck.cpp

 //===- examples/Tooling/ClangCheck.cpp - Clang check tool -----------------===//
 //
 //                     The LLVM Compiler Infrastructure
 //
 // This file is distributed under the University of Illinois Open Source
 // License. See LICENSE.TXT for details.
 //
 //===----------------------------------------------------------------------===//
 //
 //  This file implements a clang-check tool that runs the
 //  clang::SyntaxOnlyAction over a number of translation units.
 //
-//  Usage:
-//  clang-check <cmake-output-dir> <file1> <file2> ...
-//
-//  Where <cmake-output-dir> is a CMake build directory in which a file named
-//  compile_commands.json exists (enable -DCMAKE_EXPORT_COMPILE_COMMANDS in
-//  CMake to get this output).
-//
-//  <file1> ... specify the paths of files in the CMake source tree. This  path
-//  is looked up in the compile command database. If the path of a file is
-//  absolute, it needs to point into CMake's source tree. If the path is
-//  relative, the current working directory needs to be in the CMake source
-//  tree and the file must be in a subdirectory of the current working
-//  directory. "./" prefixes in the relative files will be automatically
-//  removed, but the rest of a relative path must be a suffix of a path in
-//  the compile command line database.
-//
-//  For example, to use clang-check on all files in a subtree of the source
-//  tree, use:
-//
-//    /path/in/subtree $ find . -name '*.cpp'| xargs clang-check /path/to/source
-//
 //===----------------------------------------------------------------------===//
 
 #include "llvm/Support/CommandLine.h"
 #include "clang/Frontend/FrontendActions.h"
 #include "clang/Tooling/CompilationDatabase.h"
 #include "clang/Tooling/Tooling.h"
 
 using namespace clang::tooling;
 using namespace llvm;
 
 cl::opt<std::string> BuildPath(
   "p",
-  cl::desc("<build-path>"),
+  cl::desc("<cmake-output-dir>"),
   cl::Optional);
 
 cl::list<std::string> SourcePaths(
   cl::Positional,
   cl::desc("<source0> [... <sourceN>]"),
   cl::OneOrMore);
 
+static cl::extrahelp MoreHelp(
+    "\n"
+    "<cmake-output-dir> is a CMake build directory in which a file named\n"
+    "compile_commands.json exists (enable -DCMAKE_EXPORT_COMPILE_COMMANDS in\n"
+    "CMake to get this output). When a CMake output directory is not\n"
+    "specified, clang-check will attempt to locate compile_commands.json\n"
+    "automatically in all parent paths of the first input file.\n"
+    "\n"
+    "<source0> ... specify the paths of files in the CMake source tree. This\n"
+    "path is looked up in the compile command database. If the path of a file\n"
+    "is absolute, it needs to point into CMake's source tree. If the path is\n"
+    "relative, the current working directory needs to be in the CMake source\n"
+    "tree and the file must be in a subdirectory of the current working\n"
+    "directory. \"./\" prefixes in the relative files will be automatically\n"
+    "removed, but the rest of a relative path must be a suffix of a path in\n"
+    "the compile command line database.\n"
+    "\n"
+    "For example, to use clang-check on all files in a subtree of the source\n"
+    "tree, use:\n"
+    "\n"
+    "  find path/in/subtree -name '*.cpp'|xargs clang-check -p path/to/source\n"
+    "\n"
+    "or using auto-location of compile_commands.json:\n"
+    "\n"
+    "  find path/in/subtree -name '*.cpp'|xargs clang-check\n"
+    "\n"
+);
+
 int main(int argc, const char **argv) {
   llvm::OwningPtr<CompilationDatabase> Compilations(
     FixedCompilationDatabase::loadFromCommandLine(argc, argv));
   cl::ParseCommandLineOptions(argc, argv);
   if (!Compilations) {
     std::string ErrorMessage;
     if (!BuildPath.empty()) {
       Compilations.reset(