Comments on: Xcode Index

By: Daniel Jalkut

Daniel Jalkut — Fri, 06 Apr 2007 23:27:18 +0000

You mean it crashes even when you rebuild it from the command line? I guess I would ask on the xcode-users mailing list and see if any of the Apple xcode team has a suggestion.

By: CrossPlatformAppDev

CrossPlatformAppDev — Fri, 06 Apr 2007 22:37:20 +0000

What can I do if xcode crashes when I use the gui to rebuild my index? I have tried xcodeindex from the command line but still no luck.

I went far enough to look at the stats options and the dump option but both of these react as if there is no index at all. Any Suggestions?

By: Conor

Conor — Sat, 27 Jan 2007 15:26:00 +0000

I had such high hopes for the class model, I was hoping that be exactly what it would do. At least, thanks to you, I now know the solution.

By: Daniel Jalkut

Daniel Jalkut — Fri, 26 Jan 2007 14:25:29 +0000

Conor: well, it’s always something I stumble upon for a reason. In this case I was in fact motivated after being disappointed by the Xcode Class Model :) Unless somebody knows otherwise, the Class Model in Xcode only shows inheritance relationships, not instance variable dependencies.

I thought I would be able to work around that by using Xcode’s scripting interface to the “model document.” So close, yet so far! I was able able to ask for a list of all the classes in the model, and even ask for all the variables of the classes. But unfortunately again the variables are not tagged with any information about what class they point to (even though this information is available through the UI in the class model, as a list).

By: Conor

Conor — Fri, 26 Jan 2007 08:56:18 +0000

How do you stumble across these insights? The design class model feature in Xcode is often overlooked, I myself haven’t had time to delve into it properly. But I do believe that as long as your instances have class declarations it will create connection. J o a r is on my list of the few people whose post I read on the cocoa list no matter what they are about as they are always insightful. I am going to bookmark this page and come back and play with my index later, as right now I have an update to concentrate on. :)

By: charles

charles — Fri, 26 Jan 2007 00:02:41 +0000

Daniel: I think this is actually j o a r, not Joar ;-)

and I just want to say thanks too!! (to both of you…)

By: Daniel Jalkut

Daniel Jalkut — Thu, 25 Jan 2007 21:57:39 +0000

Great tips, Joar. I hadn’t thought about the shared build-folder problem but now it makes perfect sense!

By: j o a r

j o a r — Thu, 25 Jan 2007 21:33:08 +0000

The reason that the index sometimes contains references to the “wrong” project is that it (per default) is located in your build directory. If you’re using a shared build directory (not the default), for example because you’re using project references, and if you have multiple branches / copies of your project that all “point” to this same build directory, the index can (or, will often) end up with references to all those different projects. If the index had contained project-relative source file references this would still not be a problem, but since they’re absolute you get the observed behaviour.

A workaround is to use the XCCodeSenseIndexBasePath preference key to instruct Xcode to store the index in the project directory. See: “Xcode > Help > Show Expert Preferences Notes” for more information about this preference key.