all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Olivier Dion via <gwl-devel@gnu.org>
To: gwl-devel@gnu.org
Subject: GWL as a build-automation
Date: Sun, 05 Jun 2022 18:21:32 -0400	[thread overview]
Message-ID: <871qw2ycnn.fsf@laura> (raw)

Hi,

I've been hacking around for the past weeks on a build system that uses
Guix.  The more I write it, the more I find similarities with what GWL
already does/provides.


So I'm thinking, one could easily do something like this for a simple
Guile project:

--8<---------------cut here---------------start------------->8---
process compile-guile-source (with dot-scm)
  package "guile"
  inputs  : file dot-scm
  outputs : file : string-replace-substring dot-scm ".scm" ".go"
  # {
    guild compile --output {{outputs}} {{inputs}}
  }
--8<---------------cut here---------------end--------------->8---

And this could also be done for other projects, e.g.:

--8<---------------cut here---------------start------------->8---
process compile-c-source (with dot-c)
  package "gcc-toolchain"
  inputs  : file dot-c
  outputs : file : string-replace-substring dot-c ".c" ".o"
  # {
    gcc -c -o {{outputs}} {{inputs}}
  }
--8<---------------cut here---------------end--------------->8---


I know that GWL focuses on scientific workflows, but I think that it can
go beyond its original goal.

Thoughts?

-- 
Olivier Dion
oldiob.dev



             reply	other threads:[~2022-06-05 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 22:21 Olivier Dion via [this message]
2022-06-06  8:50 ` GWL as a build-automation Ricardo Wurmus
2022-08-18 15:00   ` zimoun

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=871qw2ycnn.fsf@laura \
    --to=gwl-devel@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.