mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2024-12-04 16:11:28 +00:00
Code Issues Projects Releases Packages Wiki Activity
subsurface/packaging/macosx/Subsurface-mobile.xcodeproj/xcshareddata/xcschemes/Subsurface-mobile.xcscheme

81 lines
2.9 KiB
Text
Raw Normal View History

mac: create Xcode project for mobile (on a desktop) Create Xcode project, allowing easy editing of all sources. the project uses "make mobile" and "make desktop" to generate the project, so all CMake changes are automatically updated the project uses folder references, so adding/removing a source is automatically updated The project expect build-mobile and build to be existing as well as external libraries, so after cloning do a normal build before using the project. Signed-off-by: Jan Iversen <jani@apache.org>
2018-09-17 10:08:15 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<Scheme
LastUpgradeVersion = "0940"
mac: correct Xcode project schemes Update schemes to only allow run. Now it is possible to build/run/debug mobileExecutable as well as desktop from within Xcode. Xcode demands that the path to the debug executable it not relative, this of course gives a portability problem. The path selected are ~/develop/src/subsurface/build.... to at least give it a shine of not being fixed. Signed-off-by: Jan Iversen <jani@apache.org>
2019-12-10 10:59:07 +00:00
version = "1.3">
mac: create Xcode project for mobile (on a desktop) Create Xcode project, allowing easy editing of all sources. the project uses "make mobile" and "make desktop" to generate the project, so all CMake changes are automatically updated the project uses folder references, so adding/removing a source is automatically updated The project expect build-mobile and build to be existing as well as external libraries, so after cloning do a normal build before using the project. Signed-off-by: Jan Iversen <jani@apache.org>
2018-09-17 10:08:15 +00:00
<BuildAction
parallelizeBuildables = "YES"
buildImplicitDependencies = "YES">
<BuildActionEntries>
<BuildActionEntry
mac: correct Xcode project schemes Update schemes to only allow run. Now it is possible to build/run/debug mobileExecutable as well as desktop from within Xcode. Xcode demands that the path to the debug executable it not relative, this of course gives a portability problem. The path selected are ~/develop/src/subsurface/build.... to at least give it a shine of not being fixed. Signed-off-by: Jan Iversen <jani@apache.org>
2019-12-10 10:59:07 +00:00
buildForTesting = "NO"
mac: create Xcode project for mobile (on a desktop) Create Xcode project, allowing easy editing of all sources. the project uses "make mobile" and "make desktop" to generate the project, so all CMake changes are automatically updated the project uses folder references, so adding/removing a source is automatically updated The project expect build-mobile and build to be existing as well as external libraries, so after cloning do a normal build before using the project. Signed-off-by: Jan Iversen <jani@apache.org>
2018-09-17 10:08:15 +00:00
buildForRunning = "YES"
mac: correct Xcode project schemes Update schemes to only allow run. Now it is possible to build/run/debug mobileExecutable as well as desktop from within Xcode. Xcode demands that the path to the debug executable it not relative, this of course gives a portability problem. The path selected are ~/develop/src/subsurface/build.... to at least give it a shine of not being fixed. Signed-off-by: Jan Iversen <jani@apache.org>
2019-12-10 10:59:07 +00:00
buildForProfiling = "NO"
buildForArchiving = "NO"
buildForAnalyzing = "NO">
mac: create Xcode project for mobile (on a desktop) Create Xcode project, allowing easy editing of all sources. the project uses "make mobile" and "make desktop" to generate the project, so all CMake changes are automatically updated the project uses folder references, so adding/removing a source is automatically updated The project expect build-mobile and build to be existing as well as external libraries, so after cloning do a normal build before using the project. Signed-off-by: Jan Iversen <jani@apache.org>
2018-09-17 10:08:15 +00:00
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "39C475D9214FAF2B00CBA20C"
BuildableName = "Subsurface-mobile"
BlueprintName = "Subsurface-mobile"
ReferencedContainer = "container:Subsurface-mobile.xcodeproj">
</BuildableReference>
</BuildActionEntry>
</BuildActionEntries>
</BuildAction>
<TestAction
buildConfiguration = "Debug"
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
shouldUseLaunchSchemeArgsEnv = "YES">
<Testables>
</Testables>
</TestAction>
<LaunchAction
buildConfiguration = "Debug"
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
launchStyle = "0"
useCustomWorkingDirectory = "NO"
ignoresPersistentStateOnLaunch = "NO"
debugDocumentVersioning = "YES"
debugServiceExtension = "internal"
allowLocationSimulation = "YES">
<PathRunnable
runnableDebuggingMode = "0"
mac: correct Xcode project schemes Update schemes to only allow run. Now it is possible to build/run/debug mobileExecutable as well as desktop from within Xcode. Xcode demands that the path to the debug executable it not relative, this of course gives a portability problem. The path selected are ~/develop/src/subsurface/build.... to at least give it a shine of not being fixed. Signed-off-by: Jan Iversen <jani@apache.org>
2019-12-10 10:59:07 +00:00
FilePath = "~/develop/src/subsurface/build-mobile/Subsurface-mobile.app">
mac: create Xcode project for mobile (on a desktop) Create Xcode project, allowing easy editing of all sources. the project uses "make mobile" and "make desktop" to generate the project, so all CMake changes are automatically updated the project uses folder references, so adding/removing a source is automatically updated The project expect build-mobile and build to be existing as well as external libraries, so after cloning do a normal build before using the project. Signed-off-by: Jan Iversen <jani@apache.org>
2018-09-17 10:08:15 +00:00
</PathRunnable>
<MacroExpansion>
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "39C475D9214FAF2B00CBA20C"
BuildableName = "Subsurface-mobile"
BlueprintName = "Subsurface-mobile"
ReferencedContainer = "container:Subsurface-mobile.xcodeproj">
</BuildableReference>
</MacroExpansion>
</LaunchAction>
<ProfileAction
buildConfiguration = "Release"
shouldUseLaunchSchemeArgsEnv = "YES"
savedToolIdentifier = ""
useCustomWorkingDirectory = "NO"
debugDocumentVersioning = "YES">
<MacroExpansion>
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "39C475D9214FAF2B00CBA20C"
BuildableName = "Subsurface-mobile"
BlueprintName = "Subsurface-mobile"
ReferencedContainer = "container:Subsurface-mobile.xcodeproj">
</BuildableReference>
</MacroExpansion>
</ProfileAction>
<AnalyzeAction
buildConfiguration = "Debug">
</AnalyzeAction>
<ArchiveAction
buildConfiguration = "Release"
revealArchiveInOrganizer = "YES">
</ArchiveAction>
</Scheme>
Reference in a new issue Copy permalink