• 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: Source File Paths Outside of Project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Source File Paths Outside of Project


  • Subject: Re: Source File Paths Outside of Project
  • From: Brian Barnes <email@hidden>
  • Date: Tue, 11 Sep 2012 13:47:12 -0400

On 9/11/2012 1:33 PM, Seth Willits wrote:

On Sep 11, 2012, at 6:07 AM, Brian Barnes wrote:

Since the latest couple Xcodes, I've had a difficult time with source files that reside outside of the project folder.  My projects are almost always cross platform, so the source is always at a higher level than the various OS project folders.

These latest Xcodes seem designed to have the sources within the project file.  Either dragging in from the finder or using "add" leaves you with red (not found) files.  I can correct this by individually selecting each file and re-picking it in the right panel.

I'm about to make a big move of files, and I really don't want to go through this again :)  Can anybody explain to me if there is any easier way to get Xcode to recognize these files when I drop them in?  Which "relative" option is better for this -- relative to project or relative to group?  I'm assuming relative to project, as my groups don't necessarily represent file structure.  What is the logic involved here?

Hi Brian,


Are you sure the "Relative To … " setting is something acceptable? (ie, the project, not an absolute location.) This is certainly still possible, and really isn't any different from 3, so I suspect it's something like that.

Yup, that's what I use now.  The procedure is this:

1) pick the files I want to include using a right-click/add
2) the files come in, but they are red (these files are outside the project folder) 3) the files import as "relative to group" with a bad absolute path. Note that I am importing them by right-clicking on a group, which might be another cause of the problem 4) change to relative to project, and re-pick the file with the little button next to the file path 5) Now the file has a proper relative path (/../../../ whatever kind of thing)

The problem is I'd like to avoid all these steps. In 3, if I added files, they'd come in as relative and work right. I think it was the addition of all the new (if I'm not mistaken) path types that have messed this up.

If it's broken, it's broken, and I'll have to do it the hard way for a LOT of files. It's a bit annoying (there are hundreds), but unless somebody can tell me a way to get add to work right, or a faster way to do this, it's what I'll have to do.

[>] 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


  • Follow-Ups:
    • Re: Source File Paths Outside of Project
      • From: Stephen Kay <email@hidden>
    • Re: Source File Paths Outside of Project
      • From: Quincey Morris <email@hidden>
References: 
 >Source File Paths Outside of Project (From: Brian Barnes <email@hidden>)
 >Re: Source File Paths Outside of Project (From: Seth Willits <email@hidden>)

  • Prev by Date: Re: Kernel framework
  • Next by Date: Re: Source File Paths Outside of Project
  • Previous by thread: Re: Source File Paths Outside of Project
  • Next by thread: Re: Source File Paths Outside of Project
  • Index(es):
    • Date
    • Thread