public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/rapidyaml/
Date: Sun,  5 Feb 2023 12:11:11 +0000 (UTC)	[thread overview]
Message-ID: <1675598977.6bdfb5ab03bb84f2f6be6bb928673db7e3e346ac.ionen@gentoo> (raw)

commit:     6bdfb5ab03bb84f2f6be6bb928673db7e3e346ac
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Sun Feb  5 11:36:08 2023 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Sun Feb  5 12:09:37 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6bdfb5ab

dev-cpp/rapidyaml: bump to -std=c++17

Does not seem to be anything that requires staying on c++11.
Technically the new gtest-1.13 only needs >=14 but may as
well go higher with current gcc's default.

Closes: https://bugs.gentoo.org/893272
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 dev-cpp/rapidyaml/rapidyaml-0.5.0.ebuild | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/dev-cpp/rapidyaml/rapidyaml-0.5.0.ebuild b/dev-cpp/rapidyaml/rapidyaml-0.5.0.ebuild
index f1c6896c181b..84cf212c458f 100644
--- a/dev-cpp/rapidyaml/rapidyaml-0.5.0.ebuild
+++ b/dev-cpp/rapidyaml/rapidyaml-0.5.0.ebuild
@@ -69,6 +69,9 @@ src_configure() {
 		# TODO: enable this+tests, should(?) be easier to do with >=0.5.0 but
 		# still need looking into (please fill a bug if need this right away)
 		-DRYML_BUILD_API=no
+
+		# rapidyaml sets c++11, but >=gtest-1.13 wants >=c++14 (bug #893272)
+		-DC4_CXX_STANDARD=17
 	)
 
 	cmake_src_configure


             reply	other threads:[~2023-02-05 12:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 12:11 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-03 12:31 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/rapidyaml/ Ionen Wolkens
2024-05-25  2:03 Sam James
2024-05-24 17:35 Arthur Zamarin
2024-05-24 14:56 Arthur Zamarin
2024-05-24 14:56 Arthur Zamarin
2024-04-29 13:26 Ionen Wolkens
2023-02-21  6:07 Ionen Wolkens
2023-02-05 12:11 Ionen Wolkens
2023-01-11  7:50 Sam James
2023-01-11  5:15 Sam James
2023-01-11  5:07 Sam James
2023-01-11  3:30 Sam James
2022-12-19  5:48 Ionen Wolkens
2022-09-23  0:27 Ionen Wolkens
2022-06-07  8:26 Jakov Smolić
2022-06-07  8:26 Jakov Smolić
2022-06-07  8:24 Jakov Smolić
2022-06-07  8:24 Jakov Smolić
2022-03-09 15:04 Ionen Wolkens
2022-01-06 21:23 Georgy Yakovlev
2022-01-06 20:59 Georgy Yakovlev

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=1675598977.6bdfb5ab03bb84f2f6be6bb928673db7e3e346ac.ionen@gentoo \
    --to=ionen@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