From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lua/luv/
Date: Thu, 15 Oct 2020 12:05:18 +0000 (UTC) [thread overview]
Message-ID: <1602763511.f12b6a56bef830507569b5c1a54baf234b861fa1.marecki@gentoo> (raw)
commit: f12b6a56bef830507569b5c1a54baf234b861fa1
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 15 12:01:33 2020 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Thu Oct 15 12:05:11 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f12b6a56
dev-lua/luv: support multiple Lua implementations
Will likely need changes to revdeps.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
dev-lua/luv/luv-1.32.0.0-r101.ebuild | 113 +++++++++++++++++++++++++++++++++++
1 file changed, 113 insertions(+)
diff --git a/dev-lua/luv/luv-1.32.0.0-r101.ebuild b/dev-lua/luv/luv-1.32.0.0-r101.ebuild
new file mode 100644
index 00000000000..57253364377
--- /dev/null
+++ b/dev-lua/luv/luv-1.32.0.0-r101.ebuild
@@ -0,0 +1,113 @@
+# Copyright 2019-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+LUA_COMPAT=( lua5-{1..3} luajit )
+
+inherit cmake lua unpacker
+
+# e.g. MY_PV = a.b.c-d
+MY_PV="$(ver_rs 3 -)"
+MY_P="${PN}-${MY_PV}"
+
+DESCRIPTION="Bare libuv bindings for lua"
+HOMEPAGE="https://github.com/luvit/luv"
+
+LUA_COMPAT_PV="0.7"
+SRC_URI="
+ https://github.com/luvit/${PN}/archive/${MY_PV}.tar.gz -> ${P}.tar.gz
+ https://github.com/keplerproject/lua-compat-5.3/archive/v${LUA_COMPAT_PV}.tar.gz -> ${PN}-lua-compat-${LUA_COMPAT_PV}.tar.gz
+"
+
+LICENSE="Apache-2.0 MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+IUSE="test"
+RESTRICT="!test? ( test )"
+
+REQUIRED_USE="${LUA_REQUIRED_USE}"
+
+BDEPEND="virtual/pkgconfig"
+DEPEND="${LUA_DEPS}
+ >=dev-libs/libuv-1.32.0:="
+RDEPEND="${DEPEND}"
+
+PATCHES=(
+ "${FILESDIR}"/${PN}-1.32.0.0-cmake_lua_version.patch
+)
+
+S="${WORKDIR}/${MY_P}"
+
+src_prepare() {
+ # Fix libdir
+ # Match '/lib/' and '/lib"' without capturing / or ", replacing with libdir
+ sed -i -r "s/\/lib(\"|\/)/\/$(get_libdir)\1/g" CMakeLists.txt || die "Failed to sed CMakeLists.txt"
+ cmake_src_prepare
+}
+
+lua_src_configure() {
+ lua_compat_dir="${WORKDIR}/lua-compat-5.3-${LUA_COMPAT_PV}"
+
+ local mycmakeargs=(
+ -DINSTALL_LIB_DIR="$(lua_get_cmod_dir)"
+ -DBUILD_MODULE=OFF
+ -DLUA_BUILD_TYPE=System
+ -DLUA_COMPAT53_DIR="${lua_compat_dir}"
+ -DWITH_SHARED_LIBUV=ON
+ )
+ if [[ ${ELUA} == luajit ]]; then
+ mycmakeargs+=(
+ -DWITH_LUA_ENGINE=LuaJIT
+ )
+ else
+ mycmakeargs+=(
+ -DWITH_LUA_ENGINE=Lua
+ -DLUA_VERSION=$(ver_cut 1-2 $(lua_get_version))
+ )
+ fi
+
+ cmake_src_configure
+}
+
+lua_src_test() {
+ # We need to copy the implementation-specific library back so that the tests see it
+ rm -f ./luv.so
+ ln -s "${BUILD_DIR}/libluv.so" "./luv.so" || die "Failed to symlink library for tests"
+ ${ELUA} "tests/run.lua" || die "Tests failed"
+}
+
+lua_src_install() {
+ cmake_src_install
+ mkdir -p "${ED}"/usr/$(get_libdir)/pkgconfig && \
+ mv "${ED}$(lua_get_cmod_dir)"/pkgconfig/libluv.pc \
+ "${ED}"/usr/$(get_libdir)/pkgconfig/libluv-${ELUA}.pc || \
+ die "Failed make pkgconfig file for ${ELUA} implementation-specific"
+ rmdir "${ED}$(lua_get_cmod_dir)"/pkgconfig || die
+}
+
+src_configure() {
+ lua_foreach_impl lua_src_configure
+}
+
+src_compile() {
+ lua_foreach_impl cmake_src_compile
+}
+
+src_test() {
+ lua_foreach_impl lua_src_test
+}
+
+src_install() {
+ lua_foreach_impl lua_src_install
+}
+
+pkg_postinst() {
+ ewarn "Please note that in order to properly support multiple Lua implementations,"
+ ewarn "this ebuild of ${PN} installs its library files into implementation-specific"
+ ewarn "module directories, as well as multiple .pc files named after implementations"
+ ewarn "(e.g. 'libluv-lua5.3.pc'). Since upstream by default only supports a single"
+ ewarn "Lua implementation at a time and thus only provides a single, unversioned"
+ ewarn ".pc file, projects depending on ${PN} might require changes in order to"
+ ewarn "support the multi-implementation approach."
+}
next reply other threads:[~2020-10-15 12:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 12:05 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 20:57 [gentoo-commits] repo/gentoo:master commit in: dev-lua/luv/ Arthur Zamarin
2023-10-19 12:17 Sam James
2023-10-19 6:16 Joonas Niilola
2023-10-19 6:16 Joonas Niilola
2023-09-11 0:54 Sam James
2023-04-08 13:42 Luca Barbato
2022-12-02 12:01 Arthur Zamarin
2022-11-08 4:54 Jakov Smolić
2022-11-07 17:27 Arthur Zamarin
2022-10-01 1:29 Sam James
2022-07-15 7:40 Sam James
2022-03-31 18:45 Jakov Smolić
2022-03-31 18:45 Jakov Smolić
2021-10-11 13:47 Yixun Lan
2021-03-16 17:37 Conrad Kostecki
2021-03-16 17:37 Conrad Kostecki
2021-03-09 16:22 Aaron Bauman
2021-01-25 17:38 Marek Szuba
2020-12-22 15:08 Marek Szuba
2020-11-16 15:01 Marek Szuba
2020-11-16 13:18 Marek Szuba
2020-11-13 23:08 Marek Szuba
2019-12-29 9:20 Mikle Kolyada
2019-11-04 3:56 Joonas Niilola
2019-11-03 14:01 Mikle Kolyada
2019-10-31 15:45 Joonas Niilola
2019-10-31 15:45 Joonas Niilola
2019-09-19 12:46 Joonas Niilola
2019-09-19 12:46 Joonas Niilola
2019-09-17 19:31 Michał Górny
2019-09-07 19:42 Joonas Niilola
2019-09-05 18:45 Joonas Niilola
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=1602763511.f12b6a56bef830507569b5c1a54baf234b861fa1.marecki@gentoo \
--to=marecki@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