On OSX, 'gcc' is an alias for 'clang', so on OSX, both the
so-called 'gcc' and the 'clang' builds actually use clang.
It would be some work to find out which gcc to maybe install
and then use on OSX, so we disable the 'gcc' builds for now.
If someone wants actual gcc builds on OSX, they can take a
look later at
https://docs.travis-ci.com/user/languages/c/#gcc-on-macos
and experiment with finding out which gcc versions are
actually available by default and available in brew and
use those (after possible first installing them).
Check that programs including libgphoto2 headers compile
when compiled for a number of different language standards:
C: ansi c99 c11
C++: ansi c++98 c++11 c++14 c++17
For each of these language standards, if the compiler does not
compile an empty example program, we do not test whether compiling
with the gphoto2/*.h headers included works.
This will work with GCC as the compiler, and also should work with
CLANG as the compiler as CLANG is mostly compatible in these matters.
On other compilers, the test compile of the empty program should
fail, and thus no checks with the gphoto2/*.h headers included will
be performed.
C90/ANSI C apparently does not define __STDC_VERSION__, so the
C source code needed to be changed to become ANSI C compatible.
In C++ pedantic compilation source, we now use actual C++ code
instead of relying on C code working when compiled as C++ code.
In Travis CI, we now actually require both C and C++.
Allow setting SLEEP=no to disable sleep on warnings like
../configure SLEEP=no --prefix=/foo/bar ...
This is implemented with GP_SLEEP and gp_sleep similar to
m4sh's AS_ECHO and $as_echo.
Any TESTS definition causes "make check" to run a test suite,
even if no tests are actually defined.
So we remove the empty TESTS= from examples/Makefile.am, and
keep on using the TESTS in the tests/Makefile.am file.
This uses proper set operations both for GP_CAMLIB and for handling
the --with-camlibs value. This allows all GP_CAMLIB definitions to
be present at autoreconf time (as m4 code) time while some camlib
definitions being conditional at the time of the configure run (in
the sh code).
The ./configure output is still a bit verbose, but we can reduce that
verbosity later when we have found out that this works well on people's
different systems.
Fixes: https://github.com/gphoto/libgphoto2/issues/467
That one quick build is in-tree, includes sudo for "make install",
and does both "make clean" and "make uninstall".
That should exercise a few more code paths.
The handling of failing build steps has become too involved
to put it into a single command line in a ".travis.yml".
The new build script does a few things differently:
* No sudo use.
* Builds for and installs into separate root --prefix
* Builds as out of tree builds per build
The new things the new build script does:
* Print config.log and the test-suite.log files if the configure
or the "make check" stages have failed.
* Print the version information, both short and verbose.
* Print a list of the installed files.
The things the new build script does NOT do:
* Run "make clean" or "make uninstall"
We are keeping the old script lines around for the time
being. I cannot see a difference, but someone more familiar
with "vusb" and "examples/sample-afl" might.
The new print-libgphoto2-version program prints the complete
libgphoto2 version message in both short and verbose.
This functionality had not been available before, and we
want it for checking later changes to the camlib list part
of the version messages.
This should avoid some possible incompatibities in the case
of the multi line string argument to "echo", and cleans up
the code by replacing a number of "echo" commands with a
single AC_MSG_WARN.
