On 30 Sep 2007, at 20:07, Gonzalo Garramuño wrote: > > Nope. Try the different fltk2-config switches I sent and you'll see > fltk2-config is doing all sorts of crappy stuff.
Certainly might need a bit of a tidy-out... > And fltk2-r5940 is afaik, broken on windows, where it won't even > compile > due to scandir issues. Err... It compiled just fine for me this afternoon. Maybe mingw behaves differently from whatever compiler you have? > I do agree Greg's makefile did not need to be changed, thou. It is > however a bad practice to have a variable called FLTK2CONFIG and need > that to be set with different switches, thou. > The reason it was not working for me originally was I was calling the > Makefile-fltk2 directly as: > > make -f Makefile.fltk2 FLTK2CONFIG=fltk2-config > > Totally logical. The reason was that the main Makefile does not work > when you don't have fltk1 installed. You did check the Readme first, did you? It explicitly tells you to edit the master Makefile to indicate whether you want fltk1, fltk2 or both to build. When I did that, I managed to build just 1, just 2, or both, quite happily. > I had also tried with --use-images, but then the error would be > different, as the --use-images flag would lead to fltk2_images > appearing > twice and leading to other link problems (but that was probably > after I > added $(IMGLIB) to Greg's makefile). > > The reason why it works for you guys is that the --ldstaticflags is > magically adding the image library. Well - you MUST set either --ldflags or --ldstaticflags for the final linking, and both of these correctly return fltk2_images. Just setting --libs is seldom (e.g. never) enough (but it does seem to be broken. On fltk1 also, FWIW.) > fltk2-config is currently *severely* broken, as it just outputs a > lot of > incorrect crap whenever you ask for different flags. I don't think it is *severely* broken. Just a bit broken...! > Try the different flags and you'll see the flags don't do what they > say > they do. --ldflags and --ldstaticflags will return libraries (!), Actually - that's quite common, a lot of config scripts do that... The --ld* options provide a list of all the "flags" that need to be passed to the linker, many of which aren't "flags" at all! > instead of just the flags. And "--use-images --libs" does nothing. Yes - and the fltk1 script seems to manifest the same "feature" too. Anyway this is way off-topic for the title of this thread now - can we agree that Greg's Makefiles are actually OK as-is? Or do you really believe they need to be changed? I for one think they are fine, if used as he describes in the Readme. Cheers, -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
