Re: Framework library...
Re: Framework library...
- Subject: Re: Framework library...
- From: Mike Beam <email@hidden>
- Date: Tue, 16 Jul 2002 11:49:35 -0500
>
Actually, I was just being stupid. It was too early when I wrote this up, and
>
I realized that it's not a build time error but a runtime error. It's
>
treating the framework as a dynamic library instead of a static library (like
>
I want), and I didn't have the framework in the frameworks directory. The
>
wrapper is wrapping around a static library (there is a dynamic library that
>
is already installed on the machine), so how would I go about statically
>
linking a framework to an application (so the framework doesn't have to be on
>
the end user's machine). There must be a method, I just can't figure it out!
I haven't been following this thread too closely, so forgive me if my
response has been mentioned already, or whatnot. Would it be sufficient to
include the framework inside of your application's bundle? OmniWeb does
this in the directory OmniWeb.app/Contents/Frameworks. This would still have
the framework on the end users machine, but they don't have to know about
it.
Mike Beam
_______________________________________________
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.