From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autotools: add with/without and enable/disable helpers
Date: Fri, 19 Nov 2010 03:20:18 -0500 [thread overview]
Message-ID: <201011190320.21230.vapier@gentoo.org> (raw)
In-Reply-To: <20101119085518.655d8c0d@surf>
On Friday, November 19, 2010 02:55:18 Thomas Petazzoni wrote:
> On Thu, 18 Nov 2010 23:33:57 -0500 Mike Frysinger wrote:
> > +# $(call _USE_CONF,enable,disable,LIB_FFMPEG,video,blah) ->
> > --enable-video=blah if LIB_FFMPEG +# $(call
> > _USE_CONF,with,without,LIB_FFMPEG,video) -> --with-video if
> > LIB_FFMPEG +_USE_CONF = $(shell \
> > + opt="$(5)"; test "$${opt:+set}" = "set" && opt="=$${opt}"; \
> > + test "$(BR2_$(3))" = "y" \
> > + && echo "--$(1)-$(4)$${opt}" \
> > + || echo "--$(2)-$(4)")
>
> However, I'm worried that this will start a shell process when
> evaluating *each* USE_ENABLE/USE_WITH call, and this will slow down the
> start up of Buildroot.
not really. this is the whole point of make's lazy evaluation. so unless
somewhere the code is wrongly using ":=", these shouldnt be executed unless
the configure script in question is actually run. a simple test on my side
says that it is working as i expect -- lazily.
> It'd be nicer if we could use a pure Makefile implementation. What
> about a simpler :
>
> USE_WITH = $(if $(BR2_$(1)),--with-$(2),--without-$(2))
> USE_ENABLE = $(if $(BR2_$(1),--enable-$(2),--disable-$(2)))
this isnt functionally equivalent ... there is no support for the optional
[=val] with the flag
> However, their usage might be a little limited: often when the option
> is enabled, we need to add a dependency to the package as well.
this is due to poor design on the behalf of buildroot. it really needs to
adopt more Kconfig style and do stuff like:
foo-y =
foo-$(BR2_xxx) += libpng
and again, please retain cc in replies
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101119/6ac90925/attachment.pgp>
next prev parent reply other threads:[~2010-11-19 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 4:33 [Buildroot] [PATCH] autotools: add with/without and enable/disable helpers Mike Frysinger
2010-11-19 7:55 ` Thomas Petazzoni
2010-11-19 8:20 ` Mike Frysinger [this message]
2010-11-19 9:56 ` Thomas Petazzoni
2010-11-19 10:07 ` Mike Frysinger
2010-11-19 10:23 ` [Buildroot] [PATCH v2] " Mike Frysinger
2010-11-19 11:13 ` Thomas Petazzoni
2010-11-19 11:24 ` Mike Frysinger
2010-11-19 12:49 ` Paulius Zaleckas
2010-11-19 23:25 ` Mike Frysinger
2010-11-20 2:37 ` [Buildroot] [PATCH v3] " Mike Frysinger
2010-11-20 3:47 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-03-28 8:35 [Buildroot] [PATCH] " Mike Frysinger
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=201011190320.21230.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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