From: HiPhish <hiphish@posteo.de>
To: help-guix@gnu.org
Subject: Re: Need help porting eDuke32
Date: Sun, 17 Feb 2019 09:20:25 +0100 [thread overview]
Message-ID: <4082254.2VInIakpOu@aleksandar-ixtreme-m5740> (raw)
I have found the problem thanks to one of the eDuke32 developers. Here is the
issue:
$ echo $C_INCLUDE_PATH
/gnu/store/x3r6c04n583q3fz7szm32ahycrxgfiz6-profile/include
Compare this value to
$ sdl2-config --cflags
-I/gnu/store/4bhz5xzr39v0kgxf3ipv6kswicrdmkk4-sdl2-2.0.9/include/SDL2
They point to different entries in the store. And the store entry provided by
sdl2-config does not contain the header file for SDL Mixer (obviously, since
that one is pointing to the store entry of one package instead of a profile). I
am already using sdl-union as my input:
("sdl-union" ,(sdl-union (list sdl2 sdl2-mixer)))
The makefile uses the output of sdl2-config as part of the compiler flags, so the
include path points into the wrong directory. Is there a way to get sdl2-config
to print the correct path?
next reply other threads:[~2019-02-17 8:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 8:20 HiPhish [this message]
2019-02-17 15:33 ` Need help porting eDuke32 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
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=4082254.2VInIakpOu@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--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.
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.