> All my win32 builds have been with msys/mingw, so it's entirely possible > I've missed something on the cygwin front. I don't have that toolchain > at all now. > > Does a "regular" 1.1.8 snapshot build OK for you with cygwin? I thought > I had mostly kept my configure script the same but perhaps I messed up.
How about "non-forked 1.1.x branch current svn". :) Yes, it builds both as --enable-cygwin and --disable-cygwin. I do however get the : integer expression expected 2 : integer expression expected 4 : integer expression expected 4 : integer expression expected 4 : integer expression expected 4 after the sizeof int etc with the --disable-cygwin stuff (during ./configure). Not so with the --enable-cygwin. > Also, on another front, do you actually need the cygwin support? We used > to use cygwin here a lot, even though our win32 targets did not need or > use the cygwin layer, ... Short answer, No. Long answer, It depends. For me, perhaps, it is more of a personal preference. When I started using gcc I could never get the mingw stuff working right with my palmOS toolchain. Eventually I just got used to the cygwin-tricities. Couple that with the fact I rarely distribute anything in binary form. When I do I just uninstall my cygwin build and install the non-cygwin one. Most likely it's just that all this is a hobby for me. You know, for the fun of it. I've always liked catching the CygWin build problems with 1.1.x here. Makes me think back to when all my friends were using PC's and I had my trusty Amiga4000. 33MHz worth of Motorola 68040, running a raytracer. Sometimes I really miss NewTek... Mark _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
