unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: HiPhish <hiphish@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Need help porting eDuke32
Date: Fri, 22 Feb 2019 11:57:31 +0100	[thread overview]
Message-ID: <871s40jdk4.fsf@ambrevar.xyz> (raw)
In-Reply-To: <8736ogjeis.fsf@ambrevar.xyz>

[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]

I needed to add a custom 'install phase:

--8<---------------cut here---------------start------------->8---
       (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))
         (replace 'install
           (lambda* (#:key outputs #:allow-other-keys)
             (let ((out (assoc-ref outputs "out")))
               ;; TODO: Install custom .desktop file?  Need icon.
               (install-file "eduke32" (string-append out "/bin"))
               (install-file "mapster32" (string-append out "/bin"))
               (install-file "package/common/buildlic.txt" (string-append out "/share/licenses"))))))
--8<---------------cut here---------------end--------------->8---

I can merge this in your name, let me know.

Playing Duke now!

"Hail to the king, baby!"

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-02-22 10:58 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
2019-02-22 10:36         ` Pierre Neidhardt
2019-02-22 10:57           ` Pierre Neidhardt [this message]
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

  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=871s40jdk4.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=help-guix@gnu.org \
    --cc=hiphish@posteo.de \
    /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).