included in everything.

  which will invoke the destructor for the Glib::Source.
  
  Added an integration test to prove it
  
  (LP: #1085590)

glibmm usage

(LP: #1021139)

If the environment (like valgrind in ExperimentalMemCheck) is so slow that it
took more than 50ms to schedule the tests, then they would all be overdue
on startup (instead of just one of them) and the order would not be
predictable. So I spread the timers out over longer intervals and reduced
the number of repetitions to stop the new test from taking too long.

gtest_add_tests is good for the basic Google Test usage, but its source
based scanning falls short in a couple of areas - namely it requires that
there be no space between TEST* and ( and it also does not work for templated
tests.

compiz_discover_tests builds a small C++ program to parse the output
of --gtest_list_tests and adds those at make-time to the CTestTestfile.cmake
in the current binary directory. This allows us to correctly introspect the test
binary and get /all/ the tests regardless of the source file.

            
Strange. All versions of gcc should have reported this as an error. But
obviously gcc prior to 4.7 had bugs and failed to find all such errors.

lib/libcompiz_core.so (LP: #919948)
  
We do however want to install the headers. Unfortunately CMake gives you
no way to say install(TARGETS something ARCHIVE DESTINATION null) and it
always wants to install the archive. So we work around this problem with
CMake by removing the archives' INSTALL rules and simply installing the
required headers as part of compiz_core: src/CMakeLists.txt.

Merged: lp:~smspillaz/compiz-core/fix-timer-warnings-893998
without any of its prereqs. 

uninitialized variable use on some systems.

methods now return the real-time minimum and maximum left value, so wait
for the guarunteed timeout time and then check if they are zero