[LLVMbugs] [Bug 11660] New: set-xcode-analyzer doesn't work with custom Xcode install locations

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Tue Dec 27 12:50:26 PST 2011


             Bug #: 11660
           Summary: set-xcode-analyzer doesn't work with custom Xcode
                    install locations
           Product: clang
           Version: 3.0
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: Static Analyzer
        AssignedTo: kremenek at apple.com
        ReportedBy: e28eta at yahoo.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

This is with checker-258.

The set-xcode-analyzer script has a hard-coded assumption that Xcode is located
at /Developer

This is not true on my system, and when I run it I see:
    $ ./set-xcode-analyzer --use-checker-build=/checker-258
    (+) Using Clang bundled with checker build: /checker-258

It looks like it succeeded, but it never found the Clang LLVM xcspec, and so
never made a change. When I run analyze, it still uses the clang binary bundled
with Xcode.

I think it should be using `xcode-select -print-path` to find the path to the
current Developer directory. According to the man page for xcode-select, "This
is a recommended way for scripts and other tools to locate the current Xcode

I think it should also print some sort of confirmation/error based on whether
it actually changes Xcode to use the new/changed checker.

Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the llvm-bugs mailing list