From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/libjson-rpc-cpp/
Date: Tue, 24 May 2016 11:23:15 +0000 (UTC) [thread overview]
Message-ID: <1464088988.caedf91905a8eda88d6937220f2541144c7c6ac4.mgorny@gentoo> (raw)
commit: caedf91905a8eda88d6937220f2541144c7c6ac4
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Tue May 24 11:12:01 2016 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Tue May 24 11:23:08 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=caedf919
dev-cpp/libjson-rpc-cpp: Update deps & build args for live version
Update the live ebuild. Use dev-cpp/catch for tests. Work-around test
build failure by enabling examples. Bump to EAPI 6.
The package still fails to build because of Debian multiarch support
breaking multilib: https://github.com/cinemast/libjson-rpc-cpp/pull/161.
dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-9999.ebuild | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-9999.ebuild b/dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-9999.ebuild
index abbdc45..967818a 100644
--- a/dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-9999.ebuild
+++ b/dev-cpp/libjson-rpc-cpp/libjson-rpc-cpp-9999.ebuild
@@ -1,10 +1,10 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
-EAPI=5
+EAPI=6
-EGIT_REPO_URI="https://github.com/cinemast/${PN}"
+EGIT_REPO_URI="https://github.com/cinemast/${PN}.git"
EGIT_BRANCH=develop
inherit cmake-utils git-r3
@@ -24,16 +24,17 @@ RDEPEND="
stubgen? ( dev-libs/argtable:= )"
DEPEND="${RDEPEND}
doc? ( app-doc/doxygen )
- test? ( dev-libs/boost )"
+ test? ( dev-cpp/catch )"
src_configure() {
local mycmakeargs=(
-DHTTP_CLIENT=$(usex http-client)
-DHTTP_SERVER=$(usex http-server)
- # they are not installed
- -DCOMPILE_EXAMPLES=NO
+ # they are not installed but required for tests to build
+ -DCOMPILE_EXAMPLES=$(usex test)
-DCOMPILE_STUBGEN=$(usex stubgen)
-DCOMPILE_TESTS=$(usex test)
+ -DCATCH_INCLUDE_DIR="${EPREFIX}/usr/include/catch"
)
cmake-utils_src_configure
next reply other threads:[~2016-05-24 11:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 11:23 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-12 17:58 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/libjson-rpc-cpp/ Michał Górny
2022-12-12 17:58 Michał Górny
2022-02-26 23:26 Sam James
2021-10-24 8:54 Michał Górny
2021-10-23 20:20 Michał Górny
2020-03-19 17:20 Michał Górny
2020-01-15 7:20 Michał Górny
2020-01-15 7:20 Michał Górny
2019-04-10 15:07 Michał Górny
2019-03-29 9:18 Michał Górny
2019-03-10 8:08 Michał Górny
2019-01-19 14:21 David Seifert
2018-11-03 21:58 Michał Górny
2018-11-01 8:48 Michał Górny
2018-11-01 8:48 Michał Górny
2018-03-26 16:14 Michał Górny
2018-01-06 12:24 Michał Górny
2018-01-05 9:36 Michał Górny
2017-08-28 18:23 Michał Górny
2017-08-28 18:23 Michał Górny
2017-08-27 8:19 Michał Górny
2017-08-27 8:19 Michał Górny
2016-08-13 18:32 Michał Górny
2016-08-13 18:32 Michał Górny
2016-07-02 21:19 Michał Górny
2016-05-24 11:23 Michał Górny
2016-04-19 13:12 Michał Górny
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=1464088988.caedf91905a8eda88d6937220f2541144c7c6ac4.mgorny@gentoo \
--to=mgorny@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