Hi,
I currently have an Xcode project using an external build system (make) for one of its targets. This works very well and I get the results I expect.
I also have two schemes that use this target, each with their own executable. The Makefile specifies a location for built products (not a DerivedData folder). I set my schemes to use the executables built by make and everything works perfectly (I can launch with lldb, pass arguments, set breakpoints in the source, etc.).
The problem is: I want to share my schemes (using git). And the only way to set an external executable path to an Xcode scheme is an absolute path ( http://i.imgur.com/TA43tpd.png).
This, of course, is a problem for my collaborators who don’t necessarily have the same file structure as me.
I tried editing the .xcscheme file myself, and it’s impossible to set a relative path or to use environment variables in the executable path. If my FilePath is relative or contains environment variables selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB" selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB" useCustomWorkingDirectory = "YES" customWorkingDirectory = "$(SRCROOT)/../bin/macosx/debug" buildConfiguration = "Debug" ignoresPersistentStateOnLaunch = "NO" debugDocumentVersioning = "YES" allowLocationSimulation = "YES"> FilePath = "$(SRCROOT)/../bin/macosx/debug/zv">
Xcode crashes when I load my project.
ASSERTION FAILURE in /SourceCache/DVTFrameworks/DVTFrameworks-5072/DVTFoundation/FilePaths/DVTFilePath.m:778 Details: fsrep is relative ('$(SRCROOT)/../bin/macosx/debug/zvpn') parentPath must not be nil but it is. Method: +_filePathForParent:fileSystemRepresentation:length:allowCreation:
Is there any way to set a relative path, at least relative to the project or to the custom working directory?
I’m using Xcode Version 5.1 (5B130a) and my project is Xcode 3.2-compatible.
Charlie |