caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Chet Murthy <murthy.chet@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] sexplib, type_conv, ocamlbuild
Date: Tue, 6 Aug 2013 19:21:54 +0100	[thread overview]
Message-ID: <ABD705B5-5473-4B39-92AD-E9C5ED95E4A5@recoil.org> (raw)
In-Reply-To: <4370519.gRzcm4ADqt@groupon>

The trick is a little obscure, I fear.  At the end of your OASIS _tags file,
add this line:

# OASIS_STOP
true: syntax_camlp4o, pkg_sexplib.syntax

The lines after the OASIS_STOP will not be overridden on a future
"oasis setup".

Note that the trunk version of OASIS has a heuristic to detect
dependencies containing a ".syntax" extension and automating this
process. See:
  https://github.com/ocaml/oasis/pull/11

-anil


On 6 Aug 2013, at 18:28, Chet Murthy <murthy.chet@gmail.com> wrote:

> 
> I'm trying to puzzle out how to use sexplib's type_conv (pa_sexp_conv)
> with oasis.  I've looked at the example in the sexplib source, but
> (sigh) cannot seem to coax oasis to generate something similar for my
> own source.
> 
> I'm a little mystified as to how to get it to do the trick ....
> 
> Anybody got this to work?  Sexplib's auto-generated marshallers seem
> like they'd be so .... sweet.
> 
> Thanks,
> --chet--
> 
> 
> -- 
> 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
> 


      reply	other threads:[~2013-08-06 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 17:09 [Caml-list] Call for Participation: CUFP 2013 Thomas Gazagnaire
2013-08-06 17:28 ` [Caml-list] sexplib, type_conv, ocamlbuild Chet Murthy
2013-08-06 18:21   ` Anil Madhavapeddy [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=ABD705B5-5473-4B39-92AD-E9C5ED95E4A5@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=murthy.chet@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
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).