public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/folly/
Date: Tue, 22 Mar 2022 01:48:18 +0000 (UTC)	[thread overview]
Message-ID: <1647913537.3c8dac4c0282e5003ec8a5a3b77870afeb515a4b.sam@gentoo> (raw)

commit:     3c8dac4c0282e5003ec8a5a3b77870afeb515a4b
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 22 01:45:37 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Mar 22 01:45:37 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c8dac4c

dev-cpp/folly: add 2022.03.21.00

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-cpp/folly/Manifest                   |  1 +
 dev-cpp/folly/folly-2022.03.21.00.ebuild | 61 ++++++++++++++++++++++++++++++++
 2 files changed, 62 insertions(+)

diff --git a/dev-cpp/folly/Manifest b/dev-cpp/folly/Manifest
index 5e3d7db9c32b..fe0814329b76 100644
--- a/dev-cpp/folly/Manifest
+++ b/dev-cpp/folly/Manifest
@@ -1,3 +1,4 @@
 DIST folly-2022.02.28.00.tar.gz 3600258 BLAKE2B 5943b0e4b6178c8293714f673ed289daed26b1dad22dcb52dc80475f385961cf0a690accc44139f245f2df5cf10c0bdb5638c8bed52cb97fefd3ad6d8dc147b8 SHA512 91ee21e463ffc6eee3b0e5e0244721a9612337b9afe92645556a154f521aec1070f4f381962247bb9bf11592efb5b8bb01f70d1a66acd3444967538062dfe826
 DIST folly-2022.03.07.00.tar.gz 3604306 BLAKE2B fe255678d6f827c82ada3e136742d07bd62dfb81c1250ca6bae9a4f3e1f015904032da8de1488342da1326fa520b448c63a59ef7e0139ecb0844a1ae19c1dfed SHA512 e63eff137711ca71b5a78469e4feff1b4e7b65465413eefb91b7c0cb26b94e1d581a305a9df9937ce05bcd8af3dc465adb816ad95538689811d8ab5b5b9f269f
 DIST folly-2022.03.14.00.tar.gz 3605018 BLAKE2B 11a58e3c23c1e1299c16821e552d500f8215d2fb2fbdee3699b8487e1073196dfc322461e7670d3968c703d84b0b526d2479bcb74005b763f195ce48f04a419d SHA512 0b3710862360788eb55dc40703e3862f57819acf217287f13ce125b56692c4e5b1de12289f02520ecca9007fa872a69e8936df0ec9260adf974a88286489a9b1
+DIST folly-2022.03.21.00.tar.gz 3611725 BLAKE2B 6b0d3431810a26484b2c15a8ba4b245e720d717364a4305269b3adabaa2d005466dfd7ad086b38cb06ee2a2d5908e903e68486aadc62834a32b4fe59cd313095 SHA512 4e0fda55f007179883af30024fe1d389642159b1b4c915f7ef1a3c1003c8c52e2370f53ffa79d5fa75533d33becfb946d2bcbb2abdc62b9a297f977403d13dd7

diff --git a/dev-cpp/folly/folly-2022.03.21.00.ebuild b/dev-cpp/folly/folly-2022.03.21.00.ebuild
new file mode 100644
index 000000000000..b644181fecc6
--- /dev/null
+++ b/dev-cpp/folly/folly-2022.03.21.00.ebuild
@@ -0,0 +1,61 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit cmake toolchain-funcs
+
+DESCRIPTION="An open-source C++ library developed and used at Facebook"
+HOMEPAGE="https://github.com/facebook/folly"
+SRC_URI="https://github.com/facebook/folly/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="Apache-2.0"
+SLOT="0/${PV}"
+KEYWORDS="~amd64"
+IUSE="llvm-libunwind test"
+RESTRICT="!test? ( test )"
+
+RDEPEND="app-arch/bzip2
+	app-arch/lz4:=
+	app-arch/snappy:=
+	app-arch/xz-utils
+	app-arch/zstd:=
+	dev-cpp/gflags:=
+	dev-cpp/glog[gflags]
+	dev-libs/boost:=[context,threads(+)]
+	dev-libs/double-conversion:=
+	dev-libs/libaio
+	dev-libs/libevent:=
+	dev-libs/libfmt:=
+	dev-libs/libsodium:=
+	dev-libs/openssl:=
+	sys-libs/liburing:=
+	sys-libs/zlib
+	llvm-libunwind? ( sys-libs/llvm-libunwind:= )
+	!llvm-libunwind? ( sys-libs/libunwind:= )"
+# libiberty is linked statically
+DEPEND="${RDEPEND}
+	sys-libs/binutils-libs"
+BDEPEND="test? ( sys-devel/clang )"
+
+pkg_setup() {
+	if use test && [[ ${BUILD_TYPE} != "binary" ]] && ! tc-is-clang ; then
+		ewarn "Forcing build with Clang due to GCC bug (because tests are enabled)"
+		ewarn "(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104008)"
+
+		export CC=${CHOST}-clang
+		export CXX=${CHOST}-clang++
+	fi
+}
+
+src_configure() {
+	# TODO: liburing could in theory be optional but fails to link
+
+	local mycmakeargs=(
+		-DLIB_INSTALL_DIR="$(get_libdir)"
+
+		-DBUILD_TESTS=$(usex test)
+	)
+
+	cmake_src_configure
+}


             reply	other threads:[~2022-03-22  1:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  1:48 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-24  8:29 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/folly/ Arthur Zamarin
2023-06-24  6:32 Sam James
2023-06-24  5:39 Sam James
2023-05-04  9:03 Sam James
2023-05-01  1:43 Sam James
2023-04-14  3:39 Sam James
2023-02-17  8:59 Sam James
2023-02-16  3:29 Sam James
2023-02-06 21:25 Sam James
2023-01-23 20:25 Sam James
2022-12-21 22:54 Sam James
2022-12-16 20:48 Arthur Zamarin
2022-09-18  0:35 Sam James
2022-09-18  0:35 Sam James
2022-09-06  4:18 Sam James
2022-08-29 20:13 Sam James
2022-08-23  3:51 Sam James
2022-08-23  3:30 Sam James
2022-08-15 18:19 Sam James
2022-08-13 15:09 Sam James
2022-08-13 15:09 Sam James
2022-07-09  4:25 Sam James
2022-07-08  0:57 Sam James
2022-05-16 12:51 Agostino Sarubbo
2022-04-17 16:44 Sam James
2022-04-16  3:07 Sam James
2022-04-05  3:08 Sam James
2022-04-05  3:08 Sam James
2022-04-01  3:53 Sam James
2022-04-01  3:53 Sam James
2022-03-18  6:16 Sam James
2022-03-09 15:34 Sam James
2022-03-07  7:31 Sam James
2022-03-07  3:24 Sam James

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=1647913537.3c8dac4c0282e5003ec8a5a3b77870afeb515a4b.sam@gentoo \
    --to=sam@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