From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: "41297@debbugs.gnu.org" <41297@debbugs.gnu.org>
Subject: [bug#41297] [PATCH] gnu: openctm: Correct inputs vs native-inputs
Date: Sat, 16 May 2020 10:24:47 +0000 [thread overview]
Message-ID: <IfPdXsGgkuTydGKCn5gYq9NI_DVU3o1Lwxu8PvrCMKldek1ENyBvZUGAEKm_a9gjcXeCu77lflrPMz_si3kypODt57fT3hSdd5VeNdIkB2g=@elenq.tech> (raw)
In-Reply-To: <2d2b1aee-69ac-76ec-fed5-00f478403ffe@web.de>
Hi,
> Ah, so it's the other way round. So move mesa, glu, glut and gtk+-2 to
> inputs.
Short and accurate. Thanks
Here it goes:
From 9e6f5503fd8837bcbb03eed3a05d6105b1752fc3 Mon Sep 17 00:00:00 2001
From: Ekaitz Zarraga <ekaitz@elenq.tech>
Date: Sat, 16 May 2020 12:22:09 +0200
Subject: [PATCH] gnu: openctm: Correct inputs vs native-inputs
* gnu/packages/engineering.scm (openctm): Move mesa, glu, glut and
gtk+-2 to inputs
---
gnu/packages/engineering.scm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/engineering.scm b/gnu/packages/engineering.scm
index aec692174a..aab414bf0e 100644
--- a/gnu/packages/engineering.scm
+++ b/gnu/packages/engineering.scm
@@ -2557,11 +2557,12 @@ official SDK.")
(base32 "01wb70m48xh5gwhv60a5brv4sxl0i0rh038w32cgnlxn5x86s9f1"))))
(build-system gnu-build-system)
(native-inputs
+ `(("pkg-config" ,pkg-config)))
+ (inputs
`(("mesa" ,mesa)
("glu" ,glu)
("glut" ,freeglut)
- ("gtk" ,gtk+-2)
- ("pkg-config" ,pkg-config)))
+ ("gtk" ,gtk+-2)))
(arguments
`(#:tests? #f ;no tests
#:phases
--
2.26.1
next prev parent reply other threads:[~2020-05-16 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 22:57 [bug#41297] [PATCH] gnu: openctm: Correct inputs vs native-inputs Ekaitz Zarraga
2020-05-15 23:35 ` Jonathan Brielmaier
2020-05-16 9:57 ` Ekaitz Zarraga
2020-05-16 10:06 ` Jonathan Brielmaier
2020-05-16 10:24 ` Ekaitz Zarraga [this message]
2020-05-16 17:24 ` Ludovic Courtès
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='IfPdXsGgkuTydGKCn5gYq9NI_DVU3o1Lwxu8PvrCMKldek1ENyBvZUGAEKm_a9gjcXeCu77lflrPMz_si3kypODt57fT3hSdd5VeNdIkB2g=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=41297@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.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.
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.