DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2622 Version: 1.3-current @some868one: according to your configure options, the one in /usr/i686-w64-mingw32... should be the one that is used in your compilation (which is the MinGW cross compiler in 32-bit mode). The one in usr/x86_64-w64-mingw32 is for the MinGW cross compiler in 64-bit mode, whilst the other one in /usr/include/w32api is for the Cygwin compiler (to Manolo: i.e. the compiler that depends on cygwin1.dll and defines __CYGWIN__). As for what to edit in the makeinclude file: this would be the binutils tools (like ar (LIBCOMMAND), ranlib (RANLIB) and windres (RC), but in current FLTK 1.3 this would probably work w/o editing makeinclude, if you specify --host=i686-w64-mingw32 and maybe also --build=i686-w64-mingw32, IIRC as configure options. I recommend to use only these options: ./configure --enable-localjpeg --enable-localpng --enable-localzlib CC=i686-w64-mingw32-gcc CXX=i686-w64-mingw32-g++ --host=i686-w64-mingw32 and try again. Note that --enable-threads is default (and not used for Windows anyway), and all your other options might also be default or even wrong. Final notes: (1) currently it is much easier to use MinGW for native Windows development, and I recommend to switch from Cygwin to MinGW, as I also did some time ago. (2) If you build with the options mentioned above, you will get a dependency on the shared versions of libstdc++ and libgcc (IIRC). You can try adding LDFLAGS="--shared-libstdc++ --shared-libgcc" to resolve this. BTW: this has nothing to do with FLTK itself, but is a new feature of gcc 4.5.x. Link: http://www.fltk.org/str.php?L2622 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
