From: Thomas Petazzoni <thomas.petazzoni@free-electrons.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 22:41:00 +0100 [thread overview]
Message-ID: <20161204224100.26768191@free-electrons.com> (raw)
In-Reply-To: <20161204212433.GC3433@free.fr>
Hello,
On Sun, 4 Dec 2016 22:24:34 +0100, Yann E. MORIN wrote:
> Romain, All,
> > - $$(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)
>
> I'm not against having variables named the same across packages, but
> here I think $(2)_BUILD_OPTS would be more appropriate.
ACK.
> > @@ -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)
>
> Usually, those options entirely override the default ones. For example,
> if you provide FOO_INSTALL_STAGING_OPTS for an autotools package, then
> the default (just 'install') is lost:
>
> package/pkg-autotools.mk:
> 159 $(2)_INSTALL_STAGING_OPTS? ?= DESTDIR=$$(STAGING_DIR) install
>
> OTOH, I find this to be counter-intuitive for a user, and I would prefer
> the options to add rather than replace.
Agreed. I also find it super annoying that we have to replicate
DESTDIR=$$(STAGING_DIR) install. But in some cases, we *do* need to
override it.
Another thing that I dislike is that we have no way to pass an option
to all of the build and install steps.
> But consistency trumps it all, so we should do the same for waf
> packages:
>
> $(2)_INSTALL_STAGING_OPTS ?= install --destdir=$$(STAGING_DIR)
I agree. Even if the current situation is not 100% nice, I think a
rework of this current situation is a much broader effort. So let's
make the waf-package infrastructure be as similar as possible to the
other ones.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-04 21:41 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 ` [Buildroot] [PATCH 2/3] core: waf-package infra: add missing additional variables for each build step Romain Naour
2016-12-04 21:04 ` 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 [this message]
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=20161204224100.26768191@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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