From: Roma Sokolov <sokolov.r.v@gmail.com>
To: Martin DeMello <martindemello@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] converting ocaml libraries to bucklescript
Date: Fri, 14 Oct 2016 13:17:26 +0300 [thread overview]
Message-ID: <01D4C4EC-31B8-45B2-BB97-F944D8B6BEF8@gmail.com> (raw)
In-Reply-To: <CAFrFfuFbMyeUf0sR5q-hfdRpnN3SJFhrOfL96S8bARgS3DNKCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi Martin,
Just for the record — there is an issue about this on github — https://github.com/bloomberg/bucklescript/issues/706 <https://github.com/bloomberg/bucklescript/issues/706>.
As far as I understand, currently there is no other way apart from what you’ve described.
Roma
> On 13 Oct 2016, at 21:59, Martin DeMello <martindemello@gmail.com> wrote:
>
> Hi,
>
> I'm just starting to explore bucklescript, and from what I can gather, any libraries you want to use with it have to be checked out as source and compiled via bucklescript too. What are other people doing - copying sources into their project tree and compiling in one go, or compiling the libraries as separate npm packages and then depending on them?
>
> I found https://github.com/npm-ml <https://github.com/npm-ml> but there are very few libraries in there, and when I looked at yojson it just seemed to be a fork of the main project with no changes. Is there some other place people are collecting libraries they have converted to npm, or forked and added bucklescript build files for?
>
> martin
[-- Attachment #2: Type: text/html, Size: 1925 bytes --]
next prev parent reply other threads:[~2016-10-14 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 18:59 Martin DeMello
2016-10-14 10:17 ` Roma Sokolov [this message]
2016-10-14 14:04 Hongbo Zhang (BLOOMBERG/ 731 LEX)
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=01D4C4EC-31B8-45B2-BB97-F944D8B6BEF8@gmail.com \
--to=sokolov.r.v@gmail.com \
--cc=caml-list@inria.fr \
--cc=martindemello@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).