unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Cannot build guile-chickadee.
Date: Wed, 20 Jun 2018 14:37:42 +0200	[thread overview]
Message-ID: <87in6dtyzt.fsf@elephly.net> (raw)
In-Reply-To: <CAJ=Rwfb7fRBn+npvG+m_FXWwV1ZLB=s0mxG7sUfmf1-zcQZRWA@mail.gmail.com>


Hey Dave,

>> Turns out that the Makefile of guile-sdl2 needed to be patched.  After
>> the patch Chickadee can be built with the release tarball.
>>
>> I’ll push the package definition shortly.
>
> Could you tell me the commit id when you push it? I'd like to just
> sort out the issues you were having and make new releases of
> guile-sdl2 and chickadee so that Guix can have clean packages with no
> hackery involved.

I’ve pushed guile-chickadee with commit
00fca594da4c63a976e1c67ec3caab47f2a38d87.  The patch to guile-sdl2 is in
commit e5b77ccfe861545a61f6c6355f5c9fb712bc4894.  After that I noticed
that the package might also need a build phase to fix the installation
location:

--8<---------------cut here---------------start------------->8---
diff --git a/gnu/packages/game-development.scm b/gnu/packages/game-development.scm
index b428fa77f..f8c6583f9 100644
--- a/gnu/packages/game-development.scm
+++ b/gnu/packages/game-development.scm
@@ -1248,7 +1248,16 @@ a 2D editor view.")
                 "10qx0ha5gsayybd186r1my7vc7rf5fbzp9jvmc4xg9a8wz8rqhah"))))
     (build-system gnu-build-system)
     (arguments
-     '(#:make-flags '("GUILE_AUTO_COMPILE=0")))
+     '(#:make-flags '("GUILE_AUTO_COMPILE=0")
+       #:phases
+       (modify-phases %standard-phases
+         (add-after 'configure 'patch-makefile
+           (lambda _
+             ;; Install compiled Guile files in the expected place.
+             (substitute* '("Makefile")
+               (("^godir = .*$")
+                "godir = $(moddir)\n"))
+             #t)))))
     (propagated-inputs
      `(("guile-opengl" ,guile-opengl)
        ("guile-sdl2" ,guile-sdl2)))
--8<---------------cut here---------------end--------------->8---

Unfortunately, I still cannot use it as the example fails with OpenGL
errors, e.g.:

    chickadee/window.scm:56:21: In procedure open-window:
    Throw to key `sdl-error' with args `("make-window" "failed to create window: ~A" "Couldn't find matching GLX visual")'.

So I picked the first of the visuals that glxinfo outputs:

    export SDL_VIDEO_X11_VISUALID=0x022

But then I get another error:

    chickadee/window.scm:60:21: In procedure open-window:
    Throw to key `sdl-error' with args `("make-gl-context" "failed to create OpenGL context: ~A" "Could not create GL context")'.

And that’s probably because something somewhere decides that the
graphics chip in my Librem 13 does not support OpenGL 3.3(?), even
though glxinfo says this:

--8<---------------cut here---------------start------------->8---
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)  (0x1916)
    Version: 17.3.8
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
…
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.8
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
--8<---------------cut here---------------end--------------->8---

Not sure if this is a problem with my setup here.

Thanks for your help!

--
Ricardo

  reply	other threads:[~2018-06-20 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20  1:03 Cannot build guile-chickadee Ricardo Wurmus
2018-06-20  7:00 ` Pierre Neidhardt
2018-06-20  9:01   ` Ricardo Wurmus
2018-06-20  9:27     ` Ricardo Wurmus
2018-06-20 12:23       ` Thompson, David
2018-06-20 12:37         ` Ricardo Wurmus [this message]
2018-06-20 12:44           ` Thompson, David
2018-06-20 14:43 ` Joshua Branson

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=87in6dtyzt.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=dthompson2@worcester.edu \
    --cc=help-guix@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).