Re: Clean all targets
Re: Clean all targets
- Subject: Re: Clean all targets
- From: "Bob Currier" <email@hidden>
- Date: Thu, 8 May 2008 14:55:24 -0700
On Tue, May 6, 2008 6:42 PM, Scott Tooker <email@hidden> wrote:
>
>On May 6, 2008, at 6:25 PM, j o a r wrote:
>
>>
>> On May 6, 2008, at 6:08 PM, Scott Tooker wrote:
>>
>>> The concern (in either situation) is that if you don't clean
>>> everything, that something bad will be left behind in the build
>>> products and intermediates that could cause problems.
>>
>>
>> For the most part though, this is something that you should have to
>> do only in special cases. The Xcode build system should track
>> dependencies and automatically update your build output as needed,
>> without requiring you to remove files manually.
>>
>> Whenever you have to clean manually, consider if Xcode could have
>> figured it out for you, and if so, please file an enhancement request:
>>
>> <http://developer.apple.com/bugreporter/>
>
>Definitely agree.
>
>In my experience, cleaning is usually in response to "my build/rebuild
>didn't work correctly, let me see if cleaning fixes it".
>
>Scott
The thing is, it very often does fix problems. But, of course, the
cleaning blows away any evidence which might help figure out *why* it
fixes it.
We find that cleaning is often necessary, and that's on different
projects, large and small, implemented by different people. We'd like to
file bugs, but suspect that more information than "cleaning made it
work" is needed.
We're suspicious of copy operations, but haven't pinned it down. It does
seem to have gotten better in Xcode 3.0, but it's still flakey.
-- Bob
_______________________________________________
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