From: Ivan Gotovchits <ivg@ieee.org>
To: Louis Gesbert <louis.gesbert@ocamlpro.com>
Cc: caml-list <caml-list@inria.fr>,
"Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"Christoph Höger" <christoph.hoeger@tu-berlin.de>
Subject: Re: [Caml-list] Passing configuration options to opam
Date: Tue, 6 Sep 2016 07:47:16 -0400 [thread overview]
Message-ID: <CALdWJ+wrFrjPXOPd+mQ1M1GUoTDBnPSMkT18NmghKV0SWPGLkA@mail.gmail.com> (raw)
In-Reply-To: <2170048.Zk88dHpl0p@agaric>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Hi Christoph,
Since ocaml-lua is using oasis build system underneath the hood it is
possible to control configuration parameters via environment variables. Any
variable, if not set
explicitly by a command line, will be looked up in the environment. In
your case enabling `luajit` should be as simple as:
luajit=true opam install ocaml-lua
Regards,
Ivan
On Tue, Sep 6, 2016 at 6:34 AM, Louis Gesbert <louis.gesbert@ocamlpro.com>
wrote:
> > - Daniel Bünzli, 06/09/2016 11:49 -
> > On Tuesday 6 September 2016 at 11:46, Daniel Bünzli wrote:
> > > You can do `opam pin edit ocaml-lua` and change the build instructions
> to your wishes. But best would be to upstream luajit discovery.
> >
> > Note that you will first need to pin to a specific version using e.g.
> `opam pin add ocaml-lua 1.4`
>
> [not anymore in opam 2.0, but it's not out yet]
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 1892 bytes --]
prev parent reply other threads:[~2016-09-06 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 9:25 Christoph Höger
2016-09-06 9:46 ` Daniel Bünzli
2016-09-06 9:49 ` Daniel Bünzli
2016-09-06 10:34 ` Louis Gesbert
2016-09-06 11:47 ` Ivan Gotovchits [this message]
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=CALdWJ+wrFrjPXOPd+mQ1M1GUoTDBnPSMkT18NmghKV0SWPGLkA@mail.gmail.com \
--to=ivg@ieee.org \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@tu-berlin.de \
--cc=daniel.buenzli@erratique.ch \
--cc=louis.gesbert@ocamlpro.com \
/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