• 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: Xcode 4 Preference for Children Paths
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 4 Preference for Children Paths


  • Subject: Re: Xcode 4 Preference for Children Paths
  • From: Brian Barnes <email@hidden>
  • Date: Fri, 02 Mar 2012 23:42:26 -0500

On Mar 2, 2012, at 6:24 PM, Jens Alfke wrote:


On Mar 1, 2012, at 4:57 PM, Brian Barnes wrote:

What's happening is Xcode 4 likes to set paths to "relative to group", and *assumes* when importing that the group reflects the setup.  Why older Xcode 3 projects work is the groups have a blank path, and then the "relative to group" acts like "relative to project."  This was the key that took me a while to deduce.

I can’t figure out what the actual problem is that you’re running into. Can you describe it?

And I haven’t had this kind of problem myself, in repos that are laid out this way. When I drag a source folder into a project, Xcode gives it a relative path like “../Source”. Everything’s fine.

—Jens

Most of the time it'll work correctly, but in my situation, I got caught by this and I think it's determined by WHEN you created a group.  Still not sure, but if the groups is Xcode 3 type you'll never run into this.

Here's the deal, as best I can explain it.

Two of the path types (for files, in the right pane) are "Relative to Group" and "Relative to Project".  Relative to Project is what you'd expect, the "../Source" kind of thing.  Relative to Group is the same BUT it appends whatever the GROUPS path is to the beginning.

IF the group path is blank, then Relative to Group works exactly like Relative to Project.

When I created a new project, the groups HAD a path (something usually like the group name.)  My added files were set "Relative to Group".  So the actual path became "groupname/../Source" which was wrong.  Clearing the group path (in the right pane, when the group is selected) fixed that.  Or just setting all the files to "relative to project."

Xcode 4 -- as far as I can tell and might be mistaken because I never tracked where this came from -- seems to want to create groups that way and wants to set imported files to "relative to group" (I think if you are importing them into a group.)

Again, this isn't a bug, just a lot of options that can possible expose wacky settings that are hard to fix.  The key is HOW the groups I just created got this additional information.  I never entered it.  Not sure what happened.

[>] Brian
 _______________________________________________
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: 
 >Xcode 4 Preference for Children Paths (From: Brian Barnes <email@hidden>)

  • Prev by Date: Re: Xcode - AN APPLE OPPORTUNITY!
  • Next by Date: Re: xcode & c++
  • Previous by thread: Re: Xcode 4 Preference for Children Paths
  • Next by thread: Xcode 4.3 & distributed builds
  • Index(es):
    • Date
    • Thread