• 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
Perforce problem with XCode 3.1.1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Perforce problem with XCode 3.1.1


  • Subject: Perforce problem with XCode 3.1.1
  • From: Mike Kobb <email@hidden>
  • Date: Fri, 17 Oct 2008 23:10:13 -0700

Greetings,

I'm having a bit of a problem with the Perforce SCM integration with XCode 3.1.1, and I wonder if anybody knows what the trouble might be.

I have an XCode project file in 2.4-compatible format. It has about 43 files in the Groups & Files list, some of which are at the top level, and some of which are in groups.

I have configured a repository for my company's Perforce server, and the status indicator shows green. I have set the project's repository to that Perforce repository.

Here's the problem: XCode only seems to get SCM information for about half of the files. If I open the SCM Results window, the file listing at the top shows 21 files, but omits the rest.

The only pattern I can detect here is that the files that don't show up for SCM reside in a different directory from the project file. This is because my project shares a set of common headers with a second project, so the common headers are in a folder outside the folder that contains my project file:



Perforce root folder
    Project folder 1
        MyProject.xcodeproj
        <files that show up with SCM information>
    Project folder 2
        <stuff that I'm not working on right now>
    Common Headers
        <files that are included by reference in
         MyProject.xcodeproj, but that don't work
         with SCM within that project>


Or, if this will wrap properly:


Perforce root folder | _____________________________|_____________________ | | | Project Folder 1 Common Headers Project folder 2 | | Working files live here Non-working files live here MyProject.xcodeproj


All of the affected files are set up with "project relative" paths, and are openable, editable and buildable within XCode, as well as being integrated into the CodeSense index. They are all within the folder hierarchy managed by the Perforce workspace.


Is this just a bug in the SCM handling, with it refusing to look outside the project's folder?

Thanks,
--Mike
_______________________________________________
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: Perforce problem with XCode 3.1.1
      • From: Mike Kobb <email@hidden>
  • Prev by Date: run script after debug
  • Next by Date: Copy files phase interferes with code signature?
  • Previous by thread: run script after debug
  • Next by thread: Re: Perforce problem with XCode 3.1.1
  • Index(es):
    • Date
    • Thread