Fixes Issue 90; Also fixes some issues breaking the build on Windows
Merge branch 'cmakelists_headers' into unstable.  Reviewed by Patrick Niedzielski.
Fixes Issue 84; Also fixes issue where vector.cpp was incorrectly added to headers source group
Forgot to change ``HUMMSTRUMM_'' cmake variable to ``HUMMSTRUMM_ENGINE_'' variable in the CPPUnit source code.
Some typos in HUMMSTRUMM_xxxx -> HUMMSTRUMM_ENGINE_xxxx transition, and some things that weren't changed.  A later commit will fix remaining ones that were found on Windows.
Whitespace fix, after deleting the destructor.
Tim saw a segfault in test_engine_date.  Could not reproduce or find an suitable candidates in the engine source code for segfaults, because we use stack-based member variables in all places where this would matter.  I think it's a problem with CPPUnit and the newest version of MSVC.  See issue 80.  We already have plans to move away from this.

All variables in the unit test were moved from the heap to the stack, so no chances for a segfault (hopefully).
Fixes Issue 87
Fixes Issue 87
Merge branch 'maths_inl' of https://code.google.com/r/realmz-hummstrumm-dev into unstable.

Needed to change window/windowvisualinfo.cpp and window/x11/windowsystem.cpp to include <cstring> due to compiler errors from GCC.  This shouldn't hurt anything, and it is better that the headers be included in the source files.
Merge branch 'sse_msvc11' of https://code.google.com/r/realmz-hummstrumm-dev into unstable
Make the header guards in geometry:: consistent with the rest of the engine.
Remove the ``using hummstrumm::engine::math::Vector*d;'' lines from geometry:: class headers.  Fixes issue 91.
Remove semicolons from after namespace closing braces in .inl files.
Added optimization.hpp.  This might cause merge conflicts with the cpp11_regex branch in my repo when we merge it in.
Stylistic consistency within VariableLogging.cmake.
Change the VariableLogging.cmake file to show prettier output.
This is better for detecting flags to use C++11.  Look for known flags -- some compilers use the same interface as GCC, so we can support them as well.
Check for regex library.  We prefer to use the standard C++11 <regex> library, but if the user wants to use Boost::regex, we use that.  If the standard C++11 <regex> does not work, we fall back to Boost::regex (libstdc++'s <regex> isn't implemented, so otherwise, we'd exclude GCC and most users of Clang from compiling the engine).

It was a conscious decision not to use tr1::regex, et al.  Compliers that only have TR1 don't support C++11 very well, probably, and compilers that have both TR1 and C++11 should be using C++11, which is the actual standard.
Prepare the build system to build source code that possibly uses Boost::regex.