On 10.05.2011 10:05, MacArthur, Ian (SELEX GALILEO, UK) wrote: > >> hello, I compiled FLTK 1.3 on windows XP with this configure >> options (as suggested to me on STR #2622): >> ./configure --enable-localjpeg --enable-localpng >> --enable-localzlib --host=i686-w64-mingw32 >> --build=i686-w64-mingw32 CC=i686-w64-mingw32-gcc >> CXX=i686-w64-mingw32-g++ CFLAGS=-DMINGW_WINGDI_FIXED >> CXXFLAGS=-DMINGW_WINGDI_FIXED LDFLAGS="-static-libgcc >> -static-libstdc++" > > You don't say what tool you are using - I'm guessing mingw on the basis > of the link line.
Cygwin > Where did you get that configure line from? It looks unecessarily > complicated for a mingw build hosted on a Windows host. In a somewhat shorter form ... from me. > It might make sense for a mingw build cross-compiling from a linux host > though... He *is* cross-compiling on Windows (Cygwin) with the mingw64 cross compiler. That's the new form of "-mno-cygwin" :-( FYI: The CXXFLAGS define is necessary to work around a bug in MinGW's w32api (wingdi.h) that has been fixed in the *mingw64* w32api files and /will/ be fixed in a new release of w32api for MinGW (I supplied a preliminary patch, see STR #2622). The real problem is more complicated though. <OT here in fltk.general> To Ian: it's your code, and it compiles well with the /broken/ MinGW wingdi.h, but not with Visual C++ (STR #2623) and the corrected mingw64 header files. If you have a better idea than an autoconf "feature" test, please give a comment on STR #2622. Thanks. </OT> Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
