From: "Benda XU" <heroxbd@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/glew/
Date: Thu, 18 Jan 2018 05:18:05 +0000 (UTC) [thread overview]
Message-ID: <1516252677.f0fabf890886dab370d14e091e97de28db01c200.heroxbd@gentoo> (raw)
commit: f0fabf890886dab370d14e091e97de28db01c200
Author: Benda Xu <heroxbd <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 18 05:14:36 2018 +0000
Commit: Benda XU <heroxbd <AT> gentoo <DOT> org>
CommitDate: Thu Jan 18 05:17:57 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f0fabf89
media-libs/glew: define GLEW_PREFIX to be used in glew.pc.
This makes glew.pc Prefix-aware.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
media-libs/glew/glew-2.1.0.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/media-libs/glew/glew-2.1.0.ebuild b/media-libs/glew/glew-2.1.0.ebuild
index 3ddebf5f830..f003f13e40c 100644
--- a/media-libs/glew/glew-2.1.0.ebuild
+++ b/media-libs/glew/glew-2.1.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -78,6 +78,7 @@ set_opts() {
multilib_src_compile() {
set_opts
emake \
+ GLEW_PREFIX="${EPREFIX}/usr" \
GLEW_DEST="${EPREFIX}/usr" \
LIBDIR="${EPREFIX}/usr/$(get_libdir)" \
"${myglewopts[@]}"
next reply other threads:[~2018-01-18 5:18 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 5:18 Benda XU [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-30 3:04 [gentoo-commits] repo/gentoo:master commit in: media-libs/glew/ Sam James
2023-12-30 3:04 Sam James
2023-12-30 3:04 Sam James
2023-12-30 3:04 Sam James
2023-12-30 3:04 Sam James
2023-08-28 16:14 James Le Cuirot
2023-08-28 16:14 James Le Cuirot
2023-08-28 16:14 James Le Cuirot
2023-07-02 20:28 James Le Cuirot
2023-06-10 10:25 Sam James
2022-08-28 5:06 WANG Xuerui
2021-07-14 16:15 Marek Szuba
2021-03-16 21:28 Sam James
2021-03-16 20:21 Sam James
2021-03-16 20:21 Sam James
2020-07-27 13:54 Sam James
2020-07-25 11:16 Sam James
2020-07-25 8:42 Sergei Trofimovich
2020-07-24 14:32 Sam James
2020-07-24 11:54 Sam James
2020-07-24 7:17 Sam James
2020-05-07 12:42 Lars Wendler
2019-05-20 17:22 Aaron Bauman
2019-02-10 11:51 Mikle Kolyada
2019-02-10 11:51 Mikle Kolyada
2019-02-10 11:51 Mikle Kolyada
2019-02-10 11:51 Mikle Kolyada
2019-02-02 21:17 Sergei Trofimovich
2019-02-02 19:18 Sergei Trofimovich
2019-02-01 14:55 Tobias Klausmann
2019-01-28 19:38 Sergei Trofimovich
2018-10-01 20:55 Andreas Sturmlechner
2018-10-01 20:55 Andreas Sturmlechner
2018-05-30 16:10 Mikle Kolyada
2018-04-21 8:56 Mikle Kolyada
2018-04-07 21:30 Sergei Trofimovich
2018-03-31 17:52 Tobias Klausmann
2018-03-18 12:25 Mikle Kolyada
2018-03-18 11:15 Sergei Trofimovich
2018-03-17 12:17 Sergei Trofimovich
2017-08-04 0:43 Tim Harder
2017-05-05 19:10 Markus Meier
2017-04-23 12:40 Agostino Sarubbo
2017-04-22 7:33 Tobias Klausmann
2017-04-19 6:52 Jeroen Roovers
2017-04-01 22:42 Andreas Sturmlechner
2017-04-01 22:42 Andreas Sturmlechner
2017-04-01 22:42 Andreas Sturmlechner
2017-01-04 19:41 Zac Medico
2016-12-09 22:45 Mike Frysinger
2016-08-10 15:21 James Le Cuirot
2016-07-24 21:23 James Le Cuirot
2016-07-24 21:23 James Le Cuirot
2016-04-12 5:57 Tim Harder
2015-08-25 4:31 Tim Harder
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=1516252677.f0fabf890886dab370d14e091e97de28db01c200.heroxbd@gentoo \
--to=heroxbd@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