> > > hello, I compiled FLTK 1.3 on windows XP with this configure=20 > > options (as suggested to me on STR #2622): > > ./configure --enable-localjpeg --enable-localpng=20 > > --enable-localzlib --host=3Di686-w64-mingw32=20 > > --build=3Di686-w64-mingw32 CC=3Di686-w64-mingw32-gcc=20 > > CXX=3Di686-w64-mingw32-g++ CFLAGS=3D-DMINGW_WINGDI_FIXED=20 > > CXXFLAGS=3D-DMINGW_WINGDI_FIXED LDFLAGS=3D"-static-libgcc=20 > > -static-libstdc++" > > You don't say what tool you are using - I'm guessing mingw on the basis > of the link line.
I'm using the mingw (pseudo) cross compiler from cygwin (cygwin to mingw, something like the old --mno-cygwin option) > Where did you get that configure line from? It looks unecessarily > complicated for a mingw build hosted on a Windows host. look at SRT #2622 (http://www.fltk.org/str.php?L2622), it won't compile otherwise. > It might make sense for a mingw build cross-compiling from a linux host > though... you almost got it... > > everything eventually compiled and all the test programs run=20 > > as they should. > > now I have a vary basic question: all the files in the lib=20 > > directory are *.a files (e.g. libfltk.a), unlike regular=20 > > library files on windows which are *.lib (for static) or=20 > > *.dll (for dynamic). the FLTK libs on cygwin (which depend=20 > > on X11) are dlls. > > so is anything wrong here? > > No, that looks about right for a gcc/mingw generated build. The MS tools > generate .lib and .dll files, the gcc tools generate .a and .so files. > > As a general rule, for "plain" C-code, that does not matter and they can > be more or less interchanged. > > However, C++ compilers work in such a way that the ABI and name-mangling > is not compatible, so if you geberate a lib file (of any sort) with a > given compiler it probably will not be compatible with a different > compiler... > > So, I'm not sure what your question is but: > > - For gcc/mingw built files, the outputs you have are normal. > > - These files will work fine on pretty much any recent Windows host, > *if* you are using the mingw tools to build your app. > > - These files will not be compatible with the MS tools, so you can't use > them in Visual Studio (for example) > > > SELEX Galileo Ltd > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS= > 14 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > thank you! basically all I wanted to knew is if I can uninstall the dlls in cygwin (and install my custom build) without lousing any functionality, so the answer is yes, right? (other then using with visual studio which I can't anyway as the cygwin dlls are X11 based). thanks again. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
