Geek asks and answers

Xcode3 - Relationship Between Library Search Paths and Project Map

As a new MAc developer, coming from VS, I really don't understand what a structure is. If I add frames to my project, does that automatically mean that headers should be found when I do #include <SomeFile.h>?

It seems that in some cases I have to add header search paths. Does this mean that the structure is not working correctly?

+5
source share
2 answers

As defined by Apple Conceptual Documentation :

- , , , nib, , , .

, , , .

Apple:

#include. Objective-C, #import #include. . #import, . :

#include <Framework_name/Header_filename.h>
#import <Framework_name/Header_filename.h>

Framework_name - Header_filename - .

. , . , AddressBook.h.

:

, , , Xcode . , , " " Xcode . Xcode , .

+4

, , () . ( GCC, LLVM-clang) , . :

  • , Unix (libsqlite3.dylib, libxml2.dylib ..) /usr/lib. , () ; , , glib. /usr/include/glib -2.0 .
  • : "Umbrella" (, Core Audio , AudioToolbox.framework ..), , .

, .

+3

More articles:


All Articles