From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] stress: honor the BR2_PREFER_STATIC_LIB preference
Date: Sun, 03 Mar 2013 17:51:26 +0100 [thread overview]
Message-ID: <51337F8E.9070803@mind.be> (raw)
In-Reply-To: <1362206128-27771-1-git-send-email-roylee17@gmail.com>
On 02/03/13 07:35, Tzu-Jung Lee wrote:
> From: roylee17 <roylee17@gmail.com>
>
> Change-Id: I13f849e76557fac81b488ab26b4ac8b999888bc1
> ---
> package/stress/stress.mk | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/stress/stress.mk b/package/stress/stress.mk
> index 3a047b5..af79bf2 100644
> --- a/package/stress/stress.mk
> +++ b/package/stress/stress.mk
> @@ -10,4 +10,7 @@ STRESS_VERSION = 1.0.4
> STRESS_SITE = http://weather.ou.edu/~apw/projects/stress
> STRESS_AUTORECONF = YES
>
> +STRESS_CONF_OPT = \
> + $(if $(BR2_PREFER_STATIC_LIB),--enable-static,--disable-static)
This is already part of the standard SHARED_STATIC_LIBS_OPTS, which is
part of the argument list of configure. The difference being that in the
shared case, --enable-static is still passed (to allow building static
libraries, in case some client prefers to link statically after all).
Any reason why this doesn't work for stress?
Regards,
Arnout
> +
> $(eval $(autotools-package))
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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
next prev parent reply other threads:[~2013-03-03 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 6:35 [Buildroot] [PATCH] stress: honor the BR2_PREFER_STATIC_LIB preference Tzu-Jung Lee
2013-03-03 16:51 ` Arnout Vandecappelle [this message]
2013-03-03 18:55 ` Tzu-Jung Lee
2013-03-04 16:15 ` Peter Korsgaard
2013-03-04 17:50 ` Tzu-Jung Lee
2013-03-04 17:47 ` Tzu-Jung Lee
2013-03-04 19:59 ` Peter Korsgaard
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=51337F8E.9070803@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 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.