/llvm-project/clang/docs/analyzer/user-docs/ |
H A D | UsingWithXCode.rst | 1 Running the analyzer within Xcode 7 Since Xcode 3.2, users have been able to run the static analyzer `directly within Xcode <https://de… 9 It integrates directly with the Xcode build system and presents analysis results directly within Xc… 11 Can I use the open source analyzer builds with Xcode? 18 **Viewing static analyzer results in Xcode** 23 - **Integrated workflow:** Results are integrated within Xcode. There is no experience of using a s… 24 - **Transparency:** Works effortlessly with Xcode projects (including iPhone projects). 25 - **Cons:** Doesn't work well with non-Xcode projects. For those, consider :doc:`CommandLineUsage`. 30 Xcode is available as a free download from Apple on the `Mac App Store <https://itunes.apple.com/us… 32 Using open source analyzer builds with Xcode [all …]
|
H A D | CommandLineUsage.rst | 115 - **--use-analyzer Xcode** *(or)* **--use-analyzer [path to clang]**: ``scan-build`` uses the 'clang' executable relative to itself for static analysis. One can override this behavior with this option by using the 'clang' packaged with Xcode (on OS X) or from the PATH. 160 Conceptually Xcode projects for iPhone applications are nearly the same as their cousins for desktop applications. **scan-build** can analyze these projects as well, but users often encounter problems with just building their iPhone projects from the command line because there are a few extra preparative steps they need to take (e.g., setup code signing). 165 The absolute easiest way to analyze iPhone projects is to use the `Analyze feature in Xcode <https://developer.apple.com/library/ios/recipes/xcode_help-source_editor/chapters/Analyze.html#//apple_ref/doc/uid/TP40009975-CH4-SW1>`_ (which is based on the static analyzer). There a user can analyze their project right from a menu without most of the setup described later. 167 `Instructions are available <../xcode.html>`_ on this website on how to use open source builds of the analyzer as a replacement for the one bundled with Xcode. 174 - Analyze your project in the ``Debug`` configuration, either by setting this as your configuration with Xcode or by passing ``-configuration Debug`` to ``xcodebuild``. 175 - Analyze your project using the ``Simulator`` as your base SDK. It is possible to analyze your code when targeting the device, but this is much easier to do when using Xcode's *Build and Analyze* feature. 189 Recall that **scan-build** analyzes your project by using a compiler to compile the project and ``clang`` to analyze your project. The script uses simple heuristics to determine which compiler should be used (it defaults to ``clang`` on Darwin and ``gcc`` on other platforms). When analyzing iPhone projects, **scan-build** may pick the wrong compiler than the one Xcode would use to build your project. For example, this could be because multiple versions of a compiler may be installed on your system, especially if you are developing for the iPhone. 195 If you aren't certain which compiler Xcode uses to build your project, try just running ``xcodebuild`` (without **scan-build**). You should see the full path to the compiler that Xcode i [all...] |
/llvm-project/llvm/tools/xcode-toolchain/ |
H A D | CMakeLists.txt | 5 # developers to work without disabling SIP, this file can generate an Xcode 6 # toolchain. Xcode toolchains are a mostly-undocumented feature that allows 13 # To make this work with Xcode 7.1 and later you can install the toolchain this 37 option(LLVM_CREATE_XCODE_TOOLCHAIN "Create a target to install LLVM into an Xcode toolchain" Off) 43 # XCODE_VERSION is set by CMake when using the Xcode generator, otherwise we need 52 string(REGEX MATCH "Xcode ([0-9][0-9]?([.][0-9])+)" version_match ${xcodebuild_version}) 54 message(STATUS "Identified Xcode Version: ${CMAKE_MATCH_1}") 57 # If detecting Xcode version failed, set a crazy high version so we default 60 …message(WARNING "Failed to detect the version of an installed copy of Xcode, falling back to highe… 64 # Xcode 8 requires CompatibilityVersion 2 [all …]
|
/llvm-project/llvm/test/tools/dsymutil/ARM/ |
H A D | dwarf5-str-offsets-base-strx.test | 95 …_strx] (indexed (00000002) string = "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Content… 120 …_strx] (indexed (00000002) string = "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Content… 144 …_strx] (indexed (00000002) string = "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Content… 167 CHECK-NEXT: 0x00000036: "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Contents/Developer/P… 186 GLOBAL-NEXT: 0x00000010: 00000036 "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Contents/D… 205 LOCAL-NEXT: 0x00000010: 00000036 "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Contents/De… 215 LOCAL-NEXT: 0x0000003c: 00000036 "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Contents/De… 225 LOCAL-NEXT: 0x00000068: 00000036 "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Contents/De… 240 …_strx] (indexed (00000002) string = "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Content… 280 …_strx] (indexed (00000002) string = "/Users/shubham/apple-internal/Xcode-Rainbow/Xcode.app/Content… [all …]
|
H A D | dwarf5-dwarf4-combination-macho.test | 64 CHECK: DW_AT_LLVM_sysroot [DW_FORM_strx] (indexed (00000002) string = "/Applications/Xcode.app/Cont… 84 CHECK: DW_AT_LLVM_sysroot [DW_FORM_strp] ( .debug_str[0x00000039] = "/Applications/Xcode.app/Conten… 180 CHECK-NEXT: 0x00000039: "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Devel… 211 CHECK-NEXT: 0x00000010: 00000039 "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platf…
|
/llvm-project/llvm/utils/gn/build/ |
H A D | mac_sdk.gni | 11 # Set to true if you don't have Xcode installed, but do have the commandline 19 # long and almost everyone has Xcode installed. So require that people who 27 mac_sdk_path = "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk" 28 ios_sdk_path = "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk" 29 iossim_sdk_path = "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk"
|
/llvm-project/lldb/cmake/caches/ |
H A D | Apple-lldb-Xcode.cmake | 3 set(CMAKE_GENERATOR Xcode CACHE STRING "") 9 # Apparently, module-enabled builds clash with Xcode's analysis. 13 # build with Xcode and didn't use this cache.
|
H A D | Apple-lldb-macOS.cmake | 11 set(CMAKE_INSTALL_PREFIX /Applications/Xcode.app/Contents/Developer/usr CACHE STRING "") 15 set(LLDB_FRAMEWORK_INSTALL_DIR /Applications/Xcode.app/Contents/SharedFrameworks CACHE STRING "")
|
/llvm-project/lldb/docs/use/ |
H A D | links.rst | 36 `Advanced Debugging with Xcode and LLDB (2018)`_ 40 Xcode debugging workflows. Learn how to take advantage of LLDB and 42 Xcode’s view debugging tools to solve UI issues in your app more 70 .. _Advanced Debugging with Xcode and LLDB (2018): https://developer.apple.com/videos/play/wwdc2018/412/
|
/llvm-project/lldb/docs/resources/ |
H A D | caveats.rst | 33 LLDB in Xcode on macOS 36 Users of lldb in Xcode on macOS commonly run into these issues when they 42 To be sure you use the Python that matches with the lldb in Xcode use ``xcrun`` 59 system rather than Xcode, you can still use ``xcrun`` to launch the system
|
/llvm-project/clang/cmake/caches/ |
H A D | Apple-stage2.cmake | 27 set(LLVM_CREATE_XCODE_TOOLCHAIN ON CACHE BOOL "Generate targets to create and install an Xcode comp… 43 # Generating Xcode toolchains is useful for developers wanting to build and use
|
H A D | Apple-stage1.cmake | 7 …set(CMAKE_INSTALL_PREFIX /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.toolch…
|
/llvm-project/lldb/examples/functions/ |
H A D | Makefile | 11 LLDB_BUILD_DIR ?= /Applications/Xcode.app/Contents/SharedFrameworks
|
/llvm-project/lldb/examples/lookup/ |
H A D | Makefile | 10 LLDB_BUILD_DIR ?= /Applications/Xcode.app/Contents/SharedFrameworks
|
/llvm-project/llvm/utils/lit/tests/Inputs/ |
H A D | lit.cfg | 3 # will fail in a multi-config environment such as Visual Studio or Xcode).
|
/llvm-project/lldb/test/Shell/ScriptInterpreter/Python/Crashlog/ |
H A D | parser_text.test | 10 …38.2 - 1000.11.38.2) <96E36F5C-1A83-39A1-8713-5FDD9701C3F1> /Applications/Xcode.app/Contents/Share… 15 # CHECK: /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/LLDB
|
/llvm-project/compiler-rt/cmake/caches/ |
H A D | Apple.cmake | 2 # This configuration matches Apple uses when shipping Xcode releases.
|
/llvm-project/lldb/ |
H A D | .gitignore | 47 # We should ignore Xcode-style embedding of llvm/ at lldb root dir.
|
/llvm-project/mlir/tools/mlir-shlib/ |
H A D | CMakeLists.txt | 18 # Xcode doesn't support object libraries, so we have to trick it into
|
/llvm-project/llvm/test/DebugInfo/X86/ |
H A D | test-fexceptions-debug-frame.ll | 34 …, splitDebugInlining: false, nameTableKind: None, sysroot: "/Applications/Xcode.app", sdk: "MacOSX…
|
H A D | test-fno-exceptions-debug-frame.ll | 35 …, splitDebugInlining: false, nameTableKind: None, sysroot: "/Applications/Xcode.app", sdk: "MacOSX…
|
/llvm-project/llvm/test/DebugInfo/AArch64/ |
H A D | test-fno-exceptions-debug-frame.ll | 32 …, splitDebugInlining: false, nameTableKind: None, sysroot: "/Applications/Xcode.app", sdk: "MacOSX…
|
H A D | test-fexceptions-debug-frame.ll | 35 …, splitDebugInlining: false, nameTableKind: None, sysroot: "/Applications/Xcode.app", sdk: "MacOSX…
|
/llvm-project/clang/www/analyzer/ |
H A D | menu.html.incl | 20 <li><a href="/xcode.html">Using within Xcode</a></li>
|
/llvm-project/lldb/cmake/modules/ |
H A D | LLDBConfig.cmake | 116 if(APPLE AND CMAKE_GENERATOR STREQUAL Xcode) 119 "When building with Xcode, we recommend using the corresponding cache script. " 121 " -C ${CMAKE_SOURCE_DIR}/cmake/caches/Apple-lldb-Xcode.cmake\n"
|