From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Replace libev with libuv
Date: Fri, 18 Jul 2014 10:12:31 -0300 [thread overview]
Message-ID: <53C91D3F.4060500@zacarias.com.ar> (raw)
In-Reply-To: <CALoSW641XSGs6H4i_q07ZfxUtRYoUMgdxBaUtus5J5C7+K=0Fw@mail.gmail.com>
On 07/18/2014 09:48 AM, Nimai Mahajan wrote:
> libuv supercedes libev in many ways, adds more features, and is
> regularly updated. libev has not been updated for more than a year
> now. libuv uses autogen.sh which is tricky to get working properly in
> Buildroot so I request the higher authorities to add this as it is
> perhaps the most useful asynchronous I/O library in C. Current
> unstable version is 0.11.26 and stable is 0.10.27. Thank you.
Hi.
I don't have any authority badge ;) but libev and libuv even though they
provide basically the same functionality have different APIs, hence once
doesn't replace the other, specially since libev is used by some
packages which probably won't work with libuv without some serious
retooling.
autogen.sh isn't that tricky, normally enabling autoreconfiguration via
PKGNAME_AUTORECONF = YES suffices to get that out of your way, as stated
in the manual (adding packages autotools).
Give that a try.
Regards.
next prev parent reply other threads:[~2014-07-18 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 12:48 [Buildroot] Replace libev with libuv Nimai Mahajan
2014-07-18 13:12 ` Gustavo Zacarias [this message]
[not found] ` <CALoSW64Uisj3oLvPVKZ1nQXgCTEnt1yLMqV+Gy7aK4U=Q9FcUA@mail.gmail.com>
2014-07-18 13:32 ` Gustavo Zacarias
2014-07-18 14:02 ` Nimai Mahajan
2014-07-18 20:26 ` Gustavo Zacarias
2014-07-18 23:36 ` Nimai Mahajan
2014-07-19 12:42 ` Nimai Mahajan
2014-07-19 13:18 ` Yann E. MORIN
2014-07-19 12:51 ` Nimai Mahajan
2014-07-19 13:20 ` Yann E. MORIN
2014-07-19 13:40 ` Nimai Mahajan
2014-07-19 23:12 ` Yann E. MORIN
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=53C91D3F.4060500@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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