Using Xcode with Perforce
Using Xcode with Perforce
- Subject: Using Xcode with Perforce
- From: Kaelin Colclasure <email@hidden>
- Date: Sun, 7 Dec 2003 16:45:14 -0800
I'm trying out Xcode's integration with the Perforce version control
system. After reading that Xcode is not able to initially check a
project into version control I was able to get things basically working
-- I can now open my source files for edit from within the Xcode IDE,
for instance. However, Xcode seems to be at odds with Perforce's model
that files in the workspace are read-only until explicitly opened for
editing. And there also seem to be some "issues" with the Perforce
client integration, as evidenced by messages to the console:
2003-12-07 16:12:47.917 Xcode[670] Bad Record:
TimeTracker.app - no such file(s).
2003-12-07 16:12:48.210 Xcode[670] Bad Record:
MainMenu.nib - no such file(s).
2003-12-07 16:12:48.288 Xcode[670] Bad Record:
Path '/System/Library/Frameworks/AppKit.framework' is not under
client's root '/Users/Shared'.
Path '/System/Library/Frameworks/Foundation.framework' is not under
client's root '/Users/Shared'.
Path '/System/Library/Frameworks/Cocoa.framework' is not under client's
root '/Users/Shared'.
2003-12-07 16:12:48.359 Xcode[670] Bad Record:
2003-12-07 16:12:53.703 Xcode[670] Save of project
/Users/Shared/Projects/TimeTracker/TimeTracker.xcode failed
2003-12-07 16:13:30.843 Xcode[670] Save of project
/Users/Shared/Projects/TimeTracker/TimeTracker.xcode failed
2003-12-07 16:13:49.321 Xcode[670] Save of project
/Users/Shared/Projects/TimeTracker/TimeTracker.xcode failed
The Perforce client I am using is:
$ p4 -V
Perforce - The Fast Software Configuration Management System.
Copyright 1995, 2002 Perforce Software. All rights reserved.
Rev. P4/MACOSXPPC/2003.1/48707 (2003/09/22).
I have a fair bit of experience with Perforce. I am aware that it's
possible to set up my client specification such that the files in my
workspace are always writable, just like CVS. However, isn't Xcode's
insistence on updating the project file(s) constantly likely to cause
frequent merge conflicts? What am I missing here?
If someone has a client spec and a `p4 files` listing for an Xcode
project that's checked into Perforce and is set up "properly" to keep
Xcode happy (e.g. what file type and options should be used for the
project constituent files, the nib constituent files, etc.), I would
appreciate it if they could post it here.
-- Kaelin
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.