I'm hoping to transition my Airplay project from Visual Studio 2010 to Xcode 4. So far, I'm not having much luck with Xcode's code sense, issue navigator and live issues features.
Code Sense: I get next to no meaningful completion suggestions
Issue Navigator: Build issues are listed in the navigator. Clicking on them takes me to the correct file, but the specific line in the file is not highlighted. If I open the build log instead and click on the issue there, then I'm taken to the correct line.
Live Issues: Absolutely nobody home there.
Before I spend time digging into these issues, I'd just like to check that these features do actually work for others (with Airplay 4.4.3) and, if so, I'd appreciate some pointers on what I may be doing wrong.
After all, I spent some time digging into these issues :-)
The first thing to say is that, judging by numerous posts on the web, Xcode 4's code sense feature seems to be temperamental at best, in marked contrast to Visual Studio's Intellisense which, most of the time, just works.
Having said that, I was able to resolve my problems by using the "recursive" option on certain header search paths. My project consists of a main Ariplay project and two sub-projects. For the main project, I keep my source files in a directory called "source" under the top level. When I double-click on my project's mkb file, the resulting Xcode project's build settings specify an include path to the top level of my Airplay project, but not to the source sub directory. Initially, I added this path manually in the build settings, but it didn't seem to make any difference to code sense. But, by opening the project's build settings in Xcode, and clicking the "Recursive" option next to the paths of my project/sub projects in the "Header Search Paths" option (I've only tried this for the Debug target), I get all the missing code sense features.
I guess I'll lose these settings any time I re-generate the project from the mkb, but I can live with that.
I have exactly the same problem with xcode 4.0.2 but it is not solved by modifying the header search paths to be recursive.
If I open the HelloWorld SDK sample in Xcode and add a compile error to the cpp file:
1. Live issues doesn't pick it up.
2. When I perform a build and select the problem in the issue navigator, the cpp file is opened but the line isn't highlighted!
This renders xcode all but useless; one of the most elementary functions of the IDE doesn't work!