From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Romain Naour <romain.naour@smile.fr>,
Samuel Martin <s.martin49@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/misc/toolchainfile.cmake.in: set PKG_CONFIG/CMAKE prefix paths
Date: Wed, 11 Jan 2023 17:44:16 +0100 [thread overview]
Message-ID: <20230111164416.GQ151997@scaer> (raw)
In-Reply-To: <2ac975d4-3451-ec20-9987-a56be5ea36e4@green-communications.fr>
Nicolas, James, All,
On 2023-01-11 17:01 +0100, Nicolas Cavallari spake thusly:
> On 11/01/2023 16:19, Romain Naour wrote:
> >Le 28/07/2022 à 03:44, James Hilliard a écrit :
> >>These appear to not be getting set correctly and are needed when using
> >>meson's relocatable pkgconfig format.
> >How this cmake file (toolchainfile.cmake.in) is used by a meson package ?
> I understand it as "a cmake package needs this to use a pkgconfig file
> generated by a meson package when meson is configured to generate
> relocatable pkgconfig files".
OK, but then I have a few questions:
- what are "relocatable pkgconfig files", and how do they fit in the
pkgconfig spec?
- how do they differ from standard pkgconfig files? By "standard", I
mean all the pkgconfig files we currently install and use from the
hundreds, if not thousands, of packages that provided them.
- why is meson generating those pkgconfig files, rather than standard
ones?
- and finally, if the "relocatable pkgconfig files" generated by meson
are incorrect wrt the pkgconfig spec, can we tell meson not to do
that?
This should be answered with explanations in the commit log, rather than
providing reviewers with an elusive and confusing "appear to not be
getting set correctly" without research and explanations...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-01-11 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 1:44 [Buildroot] [PATCH 1/2] support/misc/toolchainfile.cmake.in: set PKG_CONFIG/CMAKE prefix paths James Hilliard
2022-07-28 1:44 ` [Buildroot] [PATCH 2/2] package/pkg-meson: generate relocatable pkgconfigs James Hilliard
2023-01-11 15:30 ` Romain Naour
2023-01-28 0:35 ` James Hilliard
2023-01-11 18:15 ` Yann E. MORIN
2023-01-28 1:01 ` James Hilliard
2023-01-11 15:19 ` [Buildroot] [PATCH 1/2] support/misc/toolchainfile.cmake.in: set PKG_CONFIG/CMAKE prefix paths Romain Naour
2023-01-11 16:01 ` Nicolas Cavallari
2023-01-11 16:12 ` Romain Naour
2023-01-11 16:44 ` Yann E. MORIN [this message]
2023-01-11 17:35 ` Nicolas Cavallari
2023-01-11 18:36 ` 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=20230111164416.GQ151997@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=james.hilliard1@gmail.com \
--cc=nicolas.cavallari@green-communications.fr \
--cc=romain.naour@smile.fr \
--cc=s.martin49@gmail.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