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: Andrew Pontious <email@hidden>
- Date: Mon, 14 Sep 2009 16:25:34 -0700
On Sep 13, 2009, at 5:46 PM, Paul Kim wrote:
Thanks for the response. I don't think handing over this project is
feasible given the size and the fact that it is my business here.
I'm trying to isolate it so that I can provide a sample project but
without any sense as to what can be causing this, it's a bit hard.
If you could provide some guidance in this area, that would be
helpful as there are a vast number of variables in play here.
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
On Sep 13, 2009, at 7:49 PM, Andrew Pontious wrote:
On Sep 13, 2009, at 1:41 PM, Paul Kim wrote:
After upgrading to SL, it seems that code sense broke for me for a
certain projects. It doesn't seem to complete for any SDK classes.
For instance, I enter "[NSString stringWith" and there are no
completions. It seems to work fine for my own methods. Not sure if
it's related but option-double-clicking on "NSString" gives me
"Documentation not found for symbol 'NSString'".
Now, what's weird is that it only seems to affect some projects
and not others. It doesn't seem to depend on the SDK version. I
have rebuilt the code sense index. I have uninstalled and
reinstalled XCode. I deleted all the user-specific files in
the .xcodeproject file.
I'm running out of ideas here and it's making the XCode editor
only slightly more useful than TextEdit. Any insight is greatly
appreciated.
We (or at least I) don't know of any large-scale cases of code
completion failing in 3.2 when it succeeded in 3.1. Your best bet
is to file a bug with a sample project (or even your entire
project) that reproduces the issue, and document exactly what steps
fail.
-- 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
_______________________________________________
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