maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/lldb.xcodeproj/xcshareddata/xcschemes/Run Testsuite.xcscheme

124 lines
4.3 KiB
Plaintext
Raw Normal View History

This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
<?xml version="1.0" encoding="UTF-8"?>
<Scheme
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
LastUpgradeVersion = "0720"
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
version = "1.3">
<BuildAction
parallelizeBuildables = "YES"
buildImplicitDependencies = "YES">
<BuildActionEntries>
<BuildActionEntry
buildForTesting = "YES"
buildForRunning = "YES"
buildForProfiling = "YES"
buildForArchiving = "YES"
buildForAnalyzing = "YES">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "26F5C26910F3D9A4009D5894"
BuildableName = "lldb"
BlueprintName = "lldb-tool"
ReferencedContainer = "container:lldb.xcodeproj">
</BuildableReference>
</BuildActionEntry>
</BuildActionEntries>
</BuildAction>
<TestAction
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
buildConfiguration = "Debug"
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
shouldUseLaunchSchemeArgsEnv = "YES">
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
<Testables>
</Testables>
<MacroExpansion>
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "26F5C26910F3D9A4009D5894"
BuildableName = "lldb"
BlueprintName = "lldb-tool"
ReferencedContainer = "container:lldb.xcodeproj">
</BuildableReference>
</MacroExpansion>
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
<AdditionalOptions>
</AdditionalOptions>
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
</TestAction>
<LaunchAction
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
buildConfiguration = "Debug"
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
launchStyle = "0"
useCustomWorkingDirectory = "YES"
customWorkingDirectory = "$(PROJECT_DIR)/test"
ignoresPersistentStateOnLaunch = "NO"
debugDocumentVersioning = "YES"
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
debugServiceExtension = "internal"
allowLocationSimulation = "YES"
queueDebuggingEnabled = "No">
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
<PathRunnable
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
runnableDebuggingMode = "0"
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
FilePath = "/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python">
</PathRunnable>
<MacroExpansion>
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "26F5C26910F3D9A4009D5894"
BuildableName = "lldb"
BlueprintName = "lldb-tool"
ReferencedContainer = "container:lldb.xcodeproj">
</BuildableReference>
</MacroExpansion>
<CommandLineArguments>
<CommandLineArgument
argument = "dotest.py"
isEnabled = "YES">
</CommandLineArgument>
<CommandLineArgument
argument = "-t"
isEnabled = "YES">
</CommandLineArgument>
<CommandLineArgument
argument = "-v"
isEnabled = "YES">
</CommandLineArgument>
<CommandLineArgument
argument = "-A x86_64"
isEnabled = "YES">
</CommandLineArgument>
<CommandLineArgument
Huge change to clean up types. A long time ago we start with clang types that were created by the symbol files and there were many functions in lldb_private::ClangASTContext that helped. Later we create ClangASTType which contains a clang::ASTContext and an opauque QualType, but we didn't switch over to fully using it. There were a lot of places where we would pass around a raw clang_type_t and also pass along a clang::ASTContext separately. This left room for error. This checkin change all type code over to use ClangASTType everywhere and I cleaned up the interfaces quite a bit. Any code that was in ClangASTContext that was type related, was moved over into ClangASTType. All code that used these types was switched over to use all of the new goodness. llvm-svn: 186130
2013-07-12 06:46:58 +08:00
argument = "functionalities/breakpoint/breakpoint_conditions"
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
isEnabled = "YES">
</CommandLineArgument>
</CommandLineArguments>
<AdditionalOptions>
Huge change to clean up types. A long time ago we start with clang types that were created by the symbol files and there were many functions in lldb_private::ClangASTContext that helped. Later we create ClangASTType which contains a clang::ASTContext and an opauque QualType, but we didn't switch over to fully using it. There were a lot of places where we would pass around a raw clang_type_t and also pass along a clang::ASTContext separately. This left room for error. This checkin change all type code over to use ClangASTType everywhere and I cleaned up the interfaces quite a bit. Any code that was in ClangASTContext that was type related, was moved over into ClangASTType. All code that used these types was switched over to use all of the new goodness. llvm-svn: 186130
2013-07-12 06:46:58 +08:00
<AdditionalOption
key = "DYLD_INSERT_LIBRARIES"
value = "/usr/lib/libgmalloc.dylib"
isEnabled = "YES">
</AdditionalOption>
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
</AdditionalOptions>
</LaunchAction>
<ProfileAction
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
buildConfiguration = "Release"
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
shouldUseLaunchSchemeArgsEnv = "YES"
savedToolIdentifier = ""
useCustomWorkingDirectory = "NO"
debugDocumentVersioning = "YES">
Xcode suggested enabling a "no common blocks" warning (whatever that is) and wanted to clean up some duplicated entries in the project files. llvm-svn: 251586
2015-10-29 08:21:14 +08:00
<BuildableProductRunnable
runnableDebuggingMode = "0">
This is a useful scheme for running a particular testsuite case under Xcode. Just edit the run arguments to include the directory of the test you want to run, and run the scheme. llvm-svn: 180926
2013-05-03 01:04:10 +08:00
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "26F5C26910F3D9A4009D5894"
BuildableName = "lldb"
BlueprintName = "lldb-tool"
ReferencedContainer = "container:lldb.xcodeproj">
</BuildableReference>
</BuildableProductRunnable>
</ProfileAction>
<AnalyzeAction
buildConfiguration = "Debug">
</AnalyzeAction>
<ArchiveAction
buildConfiguration = "Release"
revealArchiveInOrganizer = "YES">
</ArchiveAction>
</Scheme>