caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Hongbo Zhang (BLOOMBERG/ 731 LEX)" <hzhang295@bloomberg.net>
To: martindemello@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] converting ocaml libraries to bucklescript
Date: Fri, 14 Oct 2016 14:04:14 -0000	[thread overview]
Message-ID: <5800E5DE0062027600390448_0_26068@msclnjpmsgsv02> (raw)

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

Hi Martin, we are working on a build tool for BuckleScript, 
it should come out soon. At the same time, we will support OPAM in the future, there are some technical challenges: in JS world, ES6 module system is path sensitive, so we might only support google module system under OPAM -- Hongbo
From: martindemello@gmail.com At: 10/13/16 15:00:00
To: caml-list@inria.fr
Subject: Re:[Caml-list] converting ocaml libraries to bucklescript

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 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: 2977 bytes --]

             reply	other threads:[~2016-10-14 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 14:04 Hongbo Zhang (BLOOMBERG/ 731 LEX) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-13 18:59 Martin DeMello
2016-10-14 10:17 ` Roma Sokolov

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=5800E5DE0062027600390448_0_26068@msclnjpmsgsv02 \
    --to=hzhang295@bloomberg.net \
    --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).