From: james woodyatt <jhwoodyatt@mac.com>
To: Damien Doligez <Damien.Doligez@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] findlib and mac os x frameworks/bundles/applications
Date: Fri, 28 Sep 2001 11:31:32 -0700 [thread overview]
Message-ID: <0A833163-B43F-11D5-8A0B-000502DB38F5@mac.com> (raw)
In-Reply-To: <200109281357.PAA0000014253@beaune.inria.fr>
On Friday, September 28, 2001, at 06:57 , Damien Doligez wrote:
>
> I would say these two distribution formats have very different
> purposes. Apple's bundles and packages are most useful for easy
> installation of stand-alone applications. findlib is for managing
> libraries that are going to be used by programmers.
The Mac OS X framework system (actually, it's Darwin's framework system)
is intended for distributing libraries used by programmers. Apple
modified the GCC compiler to add support for searching and linking with
frameworks in a manner somewhat reminiscent of the way findlib does it
with Ocaml for its own framework system.
> I think you should use an Apple-style package if you're distributing
> an application targetting the end user (in which case ease of
> installation is very important), and a findlib package if your product
> is a library to be used by other programmers (in which case reading
> the docs and typing a few command lines to a shell prompt is not a big
> deal).
I hold to the philosophy that programmers are every bit as intelligent
as end users. They ought to be treated like human beings, and with the
same level of respect. Ease of use is important to everyone.
Do you think modifying findlib to understand the layout of Mac OS X
frameworks is too hard, or a bad idea for some other reason?
I haven't looked at the code for findlib yet. I suppose it could make
sense to dispense with findlib on Mac OS X and go straight for
developing a framework search, link and construction system from
scratch. But I hate reinventing other people's wheels.
I was hoping to find out if anyone else had given this problem some
thought before I started in on it.
--
j h woodyatt <jhw@wetware.com>
"...the antidote to misinformation is more information, not less."
--vinton cerf
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-09-28 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 13:57 Damien Doligez
2001-09-28 18:31 ` james woodyatt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-27 22:47 james woodyatt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0A833163-B43F-11D5-8A0B-000502DB38F5@mac.com \
--to=jhwoodyatt@mac.com \
--cc=Damien.Doligez@inria.fr \
--cc=caml-list@inria.fr \
--cc=jhw@wetware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox