From: Adrien <camaradetux@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Lwt and OCamlMakefile
Date: Tue, 21 Dec 2010 14:18:11 +0100 [thread overview]
Message-ID: <AANLkTimypOALKtLabgGW8yM3xFaqWdybm_hZbyVtwPnG@mail.gmail.com> (raw)
In-Reply-To: <slrnih0vto.ut5.sylvain@gallu.homelinux.org>
On 21/12/2010, Sylvain Le Gall <sylvain@le-gall.net> wrote:
> On 21-12-2010, Jérémie Dimino <jeremie@dimino.org> wrote:
>> On Mon, Dec 20, 2010 at 09:36:39PM -0500, orbitz@ezabel.com wrote:
>>> Thanks, I forgot to mention that I am setting that:
>>>
>>> (*pp camlp4o pa_lwt.cmo *)
>>
>> This one should work:
>>
>> (*pp camlp4o `ocamlfind query -i-format lwt` `ocamlfind query
>> -predicates syntax,preprocessor -a-format -r lwt.syntax` *)
>>
>
> It will work on Linux. On Windows, you will get a problem because
> ocamlfind EOL (win32) doesn't match "`...`" EOL wrapping (cygwin).
>
> There was a similar problem with sexplib...
>
For windows, for sexplib and mikmatch_*str*, I do the preprocessing on
linux[1] and put everything in a git branch which I then access on
windows (I also love gitweb's ability to generate a tarball of the
source :-) ).
It also avoids the need to have a working camlp* on windows (msys).
It doesn't work for mikmatch_pcre because it requires an additional
library (for the "macro" feature) but it's been quite handy so far.
Most credits for the script go to Julien Moutinho.
[1] http://git.ocamlcore.org/cgi-bin/gitweb.cgi?p=yypkg/yypkg.git;a=blob;f=preprocess.sh
--
Adrien Nader
prev parent reply other threads:[~2010-12-21 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 1:05 orbitz
2010-12-21 2:25 ` [Caml-list] " Markus Mottl
2010-12-21 2:36 ` orbitz
2010-12-21 3:02 ` Michael Ekstrand
2010-12-21 18:42 ` orbitz
2010-12-22 1:55 ` Romain Beauxis
2010-12-21 8:57 ` Jérémie Dimino
2010-12-21 10:21 ` Sylvain Le Gall
2010-12-21 13:18 ` Adrien [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=AANLkTimypOALKtLabgGW8yM3xFaqWdybm_hZbyVtwPnG@mail.gmail.com \
--to=camaradetux@gmail.com \
--cc=caml-list@inria.fr \
/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).