public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] lv2
Date: Mon, 18 Sep 2023 17:49:21 +0100	[thread overview]
Message-ID: <efa5f01f-a954-4408-a434-270ef9072405@dronecode.org.uk> (raw)
In-Reply-To: <20230917221333.c9b9bc4fdb7b85659c3f9853@nifty.ne.jp>

On 17/09/2023 14:13, Takashi Yano via Cygwin-apps wrote:
> I'd like to adopt the lv2 package.
> Thanks in advance.

Thanks.

I added this to your packages.

> lv2.cygport
> 
> inherit meson
> 
> NAME="lv2"
> VERSION=1.18.10
> RELEASE=1
> LICENSE="ISC"
> CATEGORY="Audio"
> SUMMARY="LV2 audio plugin specification"
> DESCRIPTION="LV2 is a portable plugin standard for audio systems, similar in
> scope to LADSPA, VST, AU, and others. It defines a C API for code and a format
> for data files which collectively describe a plugin. LV2 consists of a simple
> core (roughly equivalent in power to LADSPA) which can be extended to support
> more advanced functionality. This allows the interface to be grown to
> accommodate the needs of real software as they arise."
> HOMEPAGE="http://lv2plug.in/"
> SRC_URI="https://lv2plug.in/spec/lv2-${VERSION}.tar.xz"
> 
> PKG_NAMES="lv2 lv2-devel lv2-examples"

Looks like there's a pre-existing historical error here and lv2-docs 
isn't listed (so when we actually generate the documentation, it ends up 
in the main lv2 package, which isn't really what's wanted).

> lv2_OBSOLETES="lv2core"
> lv2_DOCS="usr/share/doc/"
> lv2_CONTENTS="--exclude=eg-*.lv2 etc/ usr/lib/lv2/"
> lv2_devel_REQUIRES="lv2"
> lv2_devel_CONTENTS="usr/bin/lv2specgen.py usr/bin/lv2_validate
> 	usr/include/lv2* usr/lib/pkgconfig/ usr/share/lv2specgen/"
> lv2_examples_SUMMARY="Sample LV2 audio plugins"
> lv2_examples_DOCS="plugins/README.txt"
> lv2_examples_CONTENTS="--exclude=*.dll.a usr/lib/lv2/eg-*.lv2/"
> 
> PKG_IGNORE="usr/lib/lv2/eg-*/*.dll.a"

Keeping the comment these are implibs for modules, so installing them is 
useless would be good.

> 
> CYGMESON_ARGS="
> 	-D docs=enabled
> 	-D old_headers=true
> 	-D tests=disabled
> "
> 
> src_install() {
>         cd ${S}
>         meson_install
>         doenv LV2_PATH "/usr/lib/lv2"
> }
> 
> BUILD_REQUIRES="python39-rdflib python39-markdown python39-importlib-metadata"

I think that 'libsamplerate-devel' also needs to be here.


  reply	other threads:[~2023-09-18 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 13:13 Takashi Yano
2023-09-18 16:49 ` Jon Turney [this message]
2023-09-18 18:41   ` Takashi Yano
2023-09-22 13:15     ` Jon Turney

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=efa5f01f-a954-4408-a434-270ef9072405@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).