On Mar 15, 2010, at 12:47 PM, Matthias Melcher wrote: >> ... >> Just casually tracing through the #include paths: >> >> 1) Fl.cxx (a C++ file) seems to include.. >> 2) Fl_cocoa.mm (an Objective C file) > > Yes, I am quite unhappy about that. It seems like a horrible hack to include > a file of another langeuage and then force that language on the original > file. It's for historic reasons, but maybe we can find a plausible way in the > Makefile to avoid this kludge?!
We could AC_SUBST the "correct" top-level module to use ("Fl" or "Fl_cocoa"), and then have Fl_cocoa.mm include Fl.cxx. The src/Makefile would just specify one or the other, with the value in the makeinclude file. ________________________________________ Michael Sweet, Easy Software Products _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev