From: Jeremie Dimino <jeremie@dimino.org>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] Dune 1.0.0
Date: Wed, 11 Jul 2018 11:15:34 +0100 [thread overview]
Message-ID: <CAAUeRqXaSLO=Z8tW6nykhTfkcXomaHHOKSxHW3zswz8ts86nsQ@mail.gmail.com> (raw)
Dear caml-list,
It is my pleasure to announce the 1.0.0 release of Dune!
Dune is a built system for OCaml and Reason projects. It aims at
building things fast and providing a smooth user experience.
Dune 1.0.0 is now available on github [1] and in opam.
This is a big milestone for the project as it is the first release
using the new Dune name that the community helped to choose. Dune
started about a year and a half ago as the more narrow scoped Jbuilder
and as since then proven itself to be the right tool for the job.
A big part of the work for this release was preparing the project for
long-term support. Dune is the kind of project that will pretty much
continue to evolve forever: it needs to keep up with the OCaml
compiler evolving, development workflows changing, new kinds of tools
with specific needs, etc... While doing so, it also needs to offer
stability so that projects released now will continue to build with
future versions of Dune.
Meeting these two constraints is a challenge. However, we had to do
this for the renaming: we changed many things in Dune using what we
learned from the Jbuilder experience. Still, Dune is able to
understand and build Jbuilder projects. The mechanism used to support
both Jbuilder and Dune projects is fully generic and will be the basis
for future evolution.
You can find the full list of changes and bug fixes since Jbuilder
1.0+beta20 on the github release page [1]. Following is an overview of
some the new features:
- General cleanup of the syntax: less parentheses, better behaved variables
- Introduction of a `dune.configurator` library to help projects with
C stubs detect and query the environment
- General improvement of the default behavior: more parallelism by
default, development mode by default
- Better support for changing the defaults: it is now possible to set
the default flags or change what `dune build` does by default
- Support for setting the build directory
- Better support for expect-like tests on Windows
[1] https://github.com/ocaml/dune/releases/tag/1.0.0
--
Jeremie Dimino,
For the Dune team
--
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:[~2018-07-11 10:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAAUeRqXaSLO=Z8tW6nykhTfkcXomaHHOKSxHW3zswz8ts86nsQ@mail.gmail.com' \
--to=jeremie@dimino.org \
--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).