• 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: Michael Rice <email@hidden>
  • Date: Wed, 30 Apr 2008 18:40:01 -0500

I can tell you that I have the same issues. When using the SCM commands from within Xcode, it seems to work a little better if I'm connected on the LAN with my Perforce server, as opposed to connecting through a VPN.

I have also had some success by changing the SCM repository to "None", closing the project, reopening the project and changing the repository back to my Perforce repository.

Michael

On Apr 30, 2008, at 6: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".

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
  • Follow-Ups:
    • Re: problems with Perforce and Xcode 3.0
      • From: Chris Espinosa <email@hidden>
References: 
 >problems with Perforce and Xcode 3.0 (From: Eric Johnson <email@hidden>)

  • Prev by Date: problems with Perforce and Xcode 3.0
  • Next by Date: Re: problems with Perforce and Xcode 3.0
  • Previous by thread: problems with Perforce and Xcode 3.0
  • Next by thread: Re: problems with Perforce and Xcode 3.0
  • Index(es):
    • Date
    • Thread