From: HiPhish <hiphish@posteo.de>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Need help porting eDuke32
Date: Sun, 17 Feb 2019 17:21:36 +0100 [thread overview]
Message-ID: <3942569.6XaQy4PdK7@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <87pnrqxwdm.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
On Sunday, 17 February 2019 16:33:41 CET you wrote:
> Can you share your package definition?
Sure, I posted the abridged version in the OP, here is the complete definition:
(define-public eduke32
(package
(name "eduke32")
(version "20181027-7136")
(source
(origin
(method url-fetch)
(uri (string-append "http://dukeworld.duke4.net/eduke32/synthesis/"
version
"/eduke32_src_"
version
".tar.xz"))
(sha256
(base32 "121k2k7ylw8dvs71mrdy7hwb1a2xd5di7jdqc20a1ml5k0n9akpn"))))
(build-system gnu-build-system)
(arguments
`(#:tests? #f
#:phases
(modify-phases %standard-phases
(delete 'configure)
(delete 'install))))
(native-inputs
`(("pkg-config" ,pkg-config)))
(inputs
`(("sdl-union" ,(sdl-union (list sdl2 sdl2-mixer)))
("glu" ,glu)
("libvorbis" ,libvorbis)
("libvpx" ,libvpx)
("flac" ,flac)
("gtk+" ,gtk+-2)))
(synopsis "Source port of the classic PC first person shooter Duke Nukem
3D")
(description "EDuke32 is an awesome, free homebrew game engine and source
port of the
classic PC first person shooter Duke Nukem 3D—Duke3D for short—to Windows,
Linux, Mac OS X, FreeBSD, several handhelds, your family toaster, and to your
girlfriend's vibrator. We've added thousands of cool and useful features and
upgrades for regular players and additional editing capabilities and scripting
extensions for homebrew developers and mod creators. EDuke32 is open source
software that is completely free to use for all non-commercial purposes.")
(home-page "http://eduke32.com/")
(license (list gpl2))))
> Are you running those two commands from the build environment?
Yes, from within the same build environment. I executed `guix environment --
pure --load=eduke32.scm` from within the source code directory and ran the
commands in the new shell. If I understand the user manual correctly, this
should set up an environment in which all dependencies (inputs) declared in
the package definition are set up, and nothing else. Is this correct?
[-- Attachment #2: eduke32.scm --]
[-- Type: text/x-scheme, Size: 2569 bytes --]
#!/usr/local/bin/guile
!#
(define-module (games eduke32)
#:use-module ((guix packages)
#:select (package origin base32))
#:use-module ((guix download)
#:select (url-fetch))
#:use-module ((guix licenses) #:select (gpl2))
#:use-module ((guix build-system gnu) #:select (gnu-build-system))
#:use-module ((guix build-system trivial) #:select (trivial-build-system))
;; Inputs
#:use-module ((gnu packages sdl)
#:select (sdl-union sdl2 sdl2-mixer))
#:use-module ((gnu packages gl)
#:select (glu))
#:use-module ((gnu packages pkg-config)
#:select (pkg-config))
#:use-module ((gnu packages xiph)
#:select (libvorbis flac))
#:use-module ((gnu packages video)
#:select (libvpx))
#:use-module ((gnu packages gtk)
#:select (gtk+-2)))
(define-public eduke32
(package
(name "eduke32")
(version "20181027-7136")
(source
(origin
(method url-fetch)
(uri (string-append "http://dukeworld.duke4.net/eduke32/synthesis/"
version
"/eduke32_src_"
version
".tar.xz"))
(sha256
(base32 "121k2k7ylw8dvs71mrdy7hwb1a2xd5di7jdqc20a1ml5k0n9akpn"))))
(build-system gnu-build-system)
(arguments
`(#:tests? #f
#:phases
(modify-phases %standard-phases
(delete 'configure)
(delete 'install))))
(native-inputs
`(("pkg-config" ,pkg-config)))
(inputs
`(("sdl-union" ,(sdl-union (list sdl2 sdl2-mixer)))
("glu" ,glu)
("libvorbis" ,libvorbis)
("libvpx" ,libvpx)
("flac" ,flac)
("gtk+" ,gtk+-2)))
(synopsis "Source port of the classic PC first person shooter Duke Nukem 3D")
(description "EDuke32 is an awesome, free homebrew game engine and source port of the
classic PC first person shooter Duke Nukem 3D—Duke3D for short—to Windows,
Linux, Mac OS X, FreeBSD, several handhelds, your family toaster, and to your
girlfriend's vibrator. We've added thousands of cool and useful features and
upgrades for regular players and additional editing capabilities and scripting
extensions for homebrew developers and mod creators. EDuke32 is open source
software that is completely free to use for all non-commercial purposes.")
(home-page "http://eduke32.com/")
(license (list gpl2))))
eduke32
next prev parent reply other threads:[~2019-02-17 16:21 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 [this message]
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
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=3942569.6XaQy4PdK7@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.
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).