From: moosotc@gmail.com
To: Tuncer Ayaz <tuncer.ayaz@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] llpp v23
Date: Tue, 22 Nov 2016 09:57:54 +0300 [thread overview]
Message-ID: <87twb0xaq5.fsf@gmail.com> (raw)
In-Reply-To: <CAOvwQ4j4S=6quTF0dmA=J_-4Jpx+f1bMnBRGFx3VW24=XTD9TA@mail.gmail.com> (Tuncer Ayaz's message of "Tue, 22 Nov 2016 04:12:57 +0100")
Tuncer Ayaz <tuncer.ayaz@gmail.com> writes:
> On 21 November 2016 at 16:49, <moosotc@gmail.com> wrote:
>>
>> Hello,
>>
>> New version of llpp (tagged v23) is now available at:
>> * http://repo.or.cz/w/llpp.git (has "tutorial" videos)
>> * https://github.com/moosotc/llpp/ (has a bugtracker)
>
> [...]
>
>> Diffstat v22..v23
>> .dir-locals.el | 2 +-
>> .gitignore | 5 +-
>> BUILDING | 10 +-
>> KEYS | 9 +-
>> Build.hs => Shakefile.hs | 103 ++--
>
> I like and use Shake myself, but I wish we could use Jenga instead of
> Shake in order to limit the needed toolchains at build time. However,
> it seems that for the moment macOS and Windows support would be
> problematic if we relied on Jenga, if I remember moosotc's explanation
> correctly. I don't have access to Windows or macOS, so the only
> problem I know is that polling mode isn't implemented on macOS, which
> is only important for regular developers of llpp and if they're primarily
> working on macOS.
>
Argh... This double build system bites again (I don't
use/test-well-enough the non-shake one) strikes again, fixed now in:
http://repo.or.cz/llpp.git/commitdiff/26f6396e0bfe5455fcac57e596a1dfd42b09c4e8
--
mailto:moosotc@gmail.com
prev parent reply other threads:[~2016-11-22 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 15:49 moosotc
[not found] ` <CAOvwQ4j4S=6quTF0dmA=J_-4Jpx+f1bMnBRGFx3VW24=XTD9TA@mail.gmail.com>
2016-11-22 4:22 ` moosotc
2016-11-22 6:57 ` moosotc [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=87twb0xaq5.fsf@gmail.com \
--to=moosotc@gmail.com \
--cc=caml-list@inria.fr \
--cc=tuncer.ayaz@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).