From: HiPhish <hiphish@posteo.de>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Need help porting eDuke32
Date: Thu, 21 Feb 2019 21:27:45 +0100 [thread overview]
Message-ID: <1778948.l3vIaAGMXl@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <87imxdj6ew.fsf@ambrevar.xyz>
Thank you for looking it this. I have done my own poking around and here is
the idea I came up with, after looking at how some other games were handling
SDL:
(arguments
`(#:phases
(modify-phases %standard-phases
(delete 'configure)
(add-after 'set-paths 'set-sdl-paths
;; The makefile adds the output of `sdl2-config --cflags` to the
;; compiler flags, but sdl2-config gives us the wrong directory to
;; include. We have to add the SDL2 header directory ourselves.
(lambda* (#:key inputs #:allow-other-keys)
(setenv "CPLUS_INCLUDE_PATH"
(string-append (assoc-ref inputs "sdl-union")
"/include/SDL2"
":"
(getenv "CPLUS_INCLUDE_PATH")))
#t))
(delete 'install))))
This seems cleaner to me than patching. I tested it with `guix build` and it
seems to work, but I won't have time until next week to look into it again.
On Thursday, 21 February 2019 20:19:35 CET you wrote:
> I've looked into this and found the culprit.
>
> > $ echo $C_INCLUDE_PATH
> > /gnu/store/x3r6c04n583q3fz7szm32ahycrxgfiz6-profile/include
>
> This is not correct. You should have a ":"-separated list of store items
> brom bzip2 to libxau.
>
> > $ sdl2-config --cflags
> > -I/gnu/store/4bhz5xzr39v0kgxf3ipv6kswicrdmkk4-sdl2-2.0.9/include/SDL2
>
> Indeed, sdl2-config should return the path to the union, not the sdl2
> package. SDL2_mixer is missing, which leads to the error.
>
> It seems to be an issue with sdl2-config. Any idea, anyone?
next prev parent reply other threads:[~2019-02-21 20:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 8:20 Need help porting eDuke32 HiPhish
2019-02-17 15:33 ` Pierre Neidhardt
2019-02-17 16:21 ` HiPhish
2019-02-21 19:19 ` Pierre Neidhardt
2019-02-21 19:22 ` Pierre Neidhardt
2019-02-21 19:27 ` Pierre Neidhardt
2019-02-21 20:27 ` HiPhish [this message]
2019-02-22 10:36 ` Pierre Neidhardt
2019-02-22 10:57 ` Pierre Neidhardt
2019-02-22 13:01 ` Pierre Neidhardt
2019-02-24 23:04 ` HiPhish
2019-02-25 16:09 ` Pierre Neidhardt
2019-02-25 17:51 ` Andreas Enge
2019-02-25 18:59 ` Giovanni Biscuolo
2019-02-26 9:57 ` Tobias Geerinckx-Rice
2019-02-26 10:00 ` Pierre Neidhardt
2019-02-26 11:18 ` HiPhish
2019-02-26 14:25 ` Ricardo Wurmus
2019-02-26 15:41 ` Jack Hill
2019-02-26 20:50 ` swedebugia
2019-02-24 23:00 ` HiPhish
-- strict thread matches above, loose matches on Subject: below --
2019-02-16 9:49 HiPhish
2019-02-16 10:30 ` Pierre Neidhardt
2019-02-16 12:15 ` nee
2019-02-16 12:20 ` Pierre Neidhardt
2019-02-16 16:45 ` Marius Bakke
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=1778948.l3vIaAGMXl@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.