Re: Weird Problem with Embedding Frameworks
Re: Weird Problem with Embedding Frameworks
- Subject: Re: Weird Problem with Embedding Frameworks
- From: Marc Weil <email@hidden>
- Date: Tue, 10 Jun 2003 22:18:33 -0400
Well, I know for sure that it isn't the public/private headers thing since
this is an already-made framework that has all of that stuff set.
When you say that I have to make sure the framework search path is right,
does that mean that I have to add a search path that goes into
MyApp.app/Contents/MacOS/Frameworks? What happens if I clean the project,
and the build product is deleted temporarily? I've never heard of that...
I also looking in the Info panel of the framework in my project. Choosing
any of the other settings besides Absolute results in
../../../../../../../../Library/Frameworks/EDCommon.framework being the
path, which I don't think will help any.
One of the things I am confused about is this: if you tell PB to link to a
framework in Folder A, and then you have that framework copied into the
app's bundle at compile-time, how do you tell PB not to look for that
framework in Folder A anymore? I mean, there has to be a placeholder (for
lack of a better work) object in the project for the framework that allows
it to be added to the Copy Files build phase. Geez this is confusing me. I'd
think that something as seemingly simple as this would be, well, simple to
accomplis, especially with the caliber of tools Apple provides us.
Thanks for the help though. Any other ideas anyone?
-- Marc Weil
On 6/10/03 9:34 PM, "Bill Cheeseman" <email@hidden> wrote:
>
on 03-06-10 9:03 PM, Marc Weil at email@hidden wrote:
>
>
> But now whenever I run the app, dyld complains that it can't find the
>
> framework.
>
>
There are a trillion little settings you have to get right, and they're
>
scattered all over a dozen different dialogs and panes and panels. An
>
official checklist would be really great.
>
>
But, given the state of the existing documentation, you'll have to write
>
your own checklist. Every time I try to build a new app with a new embedded
>
framework, I run into that exact same dyld error, and I have to start from
>
scratch again to remember what I forgot to do.
>
>
There's a place in the framework project where you have to remember to check
>
a checkbox to make the headers public, but that doesn't sound like your
>
issue. It bites me every time, but I've finally learned to remember to do
>
that.
>
>
You have to get the framework search path right. Some are built in, but
>
others require that you add a path to your application project.
>
>
There's a Show Info dialog you have to open, where a pop-up menu lets you
>
choose to search for the framework in an absolute path, or a
>
project-relative path, or a couple of other options. I'm forever getting
>
that wrong, because sometimes I keep my framework in a centralized build
>
folder for all my projects (especially when I'm writing the framework and
>
the app at the same time), but sometimes I keep my framework adjacent to the
>
application source (especially when I'm writing a framework and a sample app
>
for distribution together).
>
>
Frequently, I just have to remember to manually trash the last build folder
>
before building a new one with a different build style. Somehow, I think
>
that might be the issue you're confronting.
>
>
Or maybe it's something else.
>
>
--
>
>
Bill Cheeseman - email@hidden
>
Quechee Software, Quechee, Vermont, USA
>
http://www.quecheesoftware.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.