ソースを参照

- removed windows line endings

svn:r8323
Mike Chiussi 18 年 前
コミット
72e16865e9
1 ファイル変更80 行追加80 行削除
  1. 80 80
      Win32Build/mingw/CHANGES-libevent

+ 80 - 80
Win32Build/mingw/CHANGES-libevent

@@ -1,80 +1,80 @@
-Changes related to compilation under MinGW/any sane win32 gcc
+Changes related to compilation under MinGW/any sane win32 gcc
-=============================================================
+=============================================================
-
+
-* event.c
+* event.c
-- If gcc include "WIN32-Code/misc.h" instead of "misc.h"
+- If gcc include "WIN32-Code/misc.h" instead of "misc.h"
-
+
-* WIN32-Code/misc.h
+* WIN32-Code/misc.h
-- Add struct prototypes for timeval and timezone
+- Add struct prototypes for timeval and timezone
-
+
-* buffer.c
+* buffer.c
-- changed type of "i" from "u_int" to "unsigned int". My MinGW wasn't 
+- changed type of "i" from "u_int" to "unsigned int". My MinGW wasn't 
-  recognizing it. (u_int is normally typedef'ed to unsigned int, right?)
+  recognizing it. (u_int is normally typedef'ed to unsigned int, right?)
-
+
-* evbuffer.c
+* evbuffer.c
-- removed incorrect win32 error checking, see bufferevent_writecb().
+- removed incorrect win32 error checking, see bufferevent_writecb().
-  (this needs to be fixed by anyone planning to use evbuffer on win32)
+  (this needs to be fixed by anyone planning to use evbuffer on win32)
-
+
-* log.c
+* log.c
-- If gcc include "WIN32-Code/misc.h" instead of "misc.h" 
+- If gcc include "WIN32-Code/misc.h" instead of "misc.h" 
-
+
-* WIN32-Code/misc.c
+* WIN32-Code/misc.c
-- if gcc, include "misc.h"
+- if gcc, include "misc.h"
-- added newline at end of file to shut up gcc
+- added newline at end of file to shut up gcc
-
+
-* WIN32-Code/win32.c
+* WIN32-Code/win32.c
-- Altered the prototypes of win32_*() so their argument types didn't conflict
+- Altered the prototypes of win32_*() so their argument types didn't conflict
-  with the function definitions.
+  with the function definitions.
-- Casted types of win32_* to void inside win32ops so that it didn't conflict
+- Casted types of win32_* to void inside win32ops so that it didn't conflict
-  with the definition of eventops (gcc doesn't like this)
+  with the definition of eventops (gcc doesn't like this)
-- Altered prototype of signal_handler to be static since definition is static
+- Altered prototype of signal_handler to be static since definition is static
-  (why wasn't it like this before)
+  (why wasn't it like this before)
-- Casted the second argument of signal() to be void*, some reason my MinGW 
+- Casted the second argument of signal() to be void*, some reason my MinGW 
-  doesn't have sighandler_t typedef'ed.
+  doesn't have sighandler_t typedef'ed.
-
+
-* configure.in
+* configure.in
-- some code to check if we are compiling for WIN32. 
+- some code to check if we are compiling for WIN32. 
-  
+  
-* Makefile.am
+* Makefile.am
-- if BUILD_WIN32 is defined, include WIN32-Code/misc.c and
+- if BUILD_WIN32 is defined, include WIN32-Code/misc.c and
-  WIN32-Code/win32.c as source files.
+  WIN32-Code/win32.c as source files.
-- if WIN32, do not build test stuff. (not windows friendly)
+- if WIN32, do not build test stuff. (not windows friendly)
-- if WIN32, explicitly link to ws2_32.dll
+- if WIN32, explicitly link to ws2_32.dll
-  
+  
-Notes
+Notes
------
+-----
-- We assume that if __GNUC__ is undefined we are building with MSVC
+- We assume that if __GNUC__ is undefined we are building with MSVC
-- If the user wishes to build a dll, they are on their own, the syntax is 
+- If the user wishes to build a dll, they are on their own, the syntax is 
-  compiler specific. 
+  compiler specific. 
-- Getting this warning from libtool, no idea why
+- Getting this warning from libtool, no idea why
-  "libtool: link: warning: undefined symbols not allowed in i686-pc-mingw32
+  "libtool: link: warning: undefined symbols not allowed in i686-pc-mingw32
-   shared libraries"
+   shared libraries"
-
+
-  
+  
-Changes related to "custom eventops"
+Changes related to "custom eventops"
-====================================
+====================================
-
+
-* configure.in
+* configure.in
-- add argument --enable-custom-eventops, sets USE_CUSTOM_EVENTOPS in config.h
+- add argument --enable-custom-eventops, sets USE_CUSTOM_EVENTOPS in config.h
-- add argument --enable-custom-code, sets USE_CUSTOM_CODE in Makefile
+- add argument --enable-custom-code, sets USE_CUSTOM_CODE in Makefile
-
+
-* Makefile.am
+* Makefile.am
-- if USE_CUSTOM_CODE, include custom/custom.c as a source file.
+- if USE_CUSTOM_CODE, include custom/custom.c as a source file.
-  (I can't think of a way to pass a string to Makefile.am, so I'm stuck naming
+  (I can't think of a way to pass a string to Makefile.am, so I'm stuck naming
-   the new source file custom.c. It just seems simpler this way, but I'm open 
+   the new source file custom.c. It just seems simpler this way, but I'm open 
-   to suggestions)
+   to suggestions)
-   
+   
-* event.c
+* event.c
-- if USE_CUSTOM_EVENTOPS, use eventops as defined in custom-eventops.h
+- if USE_CUSTOM_EVENTOPS, use eventops as defined in custom-eventops.h
-
+
-Notes
+Notes
------
+-----
-Just in case it isn't completely obvious, the goal of "custom eventops" is to
+Just in case it isn't completely obvious, the goal of "custom eventops" is to
-allow the user to include their own event processing system without requiring a 
+allow the user to include their own event processing system without requiring a 
-fork. This is accomplished through two parts. Firstly, by allowing the user to 
+fork. This is accomplished through two parts. Firstly, by allowing the user to 
-redefine eventops. (for example, the user may wish to use epoll() exclusively). 
+redefine eventops. (for example, the user may wish to use epoll() exclusively). 
-Secondly, by allowing the user to include their own code to support a private
+Secondly, by allowing the user to include their own code to support a private
-eventop (note, this may not be necessary, as the user may choose to include 
+eventop (note, this may not be necessary, as the user may choose to include 
-already defined eventop's. 
+already defined eventop's. 
-
+
-
+