..or for me, worse than that is this suggestion in that README file:
BAD: - If creating a new fltk project remove subdirectory FL\ from includes.
BAD: #include <FL\Fl.H> becomes #include <Fl.H>
No, that is BAD advice.
That goes against all fltk example code, docs, and public projects.
And the use of backslashes in the example for #includes is wrong too.
The only right way to do an #include for FLTK files, windows or unix,
is e.g.
GOOD: #include <FL/Fl.H>
All that one has to do is set up Microsoft's "/I" compiler flag,
or if GNU G++ is involved, g++'s "-I" flag to point to the directory
that is the parent of the FL/ directory.
Apparently the parent article for that README file is this 2014 article:
https://groups.google.com/forum/#!topic/fltkgeneral/wPdHz2NA2R8
> The fltk README’s will guide you in setting up VS or mingw.
Yes, and for doing a codeblocks setup, I'd look for other articles
as a source.
I know the FLTK docs don't go into codeblocks.. I think only our
README.Unix.txt mentions it. We don't have anything for Windows
in that regard, and perhaps should.