This is intentionally committed to the 'master' branch although it is
currently only useful for FLTK 1.3.x ABI checks.
In the future we will need it for FLTK 1.4.x or higher.
Generating driver documentation can now be configured with CMake. The new
configuration OPTION_INCLUDE_DRIVER_DOCUMENTATION is "marked as advanced"
since only advanced users and/or FLTK developers need this.
Previously this could only be achieved by editing documentation/Doxyfile.in.
Added missing documentation option descriptions as well.
Note: current mail notifications are configured for first tests.
We may need to reconfigure this later.
See build logs at https://travis-ci.com/fltk/fltk
This implementation differs from existing fltk-test and also gitlab implementation :
- minimum, fast light implementation: stripoped all unused constructions compared to other implementations
- supports successful builds of four targets (linu, osx and then gcc and clang for each of them)
- uses before_script instead of before_install
- uses after_success for building documentation, instead of building always if error
- only builds documentation on linux targets for now (can easily change if future)
... if Cairo was requested (OPTION_CAIRO or OPTION_CAIROEXT) but
Cairo was not found. CMake generation is terminated with a fatal error.
The user has two choices: install Cairo libs and headers or disable
OPTION_CAIRO and OPTION_CAIROEXT.
See https://github.com/fltk/fltk/issues/5
As Manolo pointed out the questionable variable was not used (read)
in this case of the switch statement, hence it can be removed.
Quick fix to repair a case when Fl_Menu_Item::pulldown() was called with only
five arguments (argument pbutton == null) as discussed here:
d87ac9b597 (comments)
Files without '.txt' suffix can't be handled well by Windows (users),
hence renaming such text files to *.txt makes FLTK more "Windows-friendly".
There are a few exceptions (this is intentional): README and other files
in bundled libraries (maintained upstream) are not changed.
The svn contained empty directories, e.g., test/blocks.app/Contents/MacOS/
Git apparently can't store empty directories.
The test/Makefile is modified to create these directories at build-time.
