From: Tom Murray <yozhik@computer.org>
To: Stefano Zacchiroli <zack@bononia.it>
Cc: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Automake support for OCaml
Date: Mon, 22 Dec 2003 09:43:26 -0800 [thread overview]
Message-ID: <58AF87BA-34A6-11D8-BA54-000A9577557E@computer.org> (raw)
In-Reply-To: <20031222103656.GA3235@fistandantilus.takhisis.org>
> You plan to use ocamlfind only at install time, right? Why not
> supporting it also at compile time? I'm thinking about something like:
I hadn't fully thought about it, but you're right that I should use it
at compile and link time, tool.
> CAML_PACKAGES = unix pcre
>
> Surely you can do the same using yours CAML_LDADD in conjunction with
> "ocamlfind query", but it will be harder to use and less intuitive.
_PACKAGES sounds good. I'll add it on a per-makefile and per-target
basis.
> It shouldn't be a major change, should it?
No, and you're making me think I should just tackle the install stuff,
too and get it over with. I do want to make things work without
ocamlfind, too, though.
> Thanks for your work
> from an ocaml user that
> has fought a lot with
> automake in the past :-(
Yes, so many times I want to abandon the autotools for their messiness,
but they always turn out to be _so_ convenient. I have yet to see a
make replacement that is as flexible.
Cheers,
tm
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-12-22 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 7:48 Tom Murray
2003-12-22 10:36 ` Stefano Zacchiroli
2003-12-22 17:43 ` Tom Murray [this message]
2003-12-22 18:25 ` skaller
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=58AF87BA-34A6-11D8-BA54-000A9577557E@computer.org \
--to=yozhik@computer.org \
--cc=caml-list@inria.fr \
--cc=zack@bononia.it \
/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