From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: common/build-style: add `dune` (OCaml builder)
Date: Mon, 06 Jun 2022 04:14:21 +0200 [thread overview]
Message-ID: <20220606021421.-RS6zmkWUnwj_F0X4jac4DKFbDHjOCZCTueerJ3Eoh8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31601@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
There's a closed pull request on the void-packages repository
common/build-style: add `dune` (OCaml builder)
https://github.com/void-linux/void-packages/pull/31601
Description:
<!-- Mark items with [x] where applicable -->
This PR defines a `dune.sh` build style to streamline OCaml builds using the [Dune](https://dune.build) builder. Its purpose is analogous to the `cargo` build style for Rust projects, or `python3-module` build style for Python setup.py projects, etc.
As an example showing how it works, I've also added `ocaml-sexplib0` (a common sexp library for OCaml), which builds using `build_style=dune`.
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
prev parent reply other threads:[~2022-06-06 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 0:34 [PR PATCH] New package: dune-2.8.5 (OCaml build system), `dune` build-style kwshi
2021-06-22 0:36 ` [PR PATCH] [Updated] " kwshi
2021-06-22 0:57 ` kwshi
2021-06-22 1:02 ` kwshi
2021-06-22 2:18 ` kwshi
2021-06-22 2:34 ` kwshi
2021-06-22 2:36 ` kwshi
2021-06-22 2:41 ` kwshi
2021-06-22 2:45 ` kwshi
2021-06-22 2:54 ` [PR PATCH] [Updated] New package: dune-2.8.5 (OCaml builder), " kwshi
2021-06-22 19:56 ` kwshi
2021-12-30 1:46 ` kwshi
2022-05-23 2:12 ` common/build-style: add `dune` (OCaml builder) github-actions
2022-06-06 2:14 ` github-actions [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=20220606021421.-RS6zmkWUnwj_F0X4jac4DKFbDHjOCZCTueerJ3Eoh8@z \
--to=ml@inbox.vuxu.org \
/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).