> I'm hoping to try to build (and in some cases rebuild) some of the > applications listed under FLTK Links using the latest version of mingw and > msys. I downloaded fltk 1.3.0 since that's listed as stable and am > attempting to use it. Is this that the best version of the library to > start with or is another version recommended?
It is the right version to use. > I noticed a bug listed here: > http://www.mail-archive.com/[email protected]/msg08296.html > Am having the same issue. Was wondering if this was fixed in another > version (hence the question am I using the best version) or should I just > add !defined(__MINGW32__) to the include file? I've never seen this recently - you are running configure in the Msys shell, and building there too? Maybe Albrecht has an idea - he uses a more recent mingw/Msys combination than I do! > I also had a problem with the following line in the configure file: > msyspath=`mount | grep '\/usr' | grep -v '\/usr\/bin' | cut -d ' ' -f -1 | > sed -e 's/\\\/\// g'` > I use the /etc/fstab to set various directories in MinGW. The goal is to > make it more like the Linux FHS. How to do this is documented in some of > the MinGW FAQs. The result of mount | grep '\/usr' | grep -v '\/usr\/bin' > on my machine is: > \mingw\msys\usr\include > \mingw\msys\usr\local > \mingw\msys\usr\share > \mingw\msys\usr\sbin > \mingw\msys\usr\lib > \mingw\msys\usr\src > C:\mingw\msys > > Since I have multiple directories (and the line attempts to set msyspath > to all of those directories) the following setup in configure #define > FLTK_DOCDIR "$msyspath/local/share/doc/fltk" prevents fltk from building > without my patching it. Urgh... Had edit makeinclude after running configure maybe? ;-) > I changed the following in configure and it works on my system: > - msyspath=`mount | grep '\/usr' | grep -v '\/usr\/bin' | cut -d ' ' -f > -1 | sed -e 's/\\\/\// g'` > + msyspath=`mount | grep '\/usr' | grep -v '\/usr\/' | cut -d ' ' -f -1 > | sed -e 's/\\\/\// g'` > > mount | grep '\/usr' | grep -v '\/usr\/' brings back only: > C:\mingw\msys on /usr type user (binmode,noumount) > > However, was wondering if there was a way to override running this code > and supply msyspath to the configure file myself. Is there any way to > pass this location in to configure (maybe as an environment variable)? > One last thing I wanted to know about building with mingw is with regards > to the following compiler flags: > -static-libgcc -static-libstdc++ > I'm trying to build the applications so I don't have to distribute the > standard c and c++ libraries. According to the MinGW web site, there's an > exception for compiling in these two libraries, so one is allowed to > compile/link them in and still distribute the executables (without > worrying about GPL/LGPL). What's the best way to use the compiler flags > with fltk? I tried compiling the fltk libraries with them, but then when > I use the libraries with other applications and set the flags there too, I > get errors. Am I better off building without the compiler flags and only > using them when I build an executable that uses the fltk libraries? Was > wondering how others were handling this situation. That'll be one for Albrecht I think - he looked into this more than I did... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 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. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
