• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: problems with Perforce and Xcode 3.0
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems with Perforce and Xcode 3.0


  • Subject: Re: problems with Perforce and Xcode 3.0
  • From: Jason Watts <email@hidden>
  • Date: Thu, 1 May 2008 11:09:55 -0700

On Apr 30, 2008, at 4:01 PM, Eric Johnson wrote:

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".

Yep, I'm having exactly these problems. I have one project that works fine and another in the same depot that has these problems. In the broken case I can get SCM info on some of the project files but not others, though all are in Perforce. The "Edit" command is enabled in the SCM menu but has no effect on these cursed files. So I have to use p4v to open the file for edit. This sets write permission on the file (as reported in the Finder info window), but Xcode does not detect that the file is now writable. Closing and reopening the project corrects Xcode's notion of the write permissions.


¿.) Jason Watts _______________________________________________
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


References: 
 >Re: problems with Perforce and Xcode 3.0 (From: Eric Johnson <email@hidden>)

  • Prev by Date: Re: IS THERE SUCH A THING AS . . . [a cheat sheet of commands, getting started in Xcode]
  • Next by Date: Re: where did the IBPalette template project go?
  • Previous by thread: Re: problems with Perforce and Xcode 3.0
  • Next by thread: IB can't save NIB file
  • Index(es):
    • Date
    • Thread