On Jun 8, 2010, at 6:26 PM, Graham Cox wrote:
>
> On 09/06/2010, at 11:20 AM, Chris Tracewell wrote:
>
>> Why would it not be exporting the file? Yes, I added it to the target when I
>> created the file.
>
>
> Right-click the file in Xcode and set its role to "Public".
>
> This necessary st
On 09/06/2010, at 11:20 AM, Chris Tracewell wrote:
> Why would it not be exporting the file? Yes, I added it to the target when I
> created the file.
Right-click the file in Xcode and set its role to "Public".
This necessary step is very obscure and the menu doesn't reflect the currently
set
Have you set the scope of the necessary header files to public?
file:///Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.DeveloperTools.docset/Contents/Resources/Documents/documentation/DeveloperTools/Conceptual/XcodeBuildSystem/100-Targets/bs_targets.html
On 09/06/2010, at 11:20 A
I just made my first private framework a few weeks ago. I took some common
categories and custom classes I use across projects and put them in my new FW.
All has been fine until today when I added a new class file to it. I clean and
build the FW and then build my project that is utilizing the FW
