Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Add CONF_ENABLE and CONF_PKG_ENABLE helper functions
Date: Sat, 12 May 2012 00:29:15 +0200	[thread overview]
Message-ID: <4FAD92BB.5040606@mind.be> (raw)
In-Reply-To: <20120507162139.44a814e9@skate>

On 05/07/12 16:21, Thomas Petazzoni wrote:
> Le Sat, 28 Apr 2012 23:16:18 +0200,
> "Arnout Vandecappelle (Essensium/Mind)"<arnout@mind.be>  a ?crit :
>
>> >    Many packages have the following type of construct:
>> >
>> >  ifeq ($(BR2_PACKAGE_ACL),y)
>> >          SYSTEMD_CONF_OPT += --enable-acl
>> >          SYSTEMD_DEPENDENCIES += acl
>> >  else
>> >          SYSTEMD_CONF_OPT += --disable-acl
>> >  endif
>> >
>> >    The first patch in this series abbreviates that to
>> >
>> >  $(eval $(call CONF_PKG_ENABLE,SYSTEMD,acl))
>> >
>> >    It makes it possible to abbreviate similar constructs as well.
> Thanks for working on this and making a proposal.
>
> However, on my side, I am not yet convinced that this is actually
> making things better than what we have now. What we have now is quite
> obvious for the first-time reader, which is very good. Those
> CONF_PKG_ENABLE and CONF_ENABLE macros make things a bit too cryptic
> from my point of view.

  I agree that it looks too cryptic.  Certainly with the eval and call things.
And we should indeed try to keep the package .mk files as intuitive as
possible.

  However, my purpose was not to save a few lines, but rather to make sure
that package contributors do things the correct way.  Specifically, I want
to make it easier for package contributors to explicitly specify --enable
and --disable options.

  I was probably just trying too hard to support all possible use cases.
What about adding something like:

SYSTEMD_AUTO_CONF_ENABLE_DEPS += acl

which would get expanded to the whole ifeq thing in the AUTOTARGETS call?
This only works if the buildroot package name is the same as the
--enable/--disable option, but that already catches many cases.

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2012-05-11 22:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-28 21:16 [Buildroot] [PATCH 0/3] Add CONF_ENABLE and CONF_PKG_ENABLE helper functions Arnout Vandecappelle
2012-04-28 21:16 ` [Buildroot] [PATCH 1/3] pkg-infra: add " Arnout Vandecappelle
2012-04-28 21:16 ` [Buildroot] [PATCH 2/3] avahi: use CONF_ENABLE and CONF_PKG_ENABLE Arnout Vandecappelle
2012-04-28 21:16 ` [Buildroot] [PATCH 3/3] cairo: " Arnout Vandecappelle
2012-05-07 14:21 ` [Buildroot] [PATCH 0/3] Add CONF_ENABLE and CONF_PKG_ENABLE helper functions Thomas Petazzoni
2012-05-09  8:06   ` Thomas De Schampheleire
2012-05-09  9:35     ` Peter Korsgaard
2012-05-11 22:29   ` Arnout Vandecappelle [this message]
2012-05-12  9:03     ` Samuel Martin
2012-05-12 11:42       ` Thomas Petazzoni
2012-05-12 11:05     ` Thomas Petazzoni
2012-05-12 14:47       ` Arnout Vandecappelle

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=4FAD92BB.5040606@mind.be \
    --to=arnout@mind.be \
    --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