• 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 structure misses "Headers" folder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: framework structure misses "Headers" folder


  • Subject: Re: framework structure misses "Headers" folder
  • From: Dirk Stegemann <email@hidden>
  • Date: Fri, 30 Dec 2005 03:21:38 +0200

Hello Jonathan,

Am 30.12.2005 um 02:35 schrieb Jonathan Prescott:

Make sure the header files have a role of "Public". Select the framework target. For all header files on which the target depends, there will be a "role" column the project window that has project, public, and private. When you add a header file to a project, it is installed as a "project" header file by default. Project header files are NOT included as part of the final product. "Public" header files go into the Headers directory, and private header files go into the PrivateHeaders directory. These are automatically accounted for the target frameworks build phases. If no header files are marked either public of private, then, the corresponding header directories are not created.

Thanks a lot for clarification!

Works perfectly now :-)


Best regards, Dirk Stegemann





On Dec 29, 2005, at 6:48 PM, Dirk Stegemann wrote:

Hello all,

as it seems, the structure of a frameworks found in "/System/ Library/Frameworks/" differs from the structure of frameworks created with Xcode:

The former have inside their "name.framework" root folder
1) a "Versions" folder
2) a symlink to their 'current' executable
3) a symlink to their 'current' "Resources" folder
4) a symlink to their 'current' "Headers" folder
5) a "Frameworks" folder, or a symlink to their 'current' "Frameworks" folder


OTOH, the frameworks created by Xcode do neither have the symlink to their 'current' "Headers" folder, nor the "Headers" folder at all (and of course no "Frameworks" folder yet).

At the moment, I'm adjusting this by myself, by adding a "Copy Files Build Phase" to copy the headers I want to be able to #include and browse from within other projects to the "$PUBLIC_HEADERS_FOLDER_PATH" path within the "Products Directory", than creating the symlink with a "Run Script Build Phase" which does

rm -f "$CONFIGURATION_BUILD_DIR/$WRAPPER_NAME/Headers"
ln -s "$CONFIGURATION_BUILD_DIR/$PUBLIC_HEADERS_FOLDER_PATH" "$CONFIGURATION_BUILD_DIR/$WRAPPER_NAME/Headers"



Do I misunderstand something here?
Why is the $PUBLIC_HEADERS_FOLDER_PATH path not created automatically?
Is there an easier way to achive this?
Should I file a bug report?


Thanks for enlightenment.

Dirk Stegemann

_______________________________________________ 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: 
 >framework structure misses "Headers" folder (From: Dirk Stegemann <email@hidden>)

  • Prev by Date: Re: __FILE__ Without Full Path?
  • Next by Date: Re: Xcode customizations, workflows, specifications
  • Previous by thread: framework structure misses "Headers" folder
  • Next by thread: Automator update in Xcode 2.2
  • Index(es):
    • Date
    • Thread