Re: Project as aggregation of other projects. Indexing disabling for such project
Re: Project as aggregation of other projects. Indexing disabling for such project
- Subject: Re: Project as aggregation of other projects. Indexing disabling for such project
- From: Joar Wingfors <email@hidden>
- Date: Sun, 25 Dec 2011 23:05:59 -0800
Hello again Ruslan,
On 3 dec 2011, at 01:15, Ruslan Zasukhin wrote:
>> One way to approach your problem would be to have a workspace to hold all of
>> your projects. That's what I would do.
>
> And this is exactly what we have ...
> Just we have PROJECT from xcode v3 converted to v4.
>
> As I understand, Workspace will not differ here?
> Below you say workspace will still index own projects always ...
Correct. Regardless of if you have a workspace or a project as the top level container, the behavior will be the same.
>> Yes, everything would be indexed, but
>> that's great - One of the important improvements of Xcode 4 over Xcode 3 - as
>> it allows you to "see" the entirety of your code base, how all of your code
>> fits together.
<snip>
> When I develop, I will open project/workspace
> V4CC - Valentina for cocoa
>
> And here YES, I want indexing.
>
> But in BUILD_ALL I not going even to read code.
> I want just open this project as my build machine of release archives.
Sorry - That's not something that's supported in Xcode 4 today, and there are also no current plans to provide that level of additional control.
How much of an issue is this in practice? Indexing is paused when you're building in Xcode 4, so your build will complete just as fast in any case. With that in mind, does it matter that indexing will kick in when you're not building? Some additional electricity and disk space will end up being consumed, but that's about it, right?
Best,
Joar
_______________________________________________
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