From: John Whitington <john@coherentgraphics.co.uk>
To: rinderkn@caesar.elte.hu
Cc: William R <r.3@libertysurf.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] Announcing yet another Makefile for OCaml
Date: Wed, 22 Jan 2014 23:30:48 +0000 [thread overview]
Message-ID: <52E054A8.6040307@coherentgraphics.co.uk> (raw)
In-Reply-To: <52E01A76.7050109@caesar.elte.hu>
Hi,
Thanks for this work -- I'll have a look since I use OCamlmakefile
exclusively at the moment. Per-module options look interesting!
Christian Rinderknecht wrote:
> Dear William and list members,
>
> On 01/22/2014 08:43 AM, William R wrote:
>> could you explain differences with OCamlMakefile
>
> This is a fair question, since Markus' work has been around for quite
> a while, but I am afraid that I never used it. Nevertheless, I went
> through the documentation and the source code and here are the main
> differences I can see at the moment (my apologies to Markus if I am
> mistaken):
To correct a few: in OCamlmakefile:
> * Builds library and toplevels vs none
make top, make byte-code-no-link, make native-code-nolink
> * Generates documentation vs none
make htdoc/ltdoc/psdoc/pdfdoc
> * Support for ocamlfind vs none
PACKS = camlpdf
to use ocamlfind packages.
To get it to use ocamlfind all over, use
REAL_OCAMLFIND=ocamlfind
(not documented)
Thanks,
--
John Whitington
Director, Coherent Graphics Ltd
http://www.coherentpdf.com/
next prev parent reply other threads:[~2014-01-22 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 1:03 Christian Rinderknecht
2014-01-22 7:43 ` William R
2014-01-22 19:22 ` Christian Rinderknecht
2014-01-22 23:30 ` John Whitington [this message]
2014-01-23 0:08 ` Christian Rinderknecht
2014-01-23 9:35 ` Goswin von Brederlow
2014-01-23 10:36 ` Malcolm Matalka
2014-01-23 14:47 ` Christian Rinderknecht
2014-01-24 16:18 ` Christian Rinderknecht
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=52E054A8.6040307@coherentgraphics.co.uk \
--to=john@coherentgraphics.co.uk \
--cc=caml-list@inria.fr \
--cc=r.3@libertysurf.fr \
--cc=rinderkn@caesar.elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).