• 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
Xcode 2.2: Access paths and header search paths
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode 2.2: Access paths and header search paths


  • Subject: Xcode 2.2: Access paths and header search paths
  • From: Justin Bur <email@hidden>
  • Date: Mon, 14 Nov 2005 13:30:40 -0500

The problem with spaces in path names appears to have gotten worse in Xcode 2.2.

For the purpose of adding files to a project, an access path must not make any attempt to quote spaces in the path name (either backslashes or quotation marks). This was certainly the case in Xcode 2.1 and is still true for 2.2. However, 2.2's user interface for access paths will in some circumstances attempt to put backslashes before spaces in the path, and especially, it will refuse to let you remove them. If you end up with backslashes in your access path, you have to use Property List Editor to clean them out (key PBXApplicationwideBuildSettings).

When using an access path within a header search path, Xcode 2.2 *requires* that any spaces be backslashed. This is new behavior. It is particularly irritating, because it now seems to be impossible to use the same access path both to locate files for inclusion in the project, and to locate files through the header search path during compilation, e.g. for use in a precompiled header.

This situation comes up of course when compiling projects that use PowerPlant, whose files tend to be found under paths full of spaces such as "/Applications/Metrowerks CodeWarrior 10.0/Metrowerks CodeWarrior". I have temporarily defined separate access paths "CodeWarrior" (same as in Xcode 2.1 with no backslashes or quotes) and "CodeWarrior-backslash" (with a backslash before each space, for use within the header search path). I have also submitted a bug report.

But I also wonder if there is another way around this problem. After all, it is surely not an uncommon situation. What am I doing wrong, or what are others doing?

justin
_______________________________________________
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: Xcode 2.2: Access paths and header search paths
      • From: "Sean McBride" <email@hidden>
  • Prev by Date: Re: 2.1->2.2 created link error: std::__ioinit
  • Next by Date: Re: Interpreting -bind_at_load warning?
  • Previous by thread: Re: Troubles upgrading a XCode 1.5 project to 2.2
  • Next by thread: Re: Xcode 2.2: Access paths and header search paths
  • Index(es):
    • Date
    • Thread