caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: "Markus Weißmann" <markus.weissmann@in.tum.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] React 1.0.0
Date: Fri, 11 Apr 2014 17:58:30 +0200	[thread overview]
Message-ID: <B2E1915A8884481FB1F2890D2A11F5FD@erratique.ch> (raw)
In-Reply-To: <53c5ec5fa458ca0ae78f13ff79d9abf5@in.tum.de>

Le vendredi, 11 avril 2014 à 17:12, Markus Weißmann a écrit :
> while at it, could you please provide a non-opam style installation
> routine? (Oasis, Makefile, ..)

Sorry but the answer is no. 1) I don't have the time for that 2) oasis is a broken idea that gets in the way 3) I don't want to maintain more than one build system 4) I don't want to have to implement an install procedure in each of my packages.  

For react the build system is very simple, from the root directory of the distribution you have to invoke a single shell script as follow:

./pkg/build $HAS_NATIVE  

Where HAS_NATIVE should be "true" if you have ocamlopt and "false" if you don't. This will build the artefacts using ocamlbuild and generate a react.install file at the toplevel directory of the distribution. You can then either process this file yourself or more recommended directly use the opam-installer tool distributed with opam to process this file and install the files at a given $PREFIX.

Note that this procedure is the same for the dozen of packages I distribute except there may be more booleans to pass to the `build` script to specify optional dependencies. See e.g. Vg's pkg/build usage: https://github.com/dbuenzli/vg/blob/master/pkg/build#L3

Feel free to ask me any question if you run into problems.

Best,

Daniel



  reply	other threads:[~2014-04-11 16:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 16:01 Daniel Bünzli
2014-04-08  1:04 ` Daniel Bünzli
2014-04-11 15:12   ` Markus Weißmann
2014-04-11 15:58     ` Daniel Bünzli [this message]
2014-04-11 16:05       ` Anil Madhavapeddy
2014-04-11 16:32         ` Daniel Bünzli
2014-04-11 16:59           ` [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0) Daniel Bünzli
2014-04-11 22:33             ` David Allsopp
2014-04-11 23:38               ` Daniel Bünzli
2014-04-15 19:21                 ` [Caml-list] topkg (was Re: OCaml script on windows (was Re: [ANN] React 1.0.0)) Daniel Bünzli
2014-04-12  7:39               ` [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0) Adrien Nader
2014-04-12  7:44                 ` Adrien Nader
2014-04-12 10:14                   ` Daniel Bünzli
2014-04-12 11:41                     ` Adrien Nader
2014-04-12 12:38                       ` Daniel Bünzli
2014-04-13  9:21                         ` Adrien Nader
2014-04-13  9:31                           ` Anil Madhavapeddy
2014-04-13 11:17                             ` Adrien Nader
2014-04-13 12:33                               ` Daniel Bünzli
2014-04-21 18:18   ` [Caml-list] [ANN] React 1.0.1 Daniel Bünzli
2014-04-27 20:33     ` [Caml-list] [ANN] React 1.1.0 Daniel Bünzli
2014-05-04 23:16       ` Daniel Bünzli

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=B2E1915A8884481FB1F2890D2A11F5FD@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=markus.weissmann@in.tum.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).