• 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: include problems with XCode and frameworks [solved]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: include problems with XCode and frameworks [solved]


  • Subject: Re: include problems with XCode and frameworks [solved]
  • From: John James <email@hidden>
  • Date: Thu, 23 Feb 2006 07:47:54 -0500

Discovered that there were spaces in some of the folder names in the path involved. (maybe there should be a warning somewhere for this) The spaces break the definition of the search paths. Subtle error for a nubie to find.

Learned that to use the source files that where used to make the framework (which were on my machine) I had to set the "User Header Search Paths" to the folder just above the Frameworks hierarchy. Then all would work.

My conclusion is to get this framework to be used without having the original source code one would have to design the framework differently, i.e. not use hierarchy in "public" header files. Or is there a way to get the hierarchal defined includes within the Framework to work without redesigning the framework includes? Is there a documentation reference for this?

On Feb 22, 2006, at 10:47 AM, John James wrote:


I have tried a myriad of changes to various search paths to define where "<xercesc/" is but to no avail. What is the secret?
Thanks for your help.
_______________________________________________
_______________________________________________
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: 
 >include problems with XCode and frameworks (From: John James <email@hidden>)

  • Prev by Date: Re: Any compiler warning for default copy constructors?
  • Next by Date: Re: Any compiler warning for default copy constructors?
  • Previous by thread: include problems with XCode and frameworks
  • Next by thread: Linking a Universal Static Library in XCode 1.5
  • Index(es):
    • Date
    • Thread