Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/pkg-meson.mk: set correct pkgconfig for native dependencies
Date: Tue, 28 Apr 2020 10:57:48 +0200	[thread overview]
Message-ID: <20200428105748.282b13ad@windsurf.home> (raw)
In-Reply-To: <CADvTj4oX9oQTxpHLEyKMACWHwLh4pL13C4nrK=9wVkQebhV5rA@mail.gmail.com>

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.

Then in a second patch, you remove it from weston.mk.

Yes, in between it means it is passed twice, but this is OK, as it
doesn't break.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-28  8:57 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 [this message]
2020-04-30 20:06             ` James Hilliard
2020-04-30 20:13               ` 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=20200428105748.282b13ad@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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