From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] pkg-waf: add support for <pkg>_SUBDIR
Date: Wed, 10 Oct 2018 21:47:41 +0200 [thread overview]
Message-ID: <20181010214741.6ff1f7ae@windsurf> (raw)
In-Reply-To: <CAKAx1cj8sSdbR6_NJu=tiHB=EPO_bjb571k4Yu5rVo_g5h66dw@mail.gmail.com>
Hello Lionel,
Thanks for your patch, sorry for the slow reply. See some feedback
below.
On Wed, 19 Sep 2018 15:31:40 +0200, Lionel Orry wrote:
> In the Buildroot manual, it is specified that the Waf-based
> infrastructure supports the <pkg>_SUBDIR variable, which was not true.
>
> This patch makes use of this variable by changing to the given
> sub-directory before executing waf commands.
>
> Signed-off-by: Lionel Orry <lionel.orry@gmail.com>
First, could you update the Buildroot manual to document this new
variable of the waf package infrastructure ?
> +$(2)_SRCDIR = $$($(2)_DIR)/$$($(2)_SUBDIR)
Could you try after dropping this line? In fact the generic package
infrastructure already defines <pkg>_SRCDIR as <pkg>_DIR/<pkg>_SUBDIR,
so it shouldn't be needed to replicate that here.
And bonus point if you submit another patch that drops those redundant
lines from pkg-cmake, pkg-meson and pkg-python, of course after testing
that it still works fine :)
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-10 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 13:31 [Buildroot] [PATCH 1/1] pkg-waf: add support for <pkg>_SUBDIR Lionel Orry
2018-09-28 8:32 ` Lionel Orry
2018-10-10 19:47 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-10 14:44 Lionel Orry
2018-10-10 15:06 ` Marcel Patzlaff
2018-10-10 15:10 ` Lionel Orry
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=20181010214741.6ff1f7ae@windsurf \
--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 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.