all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Pierre-Henry Fröhring" <contact@phfrohring.com>
To: paren@disroot.org, help-guix@gnu.org
Subject: Re: Packaging Idris2
Date: Sat, 20 Aug 2022 02:11:33 +0200	[thread overview]
Message-ID: <a545610c6174979d69516ab5f7c1377eb4c6a97f.camel@phfrohring.com> (raw)
In-Reply-To: <CMA9OO37L00I.9Y9WGCFQ2C8Q@guix-aspire>

Well, I went from a `guix shell --container' up to `make test' passing ;
assuming a `chez-scheme' backend (no `node' nor `racket'). It boils down
to a shell session looking like:

┌────
│ $ cd ~/src/
│ $ git clone git@github.com:idris-lang/Idris2.git
│ $ cd Idris2
│ $ ./build_idris
└────
Listing 1: session

I guess that an idea would be to « translate » this session into a Guix
Package. What's the best option here? To torture the `gnu-build-system'
until it accepts to build Idris2 or should I take the
`trivial-build-system' route?
Thank you.
― PHF

┌────
│ #! /usr/bin/env bash
│ set -euo pipefail
│ IFS=$'\n\t'
│ 
│ cat <<'EOF' >manifest.scm
│ (specifications->manifest
│  '("gcc@12.1.0"
│    "chez-scheme"
│    "gmp"
│    "coreutils"
│    "bash"
│    "make"
│    "findutils"
│    "git"
│    "diffutils"
│    "glibc"
│    "sed"
│    "gawk"
│    "binutils"))
│ EOF
│ 
│ cat <<'EOF' >build_idris_in_container
│ set -euo pipefail
│ IFS=$'\n\t'
│ 
│ echo 'Idris build configuration'
│ set -x
│ export PREFIX=/tmp/idris2
│ export SCHEME=chez-scheme
│ export CC=gcc
│ export INTERACTIVE=''
│ set +x
│ echo
│ 
│ echo 'PATHS configuration'
│ set -x
│ export LD_LIBRARY_PATH=$GUIX_ENVIRONMENT/lib:$PREFIX/lib
│ export PATH=$PATH:$PREFIX/bin
│ set +x
│ echo
│ 
│ echo 'Bootstrap'
│ make bootstrap
│ echo
│ 
│ echo 'Install'
│ make install
│ echo
│ 
│ echo 'Self-host'
│ make clean
│ make all
│ make install
│ echo
│ 
│ echo 'Test'
│ make test
│ echo
│ 
│ echo 'Clean'
│ rm -v manifest.scm
│ rm -v build_idris_in_container
│ echo
│ EOF
│ 
│ guix shell -C -m manifest.scm -- bash ./build_idris_in_container
└────
Listing 2: build_idris




  reply	other threads:[~2022-08-20  8:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 15:42 Packaging Idris2 Pierre-Henry Fröhring
2022-08-19 19:54 ` (
2022-08-20  0:11   ` Pierre-Henry Fröhring [this message]
2022-08-20 18:42     ` Csepp
2022-08-20 22:01       ` Andreas Reuleaux
2022-08-21  7:31         ` (
2022-08-21  8:42           ` Csepp
2022-08-21 10:21           ` Andreas Reuleaux
2022-08-21 10:39             ` (
2022-08-21 10:41               ` (
2022-08-21 12:31               ` zimoun
2022-08-21 23:40                 ` Philip McGrath
2022-08-23  7:56                   ` contact
2022-08-23 11:39                     ` Csepp
2022-08-23 13:02                       ` contact

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=a545610c6174979d69516ab5f7c1377eb4c6a97f.camel@phfrohring.com \
    --to=contact@phfrohring.com \
    --cc=help-guix@gnu.org \
    --cc=paren@disroot.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.
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.