From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: libuv
Date: Wed, 02 Dec 2015 20:19:00 -0000 [thread overview]
Message-ID: <0406F72A-120B-425D-A0B1-0FB7598113F1@etr-usa.com> (raw)
In-Reply-To: <CAA65N5xBP-GoC5MfYc7xvBFMLunCT8nP08NcPZmY4mNfgNm6+Q@mail.gmail.com>
On Dec 2, 2015, at 12:32 PM, Mr. Coin <canard@canard.ch> wrote:
>
> Lots of project such as node.js or neovim are using libuv
> which is incompatible with Cygwin.
Why are you trying to stack two I/O abstraction layers? The whole point of libuv is that it lets you use the same code on *ix and Windows. Why do you also need Cygwin?
I realize that libuv doesn’t completely abstract the platform, but there are a bunch of libraries that you can use together to achieve that. libapr for general OS facilities, Qt/Gtk for GUIs, etc.
Presumably you’re interested in libuv rather than select(2) because you need the code to be really fast and scalable. So again, why bring Cygwin into it? That’s just going to eat up a bunch of the speed you gained by using advanced I/O polling mechanisms.
If you’re just trying to get node running, why not use the native binaries?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-12-02 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 19:32 libuv Mr. Coin
2015-12-02 19:49 ` libuv Tony Kelman
2015-12-02 20:19 ` Warren Young [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=0406F72A-120B-425D-A0B1-0FB7598113F1@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).