darkChild wrote: [Ian wrote:] >> For what it is worth, I usually build all variants of fltk on winXX >> hosts using mingw+Msys (I fond that to be easier to set up and use >> than cygwin, and more reliable too...)
I found that cygwin has been pretty stable and easy to setup during the last years - however there _have_ been some changes regarding bash and the new X server that could make troubles... And the upcoming new version 1.7 and gcc 4.x may also cause some troubles for users (especially because gcc -mno-cygwin will have to be replaced by another compiler command that is not yet completely clear). [BTW.: We will have to take care of that in FLTK configure in the near future]. >> There's a HowTo here: >> >> http://www.fltk.org/articles.php?L598 >> >> and this might help, although it is not directly relevant... >> >> http://www.fltk.org/articles.php?L599 > > Thanks. That was not obvious at all to me. I "assumed" that FLTK2.x were the > latest releases for this toolkit as it appeared logically that way. Summary for use of cygwin for compiling FLTK. If you have installed cygwin already, download the FLTK sources. As others said already, you should use the stable 1.1.9 or 1.1.10-rc2. If you need UTF-8 character encoding, then try 1.3.0 (not released yet). cd to the fltk root dir, and just type "make" [1]. This ought to just work, if you have the compiler (gcc) and autoconf installed. Optionally, run "make install", but that is not necessary for development and testing. Now, if you want to compile and link your own applications, you should use fltk-config to find the needed command line switches for the compiler and linker, or to compile and link your (one source file) app in one step: 1) fltk-config --compile test.cxx # compile and link (one file) 2) fltk-config --cxxflags # show compiler flags 3) fltk-config --ldflags # show linker flags Note that you must use the full path to fltk-config if you didn't run "make install". If you do it this way in a cygwin shell, then you will never need to use the /cygdrive/c/... full path, just use /usr/local/..., /home/... or similar, unless your sources are not within the cygwin tree. Using cygwin for compiling and linking is almost the same as mingw, so that you can use the above mentioned articles as a reference as well. The default options will build native windows applications, without cygwin dependencies. --- [1] using only "make" runs autoconf and ./configure for you. If you want to configure FLTK with some options, run autoconf and then ./configure [--options ...] before make. Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
