• 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 subgroups, and Framework header directory creation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework subgroups, and Framework header directory creation


  • Subject: Re: Framework subgroups, and Framework header directory creation
  • From: Nick Zitzmann <email@hidden>
  • Date: Thu, 8 Jul 2004 19:49:51 -0600

On Jul 8, 2004, at 4:27 PM, Joseph Goldstone wrote:

Firstly, within a new Cocoa Framework project's "External Frameworks and Libraries" group, there are two subgroups: "Linked Frameworks" and "Other Frameworks". What is the difference between the two, and if I am adding a .dylib or .framework created elsewhere to my project, in which of these two should I place it? (Or should I place it within "External Frameworks and Libraries" but outside the subfolders?)

It doesn't matter. I usually put frameworks my applications directly link to into the "Linked Frameworks" subgroup, and put frameworks that I want to be able to search (but not link to) in the "Other Frameworks" group. For example, if I want to add the Carbon framework to a project, I add the ApplicationServices and CoreServices frameworks into the "Other Frameworks" group, turn off both frameworks' inclusion in the target, then add the Carbon framework into the "Linked Frameworks" group.


Secondly, in the generated .framework product, there is no Headers directory (parallel to Resources in the hierarchy). The Xcode documentation of the Headers build phase says that it "Installs header files with Public or Private roles in the appropriate locations in the product." [their capitalization of Public and Private]. That is absolutely the only mention I can find of what goes on in this phase. How do I set my header files to be Public or Private?

It was more intuitive in Project Builder and Xcode legacy targets than it is in Xcode native targets. To set header files to be public or private in a native target, you need to click on the target and, in the table view in the project's window, choose the appropriate option from the pop-up menu that appears in each header's row under the "Role" column. It took me a while to find that...


Nick Zitzmann
<http://seiryu.home.comcast.net/>
S/MIME signature available upon request

"To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public." - Theodore Roosevelt
_______________________________________________
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.



  • Follow-Ups:
    • Re: Framework subgroups, and Framework header directory creation
      • From: Joseph Goldstone <email@hidden>
References: 
 >Framework subgroups, and Framework header directory creation (From: Joseph Goldstone <email@hidden>)

  • Prev by Date: Re: Prebinding [was Re: Static data -- thanks]
  • Next by Date: Re: External Editor / ODB Suite
  • Previous by thread: Framework subgroups, and Framework header directory creation
  • Next by thread: Re: Framework subgroups, and Framework header directory creation
  • Index(es):
    • Date
    • Thread