From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] core: waf-package infra: add missing additional variables for each build step
Date: Sun, 4 Dec 2016 21:58:45 +0100 [thread overview]
Message-ID: <1480885126-517-2-git-send-email-romain.naour@gmail.com> (raw)
In-Reply-To: <1480885126-517-1-git-send-email-romain.naour@gmail.com>
Some waf packages may want to pass additional variables to waf script
in each build step. Add the possibility to do so by defining the
following variables:
<pkg>_MAKE_OPTS for the build step
<pkg>_INSTALL_STAGING_OPTS for the install to staging directory
<pkg>_INSTALL_TARGET_OPTS for the install to target directory
Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
---
package/pkg-waf.mk | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/package/pkg-waf.mk b/package/pkg-waf.mk
index 908ac03..97e2e6a 100644
--- a/package/pkg-waf.mk
+++ b/package/pkg-waf.mk
@@ -72,7 +72,8 @@ endif
ifndef $(2)_BUILD_CMDS
define $(2)_BUILD_CMDS
cd $$(@D) && \
- $$(TARGET_MAKE_ENV) $$(HOST_DIR)/usr/bin/python2 $$($(2)_WAF) build -j $$(PARALLEL_JOBS)
+ $$(TARGET_MAKE_ENV) $$(HOST_DIR)/usr/bin/python2 $$($(2)_WAF) \
+ build -j $$(PARALLEL_JOBS) $$($(2)_MAKE_OPTS)
endef
endif
@@ -84,7 +85,8 @@ ifndef $(2)_INSTALL_STAGING_CMDS
define $(2)_INSTALL_STAGING_CMDS
cd $$(@D) && \
$$(TARGET_MAKE_ENV) $$(HOST_DIR)/usr/bin/python2 $$($(2)_WAF) \
- install --destdir=$$(STAGING_DIR)
+ install --destdir=$$(STAGING_DIR) \
+ $$($(2)_INSTALL_STAGING_OPTS)
endef
endif
@@ -96,7 +98,8 @@ ifndef $(2)_INSTALL_TARGET_CMDS
define $(2)_INSTALL_TARGET_CMDS
cd $$(@D) && \
$$(TARGET_MAKE_ENV) $$(HOST_DIR)/usr/bin/python2 $$($(2)_WAF) \
- install --destdir=$$(TARGET_DIR)
+ install --destdir=$$(TARGET_DIR) \
+ $$($(2)_INSTALL_TARGET_OPTS)
endef
endif
--
2.5.5
next prev parent reply other threads:[~2016-12-04 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 20:58 [Buildroot] [PATCH 1/3] package/aubio: add upstream hash link Romain Naour
2016-12-04 20:58 ` Romain Naour [this message]
2016-12-04 21:04 ` [Buildroot] [PATCH 2/3] core: waf-package infra: add missing additional variables for each build step Thomas Petazzoni
2016-12-04 21:20 ` Romain Naour
2016-12-04 21:22 ` Thomas Petazzoni
2016-12-04 21:44 ` Romain Naour
2016-12-04 21:24 ` Yann E. MORIN
2016-12-04 21:35 ` Romain Naour
2016-12-04 21:41 ` Thomas Petazzoni
2016-12-04 23:32 ` Arnout Vandecappelle
2016-12-05 21:18 ` Romain Naour
2016-12-05 21:24 ` Thomas Petazzoni
2016-12-05 22:03 ` Arnout Vandecappelle
2016-12-04 20:58 ` [Buildroot] [PATCH 3/3] package/aubio: disable unit tests with --notests Romain Naour
2016-12-04 21:02 ` Thomas Petazzoni
2016-12-04 21:03 ` Thomas Petazzoni
2016-12-04 21:31 ` [Buildroot] [PATCH 1/3] package/aubio: add upstream hash link Thomas Petazzoni
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=1480885126-517-2-git-send-email-romain.naour@gmail.com \
--to=romain.naour@gmail.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