Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
To: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
Cc: buildroot@buildroot.org,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Miquèl Raynal" <miquel.raynal@bootlin.com>,
	"Mahyar Koshkouei" <mahyar.koshkouei@gmail.com>,
	"Eric Le Bihan" <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH v2] package/mpv: switch to meson from waf
Date: Mon, 14 Apr 2025 19:12:34 +0200	[thread overview]
Message-ID: <Z_1CAle9fM33Yd4c@probook> (raw)
In-Reply-To: <20250106-fix_mpv-v2-1-85117ce7b16b@bootlin.com>

Hello Thomas,

On Mon, Jan 06, 2025 at 12:23:49AM +0100, Thomas Bonnefille via buildroot wrote:
> Since commit fd562315, which updated waf to v2.1.1, Buildroot has
> encountered issues building mpv, likely due to an outdated version of
> the waf build system.
>
> Starting with mpv v0.35, meson was introduced as an alternative to waf,
> and in mpv v0.37, waf was completely removed.
>
> This commit updates the mpv makefile to use meson, resolving the build
> issues and simplifying future updates to newer versions of mpv.
>
> All options previously used for Waf have been translated to the new
> build system by replacing `--disable-feature` with `-Dfeature=disabled`
> (and similarly for enabling features). Some features have special
> handling:
>
> - The `/usr` prefix is automatically passed to meson packages by
>   default.
> - The Android feature "has been removed since meson can detect if a
>   machine is Android"[1].
> - The `libmpv` parameter has been enabled in the makefile as `libmpv`
>   must be built by default with mpv.
> - Meson packages automatically set whether the library should be built
>   statically using the `default_library` meson parameter.
> - Meson automatically detects the presence of `libatomic` and passes the
>   correct argument to the linker. However, it is possible to set the
>   `stdatomic` meson parameter to specify whether `libatomic` must or
>   must not be used.
>
> Fixes:
>     https://autobuild.buildroot.org/results/68d42441fc0da34e1bf2a4247726f5f4ec3b8e77/
>
> [1]: https://github.com/mpv-player/mpv/blob/140ec21c89d671d392877a7f3b91d67e7d7b9239/DOCS/build-system-differences.md?plain=1#L48
>
> Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>

I'm trying to use this patch on top of current master (2025.02-268-g637eead755)
and there seems to be a minor incompatibility:

output/build/mpv-0.35.1/meson.build:1:0: ERROR: Option "build-date" value disabled is not boolean (true or false).

> +MPV_CONF_OPTS += -Dbuild-date=disabled

With that changed to -Dbuild-date=false:

Tested-by: J. Neuschäfer <j.ne@posteo.net>

Thanks!
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-04-14 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 23:23 [Buildroot] [PATCH v2] package/mpv: switch to meson from waf Thomas Bonnefille via buildroot
2025-04-14 17:12 ` J. Neuschäfer via buildroot [this message]
2025-04-18  8:16   ` Thomas Bonnefille via buildroot

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=Z_1CAle9fM33Yd4c@probook \
    --to=buildroot@buildroot.org \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=j.neuschaefer@gmx.net \
    --cc=mahyar.koshkouei@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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