• 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: Framework header conversion advice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework header conversion advice


  • Subject: Re: Framework header conversion advice
  • From: Arturo PĂ©rez <email@hidden>
  • Date: Sat, 5 Jun 2004 10:44:49 -0400

On Jun 4, 2004, at 11:13 PM, Glen Low wrote:

Dear All,

As you know, in OS X framework headers are #included like this <Framework/Header.h>. Unfortunately this is pretty different from standard Unix usage (LSB/FSH) where the headers are put into /usr/include and used like this <Header.h>.

Actually, most of the third party libraries frameworks I've used on Unix work the OS X way, since at least the 80s. Maybe linux doesn't but it doesn't have the legacy of support requirements that other Unices have.


5. Leave it as is and ask users to also -I Framework/Headers.

Again, that's what just about every 3rd party software kit I've used under unix has required. That an
-L<libraryInstallPath> -l<library>


--arturo
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


References: 
 >Framework header conversion advice (From: Glen Low <email@hidden>)

  • Prev by Date: GCC 3.3 and signal 5 (SIGTRAP).
  • Next by Date: RE: GCC 3.3 and signal 5 (SIGTRAP).
  • Previous by thread: Framework header conversion advice
  • Next by thread: XCode issue (wants to use the wrong Info.plist file)
  • Index(es):
    • Date
    • Thread