Hi,
The cygwin folk have made the rather odd choice to move their fltk package to
use X11 instead of native Windows GDI. Therefore, I have had to build fltk
myself. I found two issues which seem worth reporting.
The first is a cygwin packaging issue. They have two uuid libraries. One
relates to X11, and the other is the Windows library. If you have the files
/usr/lib/libuuid.a, /usr/lib/libuuid.dll.a, and /usr/lib/libuuid.la they are
from the X11 package, and will prevent the Windows UUID library being picked up
from /usr/lib/W32api at link time. I just renamed the offending files to get
the out of the way for now.
The second is a patch which is needed to FLTK's configure.in I had to add
definitions for USE_OPENGL32, as follows:
dnl OS-specific pre-tests...
case $uname in
CYGWIN* | MINGW*)
# Handle Cygwin option *first*, before all other tests.
AC_ARG_ENABLE(cygwin, [ --enable-cygwin use the CygWin
libraries [default=no]])
if test x$enable_cygwin != xyes; then
# NOTE: We can't use ARCHFLAGS for this, since it does not work
# with some of the function tests - Cygwin uses a
# different C library...
CFLAGS="$CFLAGS -mno-cygwin -DUSE_OPENGL32"
CPPFLAGS="$CPPFLAGS -mno-cygwin -DUSE_OPENGL32"
CXXFLAGS="$CXXFLAGS -mno-cygwin -DUSE_OPENGL32"
LDFLAGS="$LDFLAGS -mno-cygwin"
DSOFLAGS="$DSOFLAGS -mno-cygwin"
else
CFLAGS="$CFLAGS -DUSE_OPENGL32"
CPPFLAGS="$CPPFLAGS -DUSE_OPENGL32"
CXXFLAGS="$CXXFLAGS -DUSE_OPENGL32"
fi
With these changes, and --enable-cygwin on the command line for configure I
have been able to build and use FLTK 1.1.10 quite happily on the current cygwin
platform.
Steve
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
