From: Malcolm Matalka <mmatalka@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] Announcing yet another Makefile for OCaml
Date: Thu, 23 Jan 2014 10:36:50 +0000 [thread overview]
Message-ID: <877g9r56il.fsf@gmail.com> (raw)
In-Reply-To: <20140123093518.GC20624@frosties> (Goswin von Brederlow's message of "Thu, 23 Jan 2014 10:35:18 +0100")
FWIW, I have my own Makefile approach, with ocamlfind support. I
started it because I wanted to understand how to compile things in Ocaml
and the various files needed to build different variables. Since then
it's grown into the base for all of my Ocaml.
I should probably use ocamlbuild but I've never really found it that
compelling and my Makefile solution handles making and running tests and
examples for me just how I like it.
It is in a repo I clone from whenever I start a new repo:
https://github.com/orbitz/ocaml-template
I don't actually suggest using it unless one understands Makefile's a
bit, it's made specifically for things I want.
/M
Goswin von Brederlow <goswin-v-b@web.de> writes:
> On Wed, Jan 22, 2014 at 08:22:30PM +0100, 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):
>>
>> OCamlMakefile vs my Makefile
>> * Support for ocamlfind vs none
>
> No ocamlfind? That realy sucks. Anything non trivial will require some
> extras, if only batteries, core or unix. You realy need support for
> ocamlfind so adding libraries becomes easy.
>
> MfG
> Goswin
next prev parent reply other threads:[~2014-01-23 10:36 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
2014-01-23 0:08 ` Christian Rinderknecht
2014-01-23 9:35 ` Goswin von Brederlow
2014-01-23 10:36 ` Malcolm Matalka [this message]
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=877g9r56il.fsf@gmail.com \
--to=mmatalka@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
/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).