DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current


I agree that this seems like a sensible move, i.e. putting the HAVE_CAIRO
macro inside a "fltk namespace" by changing its name to be fltk specific,
e.g. FLTK_HAVE_CAIRO.

Note that there is also a USE_CAIRO macro that ought to be similarly
changed to FLTK_USE_CAIRO (or whatever we agree is the appropriate FL
specific naming...)

A very quick (and probably wrong!) scan with grep suggests that at least
the following files would need to be checked for these macros:

./cairo/Fl_Cairo.cxx
./CMakeLists.txt
./config.h
./configh.cmake.in
./configh.in
./configure
./configure.in
./documentation/Doxybook
./documentation/Doxyfile
./FL/Fl.H
./FL/Fl_Cairo.H
./FL/Fl_Cairo_Window.H
./fluid/CMakeLists.txt
./ide/VisualC2008/*.vcproj
./ide/VisualC2008/config.h
./ide/VisualC2010/*.vcxproj
./ide/VisualC2010/config.h
./README.Cairo.txt
./test/cairo_test.cxx
./test/CMakeLists.txt

Though I may have missed a few. We'd need to regenerate the PDF as well,
since it also references these macros too.


Link: http://www.fltk.org/str.php?L2504
Version: 1.3-current

_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to