From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Cavallari <Nicolas.Cavallari@green-communications.fr>
Cc: Cherniaev Andrei <dungeonlords789@naver.com>,
buildroot@buildroot.org,
Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/pkg-meson: use --clearcache instead of rm -rf
Date: Mon, 4 Nov 2024 17:19:40 +0100 [thread overview]
Message-ID: <20241104171940.7ee21e6f@windsurf> (raw)
In-Reply-To: <3e85727b-a279-4be9-88db-16ca10931553@green-communications.fr>
On Mon, 4 Nov 2024 12:30:26 +0100
Nicolas Cavallari <Nicolas.Cavallari@green-communications.fr> wrote:
> meson needs a non-existing directory for the outputs. Buildroot assumes that
> "build/" does not exist and use it for builds. The problem with openh264 is that
> "build/" already exists in the source and contains various build system files.
>
> The correct fix would be to not use "build/" for openh264 outputs. Either change
> it globally to a more unique name like "buildroot-build/" or add an option to
> configure it per-package.
The former looks like the good solution: use a less "generic" name,
such as buildroot-build/.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-11-04 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 7:45 [Buildroot] [PATCH 1/1] package/pkg-meson: use --clearcache instead of rm -rf Cherniaev Andrei
2024-11-04 11:30 ` Nicolas Cavallari
2024-11-04 16:19 ` Thomas Petazzoni via buildroot [this message]
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=20241104171940.7ee21e6f@windsurf \
--to=buildroot@buildroot.org \
--cc=Nicolas.Cavallari@green-communications.fr \
--cc=dungeonlords789@naver.com \
--cc=eric.le.bihan.dev@free.fr \
--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