> In case anyone is still following this, here:
>
> http://www.imm.uklinux.net/fltk/fltk118-utf8-2007-07-14.tar.bz2
>
> is another snapshot. No really big changes since the last snapshot, but
> I've added a few extra demo programs to the test directory and done a
> little tidying up.
> I've been trying to keep my baseline in synch with the 1.1.8 sources, so
> it should be (mostly) as per the recent 1.1.8 napshots.
>
> Once again, if you are using this, check the README and CAUTIONS files...
>
> Cheers,
> --
> Ian

First off, thanks Ian (and all others) for the work all of you have been doing 
on this. Some people have been asking about i18n at GIDForums and this seems to 
be a good time for me to start using the UTF-8 version to see if the 
Localization stuff can be used with it.

Since I use CygWin (XP w/AMD Turion64) I've run into a problem with compiling 
the latest posted version fltk118-utf8-2007-07-14.tar.bz2. It has to do with 
X11.

./configure --enable-cygwin --enable-threads --enable-localzlib 
--enable-localjpeg --enable-localpng

OUTPUT during make
------------------
=== making src ===
Compiling Fl.cxx...
In file included from ../FL/fl_utf8.H:57,
                 from ../FL/Fl.H:31,
                 from Fl.cxx:33:
./FL/Xutf8.h:49:19: X11/X.h: No such file or directory
./FL/Xutf8.h:50:22: X11/Xlib.h: No such file or directory
./FL/Xutf8.h:51:25: X11/Xlocale.h: No such file or directory
./FL/Xutf8.h:52:23: X11/Xutil.h: No such file or directory

And so on from there.

Since doing a ./configure --disable-cygwin DOES build to completion (with the 
same configure line) my guess is it's a check for WIN32 without an offset to 
see if CYGWIN is defined or not. Over the last few years that usually seems to 
be the culprit. I'll try to suggest a correction during the week if no one gets 
to it.

Mark
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to