FROM : Kyle Sluder
DATE : Sun Jan 13 09:55:41 2008
Assuming you're building your framework as part of the same project as
your actual app, you can simply mark the role of the framework's
header files as private, and #import them in your app's source using
relative quoted paths like #import "FrameworkHeaderFile.h", rather
than the typical #import <FrameworkName/HeaderFile.h> paradigm.
You're still going to need to link the app to the framework and copy
the framework into the app bundle's Frameworks directory, but this way
you won't be copying the headers with it.
HTH,
--Kyle Sluder
DATE : Sun Jan 13 09:55:41 2008
Assuming you're building your framework as part of the same project as
your actual app, you can simply mark the role of the framework's
header files as private, and #import them in your app's source using
relative quoted paths like #import "FrameworkHeaderFile.h", rather
than the typical #import <FrameworkName/HeaderFile.h> paradigm.
You're still going to need to link the app to the framework and copy
the framework into the app bundle's Frameworks directory, but this way
you won't be copying the headers with it.
HTH,
--Kyle Sluder
| Related mails | Author | Date |
|---|---|---|
| Mitchell Hashimoto | Jan 13, 09:15 | |
| Kyle Sluder | Jan 13, 09:55 | |
| Philippe Casgrain | Jan 13, 16:19 | |
| Stefan | Jan 13, 16:57 | |
| Kyle Sluder | Jan 13, 20:23 | |
| John Stiles | Jan 13, 22:18 | |
| glenn andreas | Jan 13, 23:06 | |
| John Stiles | Jan 14, 05:28 | |
| Chris Hanson | Jan 14, 06:51 | |
| Timothy Reaves | Jan 15, 01:08 | |
| John Stiles | Jan 15, 01:23 | |
| Alastair Houghton | Jan 15, 18:13 |






Cocoa mail archive

