From: "Stefan Strogin" <steils@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/glfw/
Date: Tue, 16 Jun 2020 14:33:35 +0000 (UTC) [thread overview]
Message-ID: <1592317957.ab46580d900aec6a1627f1fad4f41890fbbd88db.steils@gentoo> (raw)
commit: ab46580d900aec6a1627f1fad4f41890fbbd88db
Author: Stefan Strogin <steils <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 16 14:30:51 2020 +0000
Commit: Stefan Strogin <steils <AT> gentoo <DOT> org>
CommitDate: Tue Jun 16 14:32:37 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab46580d
media-libs/glfw: move x11-libs/libXi from BDEPEND to DEPEND
When cross-compiling, these headers should be on CHOST, not CBUILD.
Bug: https://bugs.gentoo.org/722186
Package-Manager: Portage-2.3.101, Repoman-2.3.22
Signed-off-by: Stefan Strogin <steils <AT> gentoo.org>
media-libs/glfw/glfw-3.3.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-libs/glfw/glfw-3.3.2.ebuild b/media-libs/glfw/glfw-3.3.2.ebuild
index 344e650b9d6..8639de154da 100644
--- a/media-libs/glfw/glfw-3.3.2.ebuild
+++ b/media-libs/glfw/glfw-3.3.2.ebuild
@@ -31,10 +31,10 @@ RDEPEND="
"
DEPEND="
${RDEPEND}
+ !wayland? ( x11-libs/libXi )
wayland? ( dev-libs/wayland-protocols )
"
BDEPEND="
- !wayland? ( x11-libs/libXi )
wayland? ( kde-frameworks/extra-cmake-modules )
"
next reply other threads:[~2020-06-16 14:33 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 14:33 Stefan Strogin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-27 1:48 [gentoo-commits] repo/gentoo:master commit in: media-libs/glfw/ Sam James
2024-05-04 21:13 James Le Cuirot
2024-05-04 21:13 James Le Cuirot
2024-01-20 12:23 Sam James
2024-01-20 12:23 Sam James
2023-03-09 20:13 Ionen Wolkens
2023-03-04 8:34 Arthur Zamarin
2023-03-04 6:29 Arthur Zamarin
2022-08-11 7:37 Ionen Wolkens
2022-07-22 14:41 Ionen Wolkens
2022-04-05 22:26 Sam James
2022-02-28 7:06 Yixun Lan
2021-12-28 17:10 Ionen Wolkens
2021-12-10 4:36 Sam James
2021-11-28 22:18 Ionen Wolkens
2021-10-30 3:55 Ionen Wolkens
2021-10-04 21:00 Ionen Wolkens
2021-09-19 6:07 Ionen Wolkens
2021-07-29 3:09 Ionen Wolkens
2021-07-29 3:09 Ionen Wolkens
2021-07-29 3:09 Ionen Wolkens
2021-07-29 3:09 Ionen Wolkens
2021-06-30 2:49 Ionen Wolkens
2021-06-30 2:49 Ionen Wolkens
2021-06-13 11:12 Sam James
2021-06-13 11:12 Sam James
2021-04-25 20:07 Sam James
2021-04-25 20:07 Sam James
2021-03-26 16:17 Agostino Sarubbo
2021-03-26 15:06 Agostino Sarubbo
2021-02-24 16:22 Sam James
2021-02-14 21:05 Andreas Sturmlechner
2021-01-25 14:16 Sam James
2020-10-15 15:58 Sam James
2020-06-16 10:39 Stefan Strogin
2020-06-16 10:39 Stefan Strogin
2020-01-08 23:22 James Le Cuirot
2020-01-08 23:22 James Le Cuirot
2020-01-08 23:22 James Le Cuirot
2019-02-27 20:45 James Le Cuirot
2017-09-16 12:27 Andreas Sturmlechner
2017-05-31 7:12 Lars Wendler
2017-05-31 7:12 Lars Wendler
2017-05-06 17:20 Agostino Sarubbo
2017-05-06 10:05 Jeroen Roovers
2017-05-05 14:10 Agostino Sarubbo
2017-01-29 22:35 Michael Weber
2016-11-01 15:14 Lars Wendler
2016-10-31 22:39 Lars Wendler
2016-04-10 8:45 Jeroen Roovers
2016-03-20 20:53 Michael Sterrett
2016-01-19 3:50 Michael Sterrett
2016-01-09 10:11 Jeroen Roovers
2015-09-21 15:38 Michael Sterrett
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=1592317957.ab46580d900aec6a1627f1fad4f41890fbbd88db.steils@gentoo \
--to=steils@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox