From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] gstreamer-meson.eclass: New eclass required for gstreamer-1.18.0+
Date: Wed, 17 Mar 2021 11:15:26 +0200 [thread overview]
Message-ID: <fe1db2c0f73f5cc6e68709b66680a56a50f3afce.camel@gentoo.org> (raw)
In-Reply-To: <094FA9B1-F288-4287-B9CF-7D47A479F34D@gentoo.org>
Thanks for working on this, some very initial comments below
Ühel kenal päeval, K, 17.03.2021 kell 01:57, kirjutas Sam James:
> > +# @FUNCTION: gstreamer_multilib_src_install_all
> > +# @DESCRIPTION:
> > +# Installs documentation for requested gstreamer plugin, and
> > removes
> .la
> > +# files.
> > +gstreamer_multilib_src_install_all() {
> > + local plugin_dir
> > +
> > + for plugin_dir in ${GST_PLUGINS_BUILD_DIR} ; do
> > + local dir=$(gstreamer_get_plugin_dir
> > ${plugin_dir})
> > + [[ -e ${dir}/README ]] && dodoc "${dir}"/README
> > + done
> > +
> > + prune_libtool_files --modules
>
> Deprecated in newer EAPIs, let’s do it manually.
I don't think that ought to be necessary at all, as a meson build
wouldn't be generating libtool files.
My main initial question on this version is:
How does it behave with helper libraries from the same tarball?
Basically what gstreamer_system_link function solved in the autotools
eclass.
E.g., if you build gst-plugins-libvisual, is it building gstreamer-
audio, gstreamer-video and gstreamer-pbutils as well again
(automatically due to generated ninja dependencies), or picks them up
from gst-plugins-base?
Some other quick notes:
* I would prefer this being EAPI-7 only
* Don't make nls optional
* It would be neat if we had a QA warning when a split plugin uses orc,
but doesn't have in IUSE for it (or vice-versa); maybe that's doable by
checking if the plugin meson.build uses orc_dep?
Mart
next prev parent reply other threads:[~2021-03-17 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 1:49 [gentoo-dev] [PATCH] gstreamer-meson.eclass: New eclass required for gstreamer-1.18.0+ Haelwenn (lanodan) Monnier
2021-03-17 1:57 ` Sam James
2021-03-17 9:15 ` Mart Raudsepp [this message]
2021-03-17 9:29 ` Haelwenn (lanodan) Monnier
2021-03-17 14:24 ` Mart Raudsepp
2021-03-17 16:13 ` Alec Warner
2021-03-23 12:44 ` [gentoo-dev] [PATCH v2] " Haelwenn (lanodan) Monnier
2021-03-23 13:05 ` 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=fe1db2c0f73f5cc6e68709b66680a56a50f3afce.camel@gentoo.org \
--to=leio@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