problems with Perforce and Xcode 3.0
problems with Perforce and Xcode 3.0
- Subject: problems with Perforce and Xcode 3.0
- From: Eric Johnson <email@hidden>
- Date: Wed, 30 Apr 2008 16:01:24 -0700
Hi All,
I have been having trouble getting Perforce and Xcode 3.0 to
work together. I'm wondering if anyone else on the list has seen
these problems and maybe have solutions or workarounds.
1) With SCM Repository set to "None" ( in Project's general settings),
if I check a file out using the Perforce client and then attempt to
modify the file, I get the "File is Read Only" dialog from Xcode. If
I press the "Allow Editing" button, I can continue. Xcode does not
seem to be aware that the file's permissions have changed to allow
writing. (Seems like an Xcode bug). Additional notes: the file is
not "locked".
2) (More serious issue) Executing SCM commands from within Xcode
seems to be completely broken. For example, checking out files does
not work. Selecting a file in the project and then going to the SCM
menu, the "Get SCM Info" choice is grayed out. The SCM Repository
setting for the project is set to Perforce and the SCM preferences for
Xcode show that the Perforce repository has been "authenticated".
Additional info:
* These problems occur with C and C++ projects
* P4V Version: MACOSX104X86/2007.3/149519
* P4 Command line client: MACOSX104X86/2007.3/143793
* Power Mac
* 2 x 2.66 GHz Dual-Core Intel Xeon
* 2 GB 667 MHz DDR2 FB-DIMM
* Mac OSX 10.5.2
Thanks,
Eric
_______________________________________________
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