> On 25 Sep 2009, at 18:24, Edzard Egberts wrote: > The fltk configure scripts are not cross-compilation aware, so setting > --host and --target don't really work.
Okay, now I know for sure. > The only things that the fltk configure script actually generates are > the "config.h" and "makeinclude" files. It is actually pretty easy > (trivial almost) to take the ones form your existing windows setup, or > even your linux generated ones, and tweak them by hand. This was the last thing I tried, before trying to configure "./configure" directly for cross-compiling. I made a configuration using Windows and took the different things into the Linux configuration. The direct result was, that make failed at once. > The key is usually just setting the paths in the makeinclude to point > to the correct tools. Hmm, must have been a problem of tools, but I'm not aware of paths to them inside of the configure files. Hmpf, must be the environment path! The main problem is, that there is no step-by-step approach possible, but everything must be right before it works. I will go on this way now, I think, there is not much missing... > Or, I have been told works (but have never tried...) is to run > mingw/Msys under Wine. I tried, but first problem was, that Msys always crashed, even when looking for files by using "ls" (Cygwin memory problems). Then I tried another windows bash, but the configuration also was built for Linux environment (it was easy to see because of "x11"). It seems to me, that wine is not a "Windows in a box", so configure finds all the Linux flags first. Have you been told details? I don't see, how it could work. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
