Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Replace libev with libuv
Date: Fri, 18 Jul 2014 10:32:59 -0300	[thread overview]
Message-ID: <53C9220B.9060809@zacarias.com.ar> (raw)
In-Reply-To: <CALoSW64Uisj3oLvPVKZ1nQXgCTEnt1yLMqV+Gy7aK4U=Q9FcUA@mail.gmail.com>

On 07/18/2014 10:30 AM, Nimai Mahajan wrote:

> Already tried that and it fails to build. I will give you the exact
> error when I am by my PC again. And you are right both libraries are for
> different purposes, I guess it would have been more accurate to say many
> projects can make better use of libuv than libev. I just like that libuv
> is significantly better documented which in itself makes it more usable.
> I am using other autogen.sh packages as a template but they all seem to
> have their own custom hooks which is what is confusing me. Thanks for
> the help BTW.

Hi.
Keep the list cc'ed, you've got a better chance of getting help with
everyone rather than just me, and also other people might be interested.
Yes please do, normally AUTORECONF is enough but there are a couple of
difficult packages that need some extra help.
Regards.

  parent reply	other threads:[~2014-07-18 13:32 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
     [not found]   ` <CALoSW64Uisj3oLvPVKZ1nQXgCTEnt1yLMqV+Gy7aK4U=Q9FcUA@mail.gmail.com>
2014-07-18 13:32     ` Gustavo Zacarias [this message]
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=53C9220B.9060809@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