• 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 2.2 is now available [Part 2]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.2 is now available [Part 2]


  • Subject: Re: Xcode 2.2 is now available [Part 2]
  • From: "William H. Schultz" <email@hidden>
  • Date: Thu, 17 Nov 2005 12:43:32 -0800

I tried this:

LIBRARY_SEARCH_PATHS = $(BUILT_PRODUCTS_DIR)/"$(APPLICATION_NAME)".app/Contents/Frameworks $(SDKROOT)/usr/lib

but after closing the project and reopening it, it comes out like this:

LIBRARY_SEARCH_PATHS = $(BUILT_PRODUCTS_DIR)/$(APPLICATION_NAME).app/Contents/Frameworks $(SDKROOT)/usr/lib

Note that different arrangements of the quotes are still removed after closing the project.

APPLICATION_NAME was set to "SuperLab 4", like so:

APPLICATION_NAME = SuperLab 4

Therefore, $(APPLICATION_NAME) needs quotes around it, otherwise the internal space causes the library search path to be split where it shouldn't.  Currently, it's set up this way:

APPLICATION_NAME = SuperLab\ 4

This compiles and links correctly, but I have to have a second copy of this variable that does not have the space escaped for use with scripts and actual build product names.

I have it set up this way because there are many different targets that need to know the name of the one application.  This allows easily changing the application name in one location...  or two...  but that's still better than a dozen or more that I might miss.


Thanks,

Hank Schultz
Cedrus Corporation
http://www.cedrus.com/



On Nov 11, 2005, at 1:55 PM, Chris Espinosa wrote:


On Nov 11, 2005, at 1:32 PM, William H. Schultz wrote:

• Spaces in project path items
Any build setting that contains a path (or includes another build setting that resolves to a path) must be enclosed in double quotes if the path is likely to contain a space character. Xcode will handle the quoted value correctly, but will fail if an unquoted value resolves to a path that includes a space.


This still doesn't seem to be working correctly.  It's better, but incomplete.  I put quotes around the one path in my library search path, and it retains the quotes when I close the project.  However, I have two directories in my framework search path, and the quotes aren't retained here.  I tried putting the quotes around one or both (individually, of course), and the quotes aren't retained when the project is closed.


Could you drag-and-drop your Library Search Paths into this reply?  If the values don't need to be quoted, the quotes may be stripped.  If they clearly do need to be quoted, they should retain the quotes.

Chris

 _______________________________________________
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 is now available [Part 2]
      • From: Dave Thorup <email@hidden>
References: 
 >Xcode 2.2 is now available [Part 2] (From: Chris Espinosa <email@hidden>)
 >Re: Xcode 2.2 is now available [Part 2] (From: "William H. Schultz" <email@hidden>)
 >Re: Xcode 2.2 is now available [Part 2] (From: Chris Espinosa <email@hidden>)

  • Prev by Date: XCode 2.2 & Perforce (Internal Error)
  • Next by Date: Re: g++ 4 & MACOSX_DEPLOYMENT_TARGET=10.2
  • Previous by thread: Re: Xcode 2.2 is now available [Part 2]
  • Next by thread: Re: Xcode 2.2 is now available [Part 2]
  • Index(es):
    • Date
    • Thread