From: Basile Starynkevitch <basile@starynkevitch.net>
To: guile-user@gnu.org
Cc: Andy Tai <atai@atai.org>, Olivier Dion <olivier.dion@polymtl.ca>
Subject: Re: guile or scheme used to implement make or meson
Date: Tue, 12 Sep 2023 17:20:01 +0200 [thread overview]
Message-ID: <3cd636d9-5be9-4060-abe3-542df4a41672@starynkevitch.net> (raw)
In-Reply-To: <87cyyntrzg.fsf@laura>
On 9/12/23 15:56, Olivier Dion wrote:
> On Mon, 11 Sep 2023, Andy Tai <atai@atai.org> wrote:
>> Is using Guile, or a similar Scheme implementation, to re-implement
>> make or meson realistic?
> By re-implementing do you mean re-writing Make with Guile? That ought
> to be realistic, but I really do not see the point of it.
>
> What is more realistic and useful is to make a build system in Guile
> where the DSL that replaces Makefiles is Scheme.
>
>
I think this already exist in GNU make. Recent versions of it can be
extended in GNU guile:
https://www.gnu.org/software/make/manual/html_node/Guile-Function.html
BTW, my pet open source project (which uses GNU make without the guile
extension) is the RefPerSys open source inference engine project (mostly
coded in C++, with the ambition to generate C++ code or machine code
thru GNU lightning), see https://github.com/RefPerSys/RefPerSys/ (and
amateurish website http://refpersys.org/ ....). Contributors are welcome.
Regards from near Paris in France.
--
Basile Starynkevitch <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
next prev parent reply other threads:[~2023-09-12 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 18:42 guile or scheme used to implement make or meson Andy Tai
[not found] ` <2061904033.101273.1694496696500@mail.yahoo.com>
2023-09-12 12:39 ` Fw: " Mike Gran
2023-09-12 13:56 ` Olivier Dion
2023-09-12 14:10 ` Vivien Kraus
2023-09-12 15:20 ` Basile Starynkevitch [this message]
2023-09-12 16:04 ` Olivier Dion
2023-09-13 0:47 ` Maxime Devos
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cd636d9-5be9-4060-abe3-542df4a41672@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=atai@atai.org \
--cc=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).