From: Arne Babenhauserheide <arne_bab@web.de>
To: "Thompson\, David" <dthompson2@worcester.edu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] Lisparuga - a 2D shoot-em-up made for the Lisp Game Jam
Date: Wed, 11 May 2016 01:17:44 +0200 [thread overview]
Message-ID: <87k2j1y02v.fsf@web.de> (raw)
In-Reply-To: <CAJ=RwfY6JP6GuPZwSEcEKCYxxgz-C98qY4G+2ew4p6y8KnNFMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Thompson, David writes:
> It's a bit difficult to build right now if you don't use GNU Guix
This is actually a really cool usage of Guix — a meta-distribution for
reproducible builds of non-packaged software.
I have guix running on Gentoo, but I had to adjust the build instructions:
guix pull # I do not know whether this was required
cd lisparuga-0.1.0
guix environment --search-paths -l guix.scm
(execute the update of the search paths by copying the lines into the shell)
./configure
make
./pre-inst-env guile game.scm
However it fails at OpenGL:
sly/window.scm:100:20: In procedure init-window:
sly/window.scm:100:20: Throw to key `sdl-error' with args `("make-gl-context" "failed to create OpenGL context: ~A" "Could not create GL context: GLXBadFBConfig")'.
Now if Guix (the build daemon setup with per-user profiles) just came
pre-packaged for all distributions… that would massively simplify
sharing in-development software.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 298 bytes --]
next prev parent reply other threads:[~2016-05-10 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 17:43 [ANN] Lisparuga - a 2D shoot-em-up made for the Lisp Game Jam Thompson, David
2016-05-10 19:46 ` Nala Ginrut
2016-05-10 23:17 ` Arne Babenhauserheide [this message]
2016-05-19 11:46 ` Ludovic Courtès
2016-05-19 18:44 ` Thompson, David
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=87k2j1y02v.fsf@web.de \
--to=arne_bab@web.de \
--cc=dthompson2@worcester.edu \
--cc=guile-user@gnu.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.
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).