Re: Packaging Omni frameworks for distribution.
Re: Packaging Omni frameworks for distribution.
- Subject: Re: Packaging Omni frameworks for distribution.
- From: Finlay Dobbie <email@hidden>
- Date: Sat, 7 Jul 2001 11:05:45 +0100
The preferred way of doing this is to include them in your app's bundle
(see OmniWeb and other Omni apps, they all do it). There is a discussion
on how to do this over at
http://www.cocoadev.com
On Friday, July 6, 2001, at 03:58 pm, Charles Bennett wrote:
Hi all, My application uses the wonderful omni frameworks for some of
the networking
code. I have two questions..
1: How should the target settings be handled for headers? There is no
need
for them to go with the installed app. Do I turn off both public and
private?
2: What makes the most sense in term of packaging the frameworks for
distribution?
Should I bury them inside my app or install them to /Library/Frameworks
or just
provide another .pkg with only the frameworks, and explain that you
"may" need to install this package? I'm not worried about developers
in the
sense that they "know" what they want to happen. I'm trying to figure
out what the
best way to deal with a "user" would be and how this would effect other
developers
that want to install the frameworks for their apps as well..
I'm just trying to figure out a method that all developers can use, to
stay out
of each others way. It seems to me that if we can all agree on some
guidelines
now. Then we will avoid a larger problem later.