From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: kory.maincent@bootlin.com, Jens Kleintje <scooby22@web.de>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/gcnano-binaries: set Version: field in .pc files
Date: Sat, 6 Aug 2022 15:40:12 +0200 [thread overview]
Message-ID: <20220806154012.75b09024@windsurf> (raw)
In-Reply-To: <20220805163534.GF3621445@scaer>
On Fri, 5 Aug 2022 18:35:34 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > The version 21.1.1 is chosen because it matches what the Yocto recipe
> > is doing for this package:
> >
> > https://github.com/STMicroelectronics/meta-st-stm32mp/blob/kirkstone/recipes-graphics/gcnano-userland/gcnano-userland.inc#L42
>
> ... which they did not provide any explanation for...
It matches a somewhat corresponding mesa3d version, I suppose. This is
at least how some packages detect if libgbm is recent enough for their
needs (I've seen a package require >= 17 for example).
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
next prev parent reply other threads:[~2022-08-06 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 20:41 [Buildroot] [PATCH 1/2] package/gcnano-binaries: create symlinks for libGLESv2 and libGLESv1_CM.so Thomas Petazzoni via buildroot
2022-08-04 20:41 ` [Buildroot] [PATCH 2/2] package/gcnano-binaries: set Version: field in .pc files Thomas Petazzoni via buildroot
2022-08-05 16:35 ` Yann E. MORIN
2022-08-06 13:40 ` Thomas Petazzoni via buildroot [this message]
2022-08-05 16:33 ` [Buildroot] [PATCH 1/2] package/gcnano-binaries: create symlinks for libGLESv2 and libGLESv1_CM.so Yann E. MORIN
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=20220806154012.75b09024@windsurf \
--to=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.com \
--cc=scooby22@web.de \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.