From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/pkg-meson.mk: set correct pkgconfig for native dependencies
Date: Thu, 30 Apr 2020 22:13:38 +0200 [thread overview]
Message-ID: <20200430201338.GP11346@scaer> (raw)
In-Reply-To: <CADvTj4ofOtmzMiVPHS1OJXYZZvcMFUU30=3=j7uweMkS-+XsFA@mail.gmail.com>
James, All,
On 2020-04-30 14:06 -0600, James Hilliard spake thusly:
> On Tue, Apr 28, 2020 at 2:57 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> >
> > On Tue, 28 Apr 2020 02:05:13 -0600
> > James Hilliard <james.hilliard1@gmail.com> wrote:
> >
> > > > Thanks James and Thomas for correcting me.
> > > >
> > > > So in that case, this patch looks good. But the meson.mk change should be a
> > > > separate patch, of course.
> > > That would overlap with the weston -Dbuild.pkg_config_path removal.
> >
> > You add -Dbuild.pkg_config_path in pkg-meson.mk in a first patch.
> https://patchwork.ozlabs.org/project/buildroot/patch/20200428122213.63826-1-james.hilliard1 at gmail.com/
> >
> > Then in a second patch, you remove it from weston.mk.
> https://patchwork.ozlabs.org/project/buildroot/patch/20200428122213.63826-2-james.hilliard1 at gmail.com/
> >
> > Yes, in between it means it is passed twice, but this is OK, as it
> > doesn't break.
> Ok, I've sent the moving of -Dbuild.pkg_config_path from weston.mk
> to pkg-meson.mk as a 2 patch series, I'll follow up with the removal of
> the other workarounds after those are merged.
Have seen them, thanks.
However, I am not sure I followed what is still needed about this meson
stuff: care to heck the status of each patch and seris on patchwork, nad
mark as rejected or not-applicable those that no longer make sense,
please?
Regards,
Yann E. MORIN.
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-04-30 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 4:06 [Buildroot] [PATCH 1/1] package/pkg-meson.mk: set correct pkgconfig for native dependencies James Hilliard
2020-04-28 5:22 ` Thomas Petazzoni
2020-04-28 5:28 ` James Hilliard
2020-04-28 5:32 ` Thomas Petazzoni
2020-04-28 5:39 ` James Hilliard
2020-04-28 6:48 ` Arnout Vandecappelle
2020-04-28 6:50 ` Arnout Vandecappelle
2020-04-28 6:55 ` James Hilliard
2020-04-28 7:00 ` James Hilliard
2020-04-28 7:10 ` Thomas Petazzoni
2020-04-28 7:55 ` Arnout Vandecappelle
2020-04-28 8:05 ` James Hilliard
2020-04-28 8:57 ` Thomas Petazzoni
2020-04-30 20:06 ` James Hilliard
2020-04-30 20:13 ` Yann E. MORIN [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=20200430201338.GP11346@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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