[p4] Perforce and Xcode
jeffjensen at upstairstechnology.com
Sat Jul 29 10:09:17 PDT 2006
If you don't want to have files as +w, this is a perfect example of the
strategy for each user creating a numbered pending changelist with files
they "never" want to checkin. It should have a description that states that
fact, such as "local customizations - do not submit".
Use that changelist to hold files that either need writable status and may
change, and local overrides to data or code files.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
Sent: Saturday, July 29, 2006 10:51 AM
To: Janine Sisk
Cc: perforce-user at perforce.com
Subject: Re: [p4] Perforce and Xcode
You could set them up with the +w file type, but then you'll need to check
for changes that need to be checked in on your own. See Tech Note
#2 for that.
Of course another alternative is just not to put them under Perforce
control, but I'm guessing you want to share them.
Janine Sisk wrote:
> Last week it was Eclipse (and thank you very much for the help on
> that), this week it's Xcode. (I'm trying to decide which IDE I want
> to use for a new project)
> The problem I have now is that the .xcodeproj directory (and files
> within it) need to be writable when Xcode exits, which seems to
> require leaving them checked out all the time. Is there a better way?
> perforce-user mailing list - perforce-user at perforce.com
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user