GitLab

drop unused valgrind package from Travis build slave installation

switch one Trevis build to Release mode

enable Travis ccache to speed up CI builds

run parallelized builds on Travis CI

CMake: use threads if allowed and found, not just if found.

... and remove explicit gcc installation (will be installed with g++
automatically)

When using INSTANTIATE_TEST_CASE_P with a lambda function which uses
'info' as parameter name, GCC complains that this would shadow
parameter 'info' used in the macro's VA_ARGS call.

This turns on optimization which allows the compiler to discover more
problems and omit some more warnings.

Fix WhenSorted() documentation example

If the user's cmakelists.txt first look for threads using
find_package(Threads), then set(gtest_disable_pthreads ON),
and then include googletest. GoogleTest will not look for
threads. But since they have already been found before in
user's cmakelists, it will use them regardless.

This helped me fix build issue in darktable-org/rawspeed
on windows/MSYS2, even though there are threads, and they
are usable, googletest build was failing with issues
about AutoHandle. I was first looking for threads, and only
then including googletest, so no matter the value of
gtest_disable_pthreads, it failed.

The other obvious solution is for user to first include
googletest, and only then look for threads by himself.

Performance fixes reported by cppcheck

Wrong version reported (1.7.0 should be 1.8.0)

use cmake build type defined in .travis.yml for travis builds

AppVeyor MinGW-w64 test build

change links from former code.google.com to current github repository

fix example's comment

Moved the ignoring of *.pyc files to top level

# Conflicts:
#	.gitignore