Re: .#_XCSCM_ files?
Re: .#_XCSCM_ files?
- Subject: Re: .#_XCSCM_ files?
- From: Jack Repenning <email@hidden>
- Date: Tue, 4 Sep 2007 11:11:42 -0700
On Sep 2, 2007, at 1:45 PM, Tom Naughton wrote:
Since CVS doesn't have a 'revert' command, when you discard changes
on a file Xcode will:
- Rename the file to one of a prefix of .#_XCSCM_
- Update the file to the BASE revision
- If that fails, restore the backup file
- Restore any sticky tags to their previous state
- Delete the backup file
So there shouldn't be any .#_XCSCM_ files left on the disk at the
end of the operation. It sounds like you may be running into a
situation where Xcode attempted to revert some files that weren't
actually under SCM control, and failed to clean up after itself.
I'm not sure about the Xcode plug-in here, but core CVS can also
leave this litter when there are surprises during an update with -C
(which I suspect is the same thing as what Tom was calling
"revert"). I can't recall the enabling conditions, exactly, but it
was something like "if the file has been deleted in the repository,
then the working copy version is kept, with the ugly rename."
-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning
_______________________________________________
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
- Prev by Date:
Re: Distributed build problems - unknown compiler error and not building locally... On Sep 1, 2007, at 11:25 AM, Bill Bumgarner wrote: On Aug 31, 2007, at 4:12 PM, Dave Thorup wrote: On Aug 31, 2007, at 8:26 AM, Ken Worley wrote: On Aug 30, 2007, at 7:08 PM, Dave Thorup wrote: Now, for my second problem, when doing distributed builds only the remote machine is being sent files to compile, my local machine isn't compiling anything. This is verified by checking the DISTCC_HOSTS variable in the Xcode build log. If I turn off distributed builds on the remote machine then it will use the local machine to compile, but that seems to be the only way I can get compiles working on the local machine. The remote machine is a Core Duo iMac while the local Machine is a Quad Mac Pro, so naturally I'd like to be utilizing the local machine as well. From what I understand, this "problem" is actually by design. It's a real pain too if you happen to be working on the fastest mach ine available for building. I hope this will change in later versions. I haven't tried 2.5 yet. distcc requires the source files to effectively be precompiled prior to compilation. This puts a huge amount of potential I/O load and a bit of CPU load on the local system. As a result, the # of local jobs was turned down so that the machine could distribute jobs more efficiently. It sounds like it was turned down too much or a bug has come into play. Please file a bug capturing the symptoms and configuration. From what I gather in the list archives, this was an intentional change between 2.3 and 2.4. Someone complained to DTS and was told that engineering had determined that was the correct behavior. Hopefully, their notion of correct behavior has changed for 2.5...perhaps filing bugs will nudge them in the right direction. Ken -- Ken Worley Software Engineer, Tiberius, Inc.
- Next by Date:
Re: .#_XCSCM_ files?
- Previous by thread:
Re: .#_XCSCM_ files?
- Next by thread:
Re: .#_XCSCM_ files?
- Index(es):