Home
last modified time | relevance | path

Searched refs:framework (Results 1 – 25 of 212) sorted by relevance

123456789

/openbsd-src/gnu/llvm/lldb/cmake/modules/
H A DLLDBFramework.cmake1 message(STATUS "LLDB.framework: build path is '${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}'")
2 message(STATUS "LLDB.framework: install path is '${LLDB_FRAMEWORK_INSTALL_DIR}'")
3 message(STATUS "LLDB.framework: resources subdirectory is 'Versions/${LLDB_FRAMEWORK_VERSION}/Resou…
5 # Configure liblldb as a framework bundle
18 MACOSX_FRAMEWORK_IDENTIFIER com.apple.LLDB.framework
28 # Note: iOS doesn't specify version, as the framework layout is flat.
32 MACOSX_FRAMEWORK_IDENTIFIER com.apple.LLDB.framework
40 # generators. Overwrite to account for special framework output directory.
48 # Affects the layout of the framework bundle (default is macOS layout).
60 # On iOS, there is no versioned framework layout. Skip this symlink step.
[all …]
H A DFindPythonAndSwig.cmake13 # The install name for the Python 3 framework in Xcode is relative to
14 # the framework's location and not the dylib itself.
16 # @rpath/Python3.framework/Versions/3.x/Python3
18 # This means that we need to compute the path to the Python3.framework
21 # The check below shouldn't match Homebrew's Python framework as it is
22 # called Python.framework instead of Python3.framework.
23 if (APPLE AND Python3_LIBRARIES MATCHES "Python3.framework")
24 string(FIND "${Python3_LIBRARIES}" "Python3.framework" python_framework_pos)
H A DLLDBConfig.cmake69 option(LLDB_BUILD_FRAMEWORK "Build LLDB.framework (Darwin only)" OFF)
90 message(FATAL_ERROR "LLDB.framework can only be generated when targeting Apple platforms")
93 set(LLDB_FRAMEWORK_VERSION A CACHE STRING "LLDB.framework version (default is A)")
94 set(LLDB_FRAMEWORK_BUILD_DIR bin CACHE STRING "Output directory for LLDB.framework")
95 …(LLDB_FRAMEWORK_INSTALL_DIR Library/Frameworks CACHE STRING "Install directory for LLDB.framework")
100 # Essentially, emit the framework's dSYM outside of the framework directory.
105 # copied into LLDB.framework in the build tree.
113 # the framework target exists and that's the only place where this is
115 add_custom_target(lldb-framework-cleanup
H A DAddLLDB.cmake220 set(subdir LLDB.framework/Versions/${LLDB_FRAMEWORK_VERSION}/Resources)
233 # The test suite relies on finding LLDB.framework binary resources in the
237 # Destination for the copy in the build-tree. While the framework target may
247 # Create a custom target to remove the copy again from LLDB.framework in the
253 COMMENT "Removing ${name} from LLDB.framework")
254 add_dependencies(lldb-framework-cleanup
274 set(bundle_subdir ${output_name}.framework/Versions/${LLDB_FRAMEWORK_VERSION}/)
294 set(dsym_name ${output_name}.framework.dSYM)
339 set(subpath "LLDB.framework/Resources/debugserver")
/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/clang-tools-extra/clangd/xpc/framework/
H A DBUILD.gn4 # create_clangd_xpc_framework() in cmake creates both the ClangdXPC.framework
7 # to have one create_bundle() each for both ClangdXPC.framework and clangd.xpc.
37 # Since this target only exists to be copied into ClangdXPC.framework,
50 # ClangdXPC.framework
81 # .framework bundle symlinks:
96 output = "$root_out_dir/lib/ClangdXPC.framework/$target"
101 output = "$root_out_dir/lib/ClangdXPC.framework/Versions/Current"
104 create_bundle("ClangdXPC.framework") {
105 # .framework directory structure.
/openbsd-src/gnu/llvm/lldb/tools/debugserver/debugserver.xcodeproj/
H A Dproject.pbxproj46 …1 /* CoreFoundation.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 26ACA3340D3E956300…
80 …2 /* CoreFoundation.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 26ACA3340D3E956300…
81 …0570CDC /* Foundation.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 49D404611E39260F…
85 …0218D5E /* Foundation.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 49D404611E39260F…
126 …framework */ = {isa = PBXFileReference; lastKnownFileType = wrapper.framework; name = CoreFoundati…
172 …framework */ = {isa = PBXFileReference; lastKnownFileType = wrapper.framework; name = Foundation.f…
195 49D404621E39260F00570CDC /* Foundation.framework in Frameworks */,
196 26CE05CF115C36F70022F371 /* CoreFoundation.framework in Frameworks */,
204 456F676B1AD46CE9002850C2 /* CoreFoundation.framework in Frameworks */,
205 AFA3FCA11E39984900218D5E /* Foundation.framework in Frameworks */,
[all …]
/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/lldb/source/Host/macosx/objcxx/
H A DBUILD.gn17 "Foundation.framework",
18 "CoreServices.framework",
19 "Security.framework",
/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/clang-tools-extra/clangd/xpc/test-client/
H A DBUILD.gn6 "//clang-tools-extra/clangd/xpc/framework:ClangdXPC.framework",
/openbsd-src/gnu/usr.bin/gcc/gcc/testsuite/
H A DREADME.gcc20 Various messages are stored in gcc.log by the testing framework and we
21 try to augment them with some of our own. The format of the framework
84 If a test does not fit into the torture framework, use the dg framework.
/openbsd-src/regress/usr.sbin/ospfd/
H A DREADME1 This is a test framework for the ospfd routing daemon. For each
9 plan is to extend the framework for the other OSPF packet types and
/openbsd-src/gnu/llvm/lldb/tools/driver/
H A DCMakeLists.txt34 # In the build-tree, we know the exact path to the framework directory.
35 # The installed framework can be in different locations.
/openbsd-src/gnu/llvm/lldb/tools/lldb-vscode/
H A DCMakeLists.txt50 # In the build-tree, we know the exact path to the framework directory.
51 # The installed framework can be in different locations.
/openbsd-src/gnu/llvm/lldb/bindings/lua/
H A DCMakeLists.txt34 set(LIBLLDB_SYMLINK_DEST "${LLDB_FRAMEWORK_ABSOLUTE_BUILD_DIR}/LLDB.framework/LLDB")
57 set(LLDB_LUA_INSTALL_PATH ${LLDB_FRAMEWORK_INSTALL_DIR}/LLDB.framework/Resources/Python)
/openbsd-src/gnu/llvm/lldb/source/API/
H A DCMakeLists.txt198 # When building the LLDB framework, this isn't necessary as there we copy everything we need into
199 # the framework (including the Clang resourece directory).
217 lldb-framework-cleanup)
222 lldb-framework-cleanup)
/openbsd-src/gnu/llvm/lldb/examples/test/tmp/
H A Dlldb_log-x86_64-clang-TestBreakpointCommand.BreakpointCommandTestCase.test_with_dsym.txt1 com.apple.main-thread /Volumes/data/lldb/svn/ToT/build/Debug/LLDB.framework/Versions/A/Resources/de…
2 argv[0]="/Volumes/data/lldb/svn/ToT/build/Debug/LLDB.framework/Versions/A/Resources/debugserver"
9 …h_info) => pid=55237, path='/Volumes/data/lldb/svn/ToT/build/Debug/LLDB.framework/Versions/A/Resou…
H A Dlldb_log-x86_64-clang-TestBreakpointCommand.BreakpointCommandTestCase.test_with_dwarf.txt1 com.apple.main-thread /Volumes/data/lldb/svn/ToT/build/Debug/LLDB.framework/Versions/A/Resources/de…
2 argv[0]="/Volumes/data/lldb/svn/ToT/build/Debug/LLDB.framework/Versions/A/Resources/debugserver"
9 …h_info) => pid=55287, path='/Volumes/data/lldb/svn/ToT/build/Debug/LLDB.framework/Versions/A/Resou…
/openbsd-src/gnu/llvm/lldb/docs/use/
H A Dsymbols.rst11 The DebugSymbols.framework framework helps locate dSYM files when given a UUID.
20 DebugSymbols.framework also has global defaults that can be modified to allow
21 all of the debug tools (lldb, gdb, sample, CoreSymbolication.framework) to
22 easily find important debug symbols. The domain for the DebugSymbols.framework
41 DebugSymbols.framework is asked to lookup a dSYM file, it will first
266 contains the DWARF. Whenever DebugSymbols.framework is asked to lookup a dSYM
305 Then the defaults for DebugSymbols.framework will entail enabling your shell
316 Hopefully this helps explain how DebugSymbols.framework can help any company
/openbsd-src/gnu/llvm/lldb/examples/functions/
H A DMakefile12 LD_EXTRAS ?= -framework LLDB -Wl,-rpath,"$(LLDB_BUILD_DIR)"
/openbsd-src/gnu/llvm/lldb/examples/lookup/
H A DMakefile11 LD_EXTRAS ?= -framework LLDB -Wl,-rpath,"$(LLDB_BUILD_DIR)"
/openbsd-src/gnu/llvm/lldb/packages/Python/lldbsuite/test/make/
H A DMakefile.rules300 DYLIB_NAME ?= $(FRAMEWORK).framework/Versions/A/$(FRAMEWORK)
301 DYLIB_FILENAME ?= $(FRAMEWORK).framework/Versions/A/$(FRAMEWORK)
307 DYLIB_INSTALL_NAME ?= @executable_path/$(FRAMEWORK).framework/Versions/A/$(FRAMEWORK)
/openbsd-src/gnu/usr.bin/cvs/
H A DTESTS90 The sanity.sh test framework combines stdout and stderr and for tests
104 framework. A quick look at sanity.sh should make it clear that there
106 replacement framework would achieve the following:
115 and install the framework, the less people will run the tests.
144 * Write our own small framework directly in tcl and distribute with
/openbsd-src/gnu/llvm/clang/docs/
H A DModules.rst55 library/framework developers even use ``__underscored`` names
464 ``conflict`` ``framework`` ``requires``
493 …``explicit``:sub:`opt` ``framework``:sub:`opt` ``module`` *module-id* *attributes*:sub:`opt` '{' *…
500 …framework`` qualifier specifies that this module corresponds to a Darwin-style framework. A Darwin…
504 Name.framework/
505 Modules/module.modulemap Module map for the framework
506 Headers/ Subdirectory containing framework headers
507 PrivateHeaders/ Subdirectory containing framework private headers
510 Name Symbolic link to the shared library for the framework
719 …framework`` specifier, the enclosing module shall have a ``framework`` specifier; the submodule's …
[all …]
H A DAPINotes.rst26 …vm/llvm-project/blob/main/clang/test/APINotes/Inputs/Frameworks/SomeKit.framework/Headers/SomeKit.…
28 notes for a hypothetical "SomeKit" framework.
38 directory as the corresponding module map; for framework modules, they should
40 module map for a private top-level framework module should be placed in the
75 The name of the module (the framework name, for frameworks). Note that this
/openbsd-src/gnu/llvm/llvm/tools/dsymutil/
H A DCMakeLists.txt41 target_link_libraries(dsymutil PRIVATE "-framework CoreFoundation")
/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/llvm/tools/dsymutil/
H A DBUILD.gn35 frameworks = [ "CoreFoundation.framework" ]

123456789