Re: About "./configure" Checking the build environment
On Wed, Jun 26, 2019 at 07:13:52AM +0800, CandyMI <869646...@qq.com> wrote: > I recently tried to install libev painlessly on Win32 to run my poor Lua Web > Web framework on it. > > > However, Win32 requires embedded compilation to take effect. Can I get better > libev build suggestions here? Other than using cygwin or windows linux emulation, or their services for unix, the only way would be to provide your own config.h file in advance. But since windows doesn't have as standard ABI or even API, and most compilers being incomaptible to each other, it's close to impssible to do anything else, as libev can't know the compilation environment in advance - that's what configure would be for. Even then, configure couldn't guess how you want to map handles to fds and vice versa. -- The choice of a Deliantra, the free code+content MORPG -==- _GNU_ http://www.deliantra.net ==-- _ generation ---==---(_)__ __ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schm...@schmorp.de -=/_/_//_/\_,_/ /_/\_\ ___ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/mailman/listinfo/libev
Re: About "./configure" Checking the build environment
Yes, it is always different from other platforms (want to highlight its particularity) At least I have never had such an annoyance when writing code on the OSX platform. I recently tried to install libev painlessly on Win32 to run my poor Lua Web Web framework on it. However, Win32 requires embedded compilation to take effect. Can I get better libev build suggestions here? -- Original -- From: "Marc Lehmann"; Date: Wed, Jun 26, 2019 06:51 AM To: "CandyMi"<869646...@qq.com>; Cc: "libev"; Subject: Re: About "./configure" Checking the build environment On Wed, Jun 26, 2019 at 03:43:33AM +0800, CandyMI <869646...@qq.com> wrote: > I checked and found that the "./configure" file was taken from the package > file of libev-4.25.tar.gz. Good to hear :) > By the way, I saw the macro definition of IOCP in "ev.c". Does it mean that > libev will have a plan supported by the Windows platform? libev has pretty much always (at least since 2007) supported windows using its select backend. the reference to iocp is a reference to windows i/o control ports, for which I tried to make a more performant interface, but it turned out that iocps (at least at the time) only supported very few handle types, many tcp socket types not among them, so it would be even less useful than select which at least seems to support all socket types, and the code was dropped. -- The choice of a Deliantra, the free code+content MORPG -==- _GNU_ http://www.deliantra.net ==-- _ generation ---==---(_)__ __ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schm...@schmorp.de -=/_/_//_/\_,_/ /_/\_\___ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/mailman/listinfo/libev
Re: About "./configure" Checking the build environment
On Wed, Jun 26, 2019 at 03:43:33AM +0800, CandyMI <869646...@qq.com> wrote: > I checked and found that the "./configure" file was taken from the package > file of libev-4.25.tar.gz. Good to hear :) > By the way, I saw the macro definition of IOCP in "ev.c". Does it mean that > libev will have a plan supported by the Windows platform? libev has pretty much always (at least since 2007) supported windows using its select backend. the reference to iocp is a reference to windows i/o control ports, for which I tried to make a more performant interface, but it turned out that iocps (at least at the time) only supported very few handle types, many tcp socket types not among them, so it would be even less useful than select which at least seems to support all socket types, and the code was dropped. -- The choice of a Deliantra, the free code+content MORPG -==- _GNU_ http://www.deliantra.net ==-- _ generation ---==---(_)__ __ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schm...@schmorp.de -=/_/_//_/\_,_/ /_/\_\ ___ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/mailman/listinfo/libev
Re: About "./configure" Checking the build environment
Thank you for your prompt reply. I checked and found that the "./configure" file was taken from the package file of libev-4.25.tar.gz. I forked a code from CVS on my github, and now I think I should delete these files. :) By the way, I saw the macro definition of IOCP in "ev.c". Does it mean that libev will have a plan supported by the Windows platform? -- Original -- From: "Marc Lehmann"; Date: Wed, Jun 26, 2019 03:27 AM To: "CandyMI"<869646...@qq.com>; Cc: "libev"; Subject: Re: About "./configure" Checking the build environment On Wed, Jun 26, 2019 at 01:15:25AM +0800, CandyMI <869646...@qq.com> wrote: > When I tried to build libev based on "configure", it didn't try to detect if > the system contains the following "linux/aio_abi.h" file Unless I build with > "sh autogen.sh". > > > Does this mean that using "./configure" alone is wrong? Hi! linux/aio_abi.h is not checked or used in any released version of libev, so you must be using a CVS checkout, is this correct? If not, where did you get your copy? CVS does not contain a ./configure file, so where is your configure file from? When building for CVS, you indeed first need to generate a configure script by running autogen.sh. The release tarballs would contain all the necessary files pregenarated, and its configure scirpt should work. So in short, in a release tarball, ./configure should work. In a CVS checkout, there shouldn't be a configure script. -- The choice of a Deliantra, the free code+content MORPG -==- _GNU_ http://www.deliantra.net ==-- _ generation ---==---(_)__ __ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schm...@schmorp.de -=/_/_//_/\_,_/ /_/\_\___ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/mailman/listinfo/libev
Re: About "./configure" Checking the build environment
On Wed, Jun 26, 2019 at 01:15:25AM +0800, CandyMI <869646...@qq.com> wrote: > When I tried to build libev based on "configure", it didn't try to detect if > the system contains the following "linux/aio_abi.h" file Unless I build with > "sh autogen.sh". > > > Does this mean that using "./configure" alone is wrong? Hi! linux/aio_abi.h is not checked or used in any released version of libev, so you must be using a CVS checkout, is this correct? If not, where did you get your copy? CVS does not contain a ./configure file, so where is your configure file from? When building for CVS, you indeed first need to generate a configure script by running autogen.sh. The release tarballs would contain all the necessary files pregenarated, and its configure scirpt should work. So in short, in a release tarball, ./configure should work. In a CVS checkout, there shouldn't be a configure script. -- The choice of a Deliantra, the free code+content MORPG -==- _GNU_ http://www.deliantra.net ==-- _ generation ---==---(_)__ __ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schm...@schmorp.de -=/_/_//_/\_,_/ /_/\_\ ___ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/mailman/listinfo/libev
About "./configure" Checking the build environment
When I tried to build libev based on "configure", it didn't try to detect if the system contains the following "linux/aio_abi.h" file Unless I build with "sh autogen.sh". Does this mean that using "./configure" alone is wrong? checking sys/signalfd.h usability... yeschecking sys/signalfd.h presence... yeschecking for sys/signalfd.h... yeschecking linux/aio_abi.h usability... yeschecking linux/aio_abi.h presence... yeschecking for linux/aio_abi.h... yeschecking for inotify_init... yeschecking for epoll_ctl... yes___ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/mailman/listinfo/libev
