unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Blake Shaw <blake@reproduciblemedia.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: jgart <jgart@dismail.de>, guix-devel@gnu.org
Subject: Re: Can zig-build-system  be an alternative to the gnu-build-system?
Date: Wed, 01 Feb 2023 22:37:03 +0700	[thread overview]
Message-ID: <7zzg9x1jj5.fsf@reproduciblemedia.com> (raw)
In-Reply-To: <20230201101127.eiq7unzgdbzidnky@thebird.nl>


This has reminded me of Make's built-in support for guile[1].

I've assumed that the fact that we don't use it means that it
probably depends on an earlier guile, as many projects many
that support "guile scripting" typically depend on ~v1.8; but
that is just an assumption.

Does anyone know what its status is?

[1] https://www.gnu.org/software/make/manual/html_node/Guile-Integration.html

Pjotr Prins <pjotr.public12@thebird.nl> writes:

> Hi jgart,
>
> zig as a build system is nice, but it is llvm bound and only targets
> zig and C/C++. It does not handle packages, and that is a feature in
> my book ;). Mind they are planning to go down the packaging route,
> from what I can tell.
>
> There have been some older discussions about creating our own
> replacement for autotools, cmake and others. I often fight these make
> make systems - and meson and/or language specific build systems. It is
> a time waster for programmers and none of these systems leverages the
> power of Guix itself. I kinda settled for cmake because, even though
> it is an effing dragon, at least I can make it work (pun intended).
>
> We need someone with deep experience in build systems to write a guile
> replacement - generating ninja is one idea. That is my opinion :). I
> would love a simple way to describe a project in guile. It should not
> be too hard actually (famously that is how these projects start and
> turn out to be a real time sink). Maybe someone wants to try with
> guidance from us, or maybe we can do it when we get bored some day.
>
> Pj.
>
> On Fri, Jan 27, 2023 at 02:03:06AM +0000, jgart wrote:
>> Can `zig-build-system` be an alternative to the `gnu-build-system`? 
>> 
>> https://ziglang.org/learn/why\_zig\_rust\_d\_cpp/#a-package-manager-and-build-system-for-existing-projects
>> 
>> > Not only can you write Zig code instead of C or C++ code, but you
>> can use Zig as a replacement for autotools, cmake, make, scons,
>> ninja, etc. And on top of this, it (will) provide a package manager
>> for native dependencies. This build system is intended to be
>> appropriate even if the entirety of a project’s codebase is in C or
>> C++.
>> 
>> WDYT
>> 



  reply	other threads:[~2023-02-02 14:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  2:03 Can zig-build-system be an alternative to the gnu-build-system? jgart
2023-02-01 10:11 ` Pjotr Prins
2023-02-01 15:37   ` Blake Shaw [this message]
2023-02-02 17:52   ` Philip McGrath
2023-02-02 18:33     ` zuo build system; formerly: " Pjotr Prins
2023-02-01 14:31 ` Ekaitz Zarraga
2023-02-01 15:45 ` jgart
2023-02-01 15:47   ` Ekaitz Zarraga
2023-02-01 15:51   ` jgart
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01 22:46 Nathan Dehnel

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7zzg9x1jj5.fsf@reproduciblemedia.com \
    --to=blake@reproduciblemedia.com \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=pjotr.public12@thebird.nl \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).