I'd get info on the headers directory or one of the red header files
under it and see what Xcode thinks the path is and then compare that
with what the actual path is.
Scott
On Jan 15, 2004, at 8:53 PM, Pete Yandell wrote:
> I've got a framework that I've built that works just fine on my
> machine but, when it's added to a project on another person's machine,
> builds fail. Expanding the framework in Xcode shows the Headers folder
> in red as though Xcode can't find it.
>
> Has anybody seen behaviour like this before? I'm completely stumped as
> to why this would happen.
>
> What we've tried so far:
> - Checking the framework in the Finder on both machines show that
> everything is where it should be and all the internal aliases in the
> framework are correct.
> - Creating a new empty project and adding the framework doesn't make
> any difference. It works just fine on my machine but dies on the other
> one.
> - Adding an older version of the framework built with Project Builder
> to the Xcode projects works just fine on both machines.
>
> Pete Yandell
> http://pete.yandell.com/
> _______________________________________________
> 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.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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.
