From: Ted Kremenek Date: Mon, 31 Jan 2011 20:45:38 +0000 (+0000) Subject: Document that set-xcode-analyzer should typically be run using sudo. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=4c551b63c42d0b771a13252eab0e85947b1ee54c;p=clang Document that set-xcode-analyzer should typically be run using sudo. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@124602 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/www/analyzer/xcode.html b/www/analyzer/xcode.html index 474156e574..51c5a56163 100644 --- a/www/analyzer/xcode.html +++ b/www/analyzer/xcode.html @@ -102,6 +102,14 @@ specify for static analysis. Within this model it provides you two basic modes:
  • --use-checker-build: Switch Xcode to using the clang provided by the specified analyzer build.
  • +

    Things to keep in mind

    + + +

    Examples

    Example 1: Telling Xcode to use checker-235 for Build and Analyze:

    @@ -110,7 +118,7 @@ specify for static analysis. Within this model it provides you two basic modes: $ pwd /tmp $ tar xjf checker-235.tar.bz2 -$ checker-235/set-xcode-analyzer --use-checker-build=/tmp/checker-235 +$ sudo checker-235/set-xcode-analyzer --use-checker-build=/tmp/checker-235

    Note that you typically won't install an analyzer build in /tmp, but @@ -120,13 +128,13 @@ path to an untarred analyzer build.

    Example 2: Telling Xcode to use a very specific version of clang:

    -$ set-xcode-analyzer --use-checker-build=~/mycrazyclangbuild/bin/clang
    +$ sudo set-xcode-analyzer --use-checker-build=~/mycrazyclangbuild/bin/clang
     

    Example 3: Resetting Xcode to its default behavior:

    -$ set-xcode-analyzer --use-xcode-clang
    +$ sudo set-xcode-analyzer --use-xcode-clang