From: Ken Wakita <wakita@is.titech.ac.jp>
To: caml-list@inria.fr
Subject: Re: wish
Date: Wed, 27 Dec 2000 11:35:29 +0900 [thread overview]
Message-ID: <20001227113529Y.wakita@is.titech.ac.jp> (raw)
In-Reply-To: <861yuvd160.fsf@itz.dsl.speakeasy.net>
In message (<861yuvd160.fsf@itz.dsl.speakeasy.net>)
from Ian Zimmerman <itz@speakeasy.org>,
talking about "Re: wish",
on 26 Dec 2000 00:41:59 -0800
> Ken> 2. compilers and other tools recognize "-i <subdir>" options that
> Ken> specifies the include subdirectories relative to the standard
> Ken> library path (e.g., "ocamlc -i labltk" instead of "ocamlc -I
> Ken> /usr/local/lib/ocaml-3.00/labltk").
>
> This is already possible with Stolpmann's findlib.
Right. Actually I sometimes use findlib and I feel comfortable with
it. But I am reluctant to use it in a project that I intend to
distribute to others simply because findlib is not part of the
standard distribution. My proposal is simple and easy to use. For
instance, building a multithreaded GTk-based GUI application can be
done by:
ocamlopt -o <executable> -i lablgtk -i threads <source>
which is more pleasant than
ocamlopt -o <executable> \
-I /usr/local/lib/ocaml-3.00/lablgtk \
-I /usr/local/lib/ocaml-3.00/threads <source>
I was very glad that ocaml-3.00 reuses linking information stored in
libraries (.cma and .cmxa). This feature removed most of the long and
ugly --ccopt and --cclib options from my Makefiles's. I guess my
proposal is along this spirit and steps little bit further.
The same (and probably more intelligent stuff) can be done by using
findlib. But I suppose it is easier to convince INRIA people to
include my simple proposal in the standard distribution than findlib.
Ken Wakita
next prev parent reply other threads:[~2000-12-27 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 10:23 wish Ken Wakita
2000-12-26 8:41 ` wish Ian Zimmerman
2000-12-27 2:35 ` Ken Wakita [this message]
2000-12-27 18:04 ` wish Pierre Weis
2000-12-28 6:47 ` wish Ken Wakita
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=20001227113529Y.wakita@is.titech.ac.jp \
--to=wakita@is.titech.ac.jp \
--cc=caml-list@inria.fr \
/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