[imapfilter-devel] Patch for cygwin

[Lefteris Chatzibarbas]

On Fri, Apr 30, 2004 at 06:46:22AM +1000, Gautam Gopalakrishnan wrote:
> On Thu, Apr 29, 2004 at 11:55:39AM +0300, Lefteris Chatzibarbas wrote:
> > On Thu, Apr 29, 2004 at 10:20:49AM +1000, Gautam Gopalakrishnan wrote:
> > > ! all: \$(BIN)
> > > ! 
> > > ! \$(BIN): \$(OBJ)
> > > ! EOF
> > 
> > I'm changing this in the Makefile, because it's more correct this way.
> > 
> > Thus, on cygwin, one could also do a:
> > 
> >   make BIN=imapfilter.exe
> > 
> > ... and build without problems (or not?).
> 
> But it would require people to know the build variables. I'd
> rather not have it like this, but I shall leave it to you.

Yes, I know.

I'm thinking of getting rid of the config Bourne shell script, because this
test and many others are required in order to build without user intervention
in some systems.  I will then reside only to a well commented Makefile and
INSTALL file with details for each system (BSD, Linux, Solaris, Cygwin,
etc.)...

Also, I don't like GNU autoconf (I wonder how would it deal with Debian's
change of name of the Lua 5.0 library from "liblua" to "liblua50"?), so I'm not
considering it as an alternative. 

> > > + /* 
> > > + 	Cygwin blotch
> > > + 	2048 is the value in limits.h in cygwin
> > > +  */
> > > + #ifndef LINE_MAX
> > > + #define LINE_MAX 2048
> > > + #endif
> > 
> > Cygwin doesn't define LINE_MAX inside <limits.h> as the POSIX standard
> > describes?
> 
> I don't what I was smoking when I wrote that. LINE_MAX is not defined in
> limits.h in cygwin, precisely why I had to put this in. Code is right,
> not the comments. I used 2048 from my Linux's limit.h.

I will correct this, too.