Re: Code sense not working on 3.2
Re: Code sense not working on 3.2
- Subject: Re: Code sense not working on 3.2
- From: Paul Kim <email@hidden>
- Date: Mon, 14 Sep 2009 20:09:57 -0400
Hi Andrew,
As noted in the radar I filed, the project is a stripped out version
of an actual project with a lot of source files and targets. I only
stripped it out for the purposes of giving you a sample which
replicated the problem without giving away any of my proprietary code
(I left in some third party open source code to have some code in
there). Since the problem persisted after stripping it out, I thought
it was a suitable sample. Also, adding a target with a compile phase
doesn't change things (and I've had another developer confirm it not
working for him either).
Whether it changed or not from 3.1 to 3.2 is also a bit of a red
herring in that it's not working now with 3.2. The full project has
plenty of targets and compile phases so suggesting that as a fix
doesn't apply here (nor does it seem to work for the stripped out
sample either).
If there are any other diagnostics or things you can suggest that I
can tweak, I'd be very happy to try them out.
Thanks,
paul
On Sep 14, 2009, at 7:25 PM, Andrew Pontious wrote:
Paul --
Just to give you a quick answer here: the sample project you
provided has no source code files in its target.
This is why indexing isn't working. Xcode's index will only index
files that are part of at least some target in a project. This is
because it needs the build settings from the target to know how to
parse the file the way a compiler would.
If you add a Compile Sources build phase to the existing target, and
then add one or more files into that target, you'll get a fuller
index and at least some symbols highlighted, including all Cocoa
symbols, which will be brought in as part of the first file that
either includes Cocoa.h or has a precompiled header that includes
Cocoa.h.
This behavior didn't change from Xcode 3.1.* to 3.2, so something
else must be going on if certain projects changed their behavior
during that transition. Possibly they just got fully reindexed for
the first time in a while -- perhaps they'd never been fully
reindexed after the point you removed all Compile Sources build
phrases from your targets?
If your actual projects do have Compile Sources phases with .m files
in them, then something else is going on, but that's the reason your
sample project doesn't index, and therefore command-double-click
doesn't work.
-- Andrew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden