From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libwebsockets : bump to v1.7.2
Date: Wed, 2 Mar 2016 21:23:19 +0100 [thread overview]
Message-ID: <20160302212319.6768a95d@free-electrons.com> (raw)
In-Reply-To: <56D6EAEA.5050709@proximus.be>
Johan,
On Wed, 2 Mar 2016 14:30:18 +0100, Johan Sagaert wrote:
> The static library libwebsockets.a is at .../staging/usr/lib as well as
> the shared version
> having both static and shared libraries enabled in Buildroot.
>
> However when i select static only libraries i get the following build error:
> I looks like the extention fails to build.
>
> When adding :
> ifeq ($(BR2_STATIC_LIBS),y)
> LIBWEBSOCKETS_CONF_OPTS += -DLWS_WITH_SHARED=OFF
> endif
>
> libwebsockets.a builds fine, so i guess this is the way to go.
Right, but you didn't add this to your v2. Did I miss it?
> (should i disable the static build when shared libs are selected ?
> both static and shared are now build when shared libs only is selected
> in Buildroot. )
We have three cases in Buildroot:
BR2_STATIC_LIBS=y => only static lib should be built
BR2_SHARED_LIBS=y => only shared lib should be built
BR2_SHARED_STATIC_LIBS=y => both shared and static lib should be
built
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-02 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 22:30 [Buildroot] [PATCH 1/1] libwebsockets : bump to v1.7.2 Sagaert Johan
2016-03-01 22:34 ` Thomas Petazzoni
[not found] ` <56D63448.4080202@proximus.be>
2016-03-02 8:16 ` Thomas Petazzoni
2016-03-02 13:30 ` Johan Sagaert
2016-03-02 20:23 ` Thomas Petazzoni [this message]
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=20160302212319.6768a95d@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