caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Florent Monnier <monnier.florent@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome
Date: Thu, 19 Dec 2013 13:38:45 +0100	[thread overview]
Message-ID: <CAE1DttCaisa83oxnQd2ze25wQwy7H_BgoP_01cTQNfWPCvZyyQ@mail.gmail.com> (raw)
In-Reply-To: <4FC13EE9F3724C5CA1CFD13544AD2AAC@erratique.ch>

2013/12/19, Daniel Bünzli wrote:
>
> Le jeudi, 19 décembre 2013 à 06:20, Florent Monnier a écrit :
>
>> which did "compiled" the lib but not "installed" it (the poor joke
>> that i'm attempting to make is that the paragraph is called
>> "Installation", and that following it doesn't lead me to a point where
>> I get something installed.)
>
> Well if you want to be picky the paragraph tells you how to *install* with
> opam and says to look at the `opam` file for *build* instructions...

Oh yes! One day I'll have to learn reading the English language :-)

> That being said after that you are almost there, just use opam-installer [1]
> on the toplevel `tsdl.install` file that these build commands generated.
> Especially since you are packaging for a distribution, this tool can
> generate you a shell script for installation (and eventually you'll be able
> to apply this to all of my packages).

Using the Opam method will not help on platforms where I'm unable to
compile Opam.
(For example on MS/Windows)

> (N.B. manual installation is for advanced users who know what they are doing
> so I'm not going to maintain instructions about that)

Compiling Opam the "file-by-file" way on MS/Windows is also not a piece of cake.

> Best,
>
> Daniel
>
> [1] https://sympa.inria.fr/sympa/arc/caml-list/2013-12/msg00068.html
>
-- 
Regards,
Florent

  reply	other threads:[~2013-12-19 12:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  6:11 Daniel Bünzli
2013-12-17  7:02 ` Anthony Tavener
2013-12-17 14:17 ` Florent Monnier
2013-12-17 15:14   ` Daniel Bünzli
2013-12-18  6:54   ` Erkki Seppala
2013-12-18  8:05     ` Anthony Tavener
2013-12-18  9:24       ` Daniel Bünzli
2013-12-18  8:18     ` Florent Monnier
2013-12-22 10:01       ` Kakadu
2013-12-30 13:28         ` Vu Ngoc San
2013-12-17 17:05 ` Ashish Agarwal
2013-12-17 17:47   ` Daniel Bünzli
2013-12-17 18:57     ` Ashish Agarwal
2013-12-17 19:45       ` Anthony Tavener
2013-12-18 15:40         ` Ashish Agarwal
2013-12-18 18:02           ` Yotam Barnoy
2013-12-18 19:53             ` Daniel Bünzli
2013-12-18 22:29               ` Ashish Agarwal
2013-12-18 22:45                 ` Daniel Bünzli
2013-12-17 20:26       ` Daniel Bünzli
2013-12-18  1:13         ` Francois Berenger
2013-12-18  6:44           ` Erkki Seppala
2013-12-18  9:21           ` Daniel Bünzli
2013-12-19  1:11             ` Florent Monnier
2013-12-19  6:39       ` Florent Monnier
2013-12-17 19:29     ` Erkki Seppala
2013-12-19  5:20 ` Florent Monnier
2013-12-19  5:27   ` Florent Monnier
2013-12-19  7:13   ` Daniel Bünzli
2013-12-19 12:38     ` Florent Monnier [this message]
2014-02-12 10:43 ` 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=CAE1DttCaisa83oxnQd2ze25wQwy7H_BgoP_01cTQNfWPCvZyyQ@mail.gmail.com \
    --to=monnier.florent@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).