caml-list - the Caml user's mailing list
 help / Atom feed
From: Yawar Amin <yawar.amin@gmail.com>
To: Robert Muller <robert.muller2@gmail.com>
Cc: Nicolás Ojeda Bär <nicolas.ojeda.bar@lexifi.com>,  Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] make -> dune: recommended structure
Date: Sun, 12 Jan 2020 19:20:29 -0500
Message-ID: <CAJbYVJ+wSRw8bwrswf-aVf5KNOkggMO5UUwW=nz=bu4=s82izg@mail.gmail.com> (raw)
In-Reply-To: <CAKmYink6Btte-mkcTdZ5nfMKbhNz5pYJg8mrHjeT2+Y3Z_VQCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Hi,

On Sun, Jan 12, 2020 at 6:07 PM Robert Muller <robert.muller2@gmail.com>
wrote:

> One year later, take-two on transitioning from make to dune for an
> OCaml-based PL course. We have a course library, say, code.cma, stored in a
> folder outside the dune workspace, say /Users/studentX/lib/, several course
> projects use the definitions in this course library.
>

Instead of trying to share a code.cma file, perhaps you could distribute an
opam/dune project skeleton with the library source code, code.ml? Then the
problem of trying to tell dune where code.cma is goes away :-)


> I could be wrong, but it seems this setup (with a standard site library
> code.cma) is pretty common,
>

I've never heard of it. From what I understand, OCaml, opam, and dune all
heavily encourage compiling projects from source because of potential
system/architecture differences.

Regards,

Yawar

[-- Attachment #2: Type: text/html, Size: 1560 bytes --]

      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 13:31 Robert Muller
2019-01-13 14:07 ` Nicolás Ojeda Bär
2019-01-13 14:22   ` Robert Muller
2020-01-12 23:06   ` Robert Muller
2020-01-13  0:20     ` Yawar Amin [this message]

Reply instructions:

You may reply publically 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='CAJbYVJ+wSRw8bwrswf-aVf5KNOkggMO5UUwW=nz=bu4=s82izg@mail.gmail.com' \
    --to=yawar.amin@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=nicolas.ojeda.bar@lexifi.com \
    --cc=robert.muller2@gmail.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

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox