From: "Hongbo Zhang (BLOOMBERG/ 731 LEX)" <hzhang295@bloomberg.net>
To: caml-list@inria.fr, Fabrice.Le_fessant@inria.fr
Subject: Re: [Caml-list] [ANN] BuckleScript 1.5 - First class support for Reason syntax
Date: Wed, 1 Mar 2017 17:37:16 -0000 [thread overview]
Message-ID: <58B706CC022E07F8003A03C6_0_1262411@p058> (raw)
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Not really, we developed a small utility to bundle all deps into a single file, it is quite useful,
we can bundle the whole OCaml compiler into a single file, the same applies to Reason and BuckleScript. Then it is super easy to pre-built a windows image, and BuckleScript toolchain does not need c++ toolchain(linker), so from user's point of view, it is just one click style.
We have our own blazing fast build system(powered by Ninja) which is also heavily tested on Windows without Cygwin.
From: Fabrice.Le_fessant@inria.fr At: 03/01/17 12:26:44
To: HONGBO ZHANG (BLOOMBERG/ 731 LEX), caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] BuckleScript 1.5 - First class support for Reason syntax
On Wed, Mar 1, 2017 at 5:56 PM Hongbo Zhang (BLOOMBERG/ 731 LEX) <hzhang295@bloomberg.net> wrote:
I don't know exactly why it did not work on windows(maybe due to some bashism?). Our solution is very clean, no dependencies on Cygwin or MSVC : )
You compile BuckleScript to JS and then use some JS-engine (node.js ?) to run it ?
--Fabrice
[-- Attachment #2: Type: text/html, Size: 3125 bytes --]
next reply other threads:[~2017-03-01 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 17:37 Hongbo Zhang (BLOOMBERG/ 731 LEX) [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-01 16:56 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-03-01 17:26 ` Fabrice Le Fessant
2017-02-28 15:34 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-03-01 8:30 ` Fabrice Le Fessant
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=58B706CC022E07F8003A03C6_0_1262411@p058 \
--to=hzhang295@bloomberg.net \
--cc=Fabrice.Le_fessant@inria.fr \
--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).