From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Luca Pesce via buildroot <buildroot@buildroot.org>
Cc: Luca Pesce <luca.pesce@vimar.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/libwebsockets: enable libev and libevent support indipendently
Date: Sun, 12 Mar 2023 10:58:44 +0100 [thread overview]
Message-ID: <20230312105844.2238d7dd@windsurf> (raw)
In-Reply-To: <1678456111-30786-1-git-send-email-luca.pesce@vimar.com>
On Fri, 10 Mar 2023 14:48:31 +0100
Luca Pesce via buildroot <buildroot@buildroot.org> wrote:
> libev and libevent can be enabled at the same time since version 4.1.0,
> thanks to the event lib support refactoring into plugins, which is enabled by
> default for unix platform builds (LWS_WITH_EVLIB_PLUGINS=ON):
> https://github.com/warmcat/libwebsockets/commit/c6c7ab2b4498c62bf9461b36395d8466e023575d
>
> In this way, libwebsockets can be compiled with both libev and libevent
> support, which is then user-selectable at runtime.
>
> This basically restores the behavior changed by previous commit 27f257e.
>
> Signed-off-by: Luca Pesce <luca.pesce@vimar.com>
> ---
> package/libwebsockets/libwebsockets.mk | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-03-12 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 13:48 [Buildroot] [PATCH 1/1] package/libwebsockets: enable libev and libevent support indipendently Luca Pesce via buildroot
2023-03-12 9:58 ` Thomas Petazzoni via buildroot [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=20230312105844.2238d7dd@windsurf \
--to=buildroot@buildroot.org \
--cc=luca.pesce@vimar.com \
--cc=thomas.petazzoni@bootlin.com \
/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.