In my continued quest to actually use Xcode 4 full time, I’ve run into yet another major issue: Xcode 4’s code index sometimes gets borked and syntax highlighting & code completion stop working.
In the past, this has been fixed (temporarily) by deleting the Derived Data folder in Organizer, restarting Xcode, changing the compiler from LLVM to GCC & back again or some random combination of the 3. This doesn’t always work, and today I sat down to figure out what the cause was and how to fix it.
In searching stackoverflow and the developer forums, I found that Xcode’s code index can hang on recursive and/or relative search paths.
My project utilizes 2 static libraries, so I must provide proper header search paths, otherwise the compiler doesn’t recognize any of the symbols.
So if you have a Header Search Path setting of
../lib/MyAwesomeLib/** then you might be having this problem too.
Step 1: Correcting relative paths
You might be tempted to hard code the path to the file. Don’t! This will break on somebody else’s machine, and most of the time you’re not working on this stuff alone.
You can utilize the
$(SOURCE_ROOT) build variable to construct a dynamic path relative to the Xcode project directory.
This step might be all you need, but in my case I needed to follow the next step as well…
Step 2: Remove the need for recursive searches
I have two subprojects, each of which symlink their build output to a build/current folder. This makes it easy to add a non-recursive library search path reference for similar reasons. I also want to copy headers into this folder so there’s always a deterministic location to find the headers, regardless of the platform & configuration we’re building for.
So I added a Run Script build phase to do this work for me:
1 2 3 4 5 6 7
The line is a bash for loop that copies all the header files in any subfolder & flattens it out for a single headers folder reference.
Step 3: Add the new common header search paths
In my case I exchanged a relative, recursive search path of:
to the more explicit, and more Xcode 4 friendly:
As soon as I did that, my code lit up like a Christmas tree! Symbols were recognized, code was highlighted, and best of all… code completion resumed.
Here’s to hoping the Xcode 4 continues to be improved. In the meantime, hope this fix saves you the headache I’ve been having.