Remove Loki as a dependency, require C++11 support in library

This MR removes Loki as a dependency of Nektar++ and enables the requirement of C++11 for compiling Nektar++. In particular the following changes are made:

• Loki::Singleton is removed for our factory holders, instead using a simple static variable inside a static function, which is guaranteed to be thread-safe in C++11.
• CMake configuration is set up to require C++11
• Boost preprocessor headers have been removed in deference to variadic templates in the factory, manager and memory manager.
• .clang-format updated to C++11

This is an alternative to the approach taken in !764 (closed).

mentioned in merge request !764 (closed)

@dmoxey just a few points on this. There is a small issue when memory pools are off. One the declarations in memory manager hasnt been set up. It also appears that when you use mpi with openmpi such as on the compute nodes there are a lot of compiler warnings about one of the headers not being okay with c++11.

added 169 commits

• 8e7645c9...e598a95c - 168 commits from branch master
• 1cfefa24 - Merge branch 'master' into feature/remove-loki

Compare with previous version

added 4 commits

• 4414bff3 - Add CMake options for versions less than 3.1, and update .clang-format to C++11 standard
• 17f96824 - Update to ignore check on Windows
• 158e1f18 - Merge remote-tracking branch 'upstream/feature/libutils-c++11' into feature/remove-loki
• 9806c49d - Fix some compiler warnings and error if memory pools disabled

Compare with previous version

unmarked as a Work In Progress

changed title from [WIP] Remove Loki as a dependency to Remove Loki as a dependency, require C++11 support in library

changed the description

assigned to @ccantwel

Okay, I have fixed the issue with memory pools and applied the changes in the discussion in !766 (closed). I don't think we need both merge requests, so I have closed that one and gone with this one instead since it also incorporates the Loki removal change.

I will run through buildbot again now. I anticipate that the VTK issue on Ubuntu 14.04 will still remain. However other than this, it is good to go from my perspective.

added 1 commit

• 1e3811e9 - Fix for VTK 6 compiler error

Compare with previous version

added 1 commit

• 92c8d6b7 - Adjust fix since vtkVersionMacros isn't present in VTK5

Compare with previous version

Okay, I have patched the VTK issue and this seems to now be compiling/passing. It seems to only happen for VTK 6.0.0 exactly (VTK 5 is fine and VTK 6.0.1 had a patch to fix the issue). It does however require including a VtkUtil.hpp header file before you use any VTK headers.

I have also fixed the Windows buildbot and am now testing on this, so once that is done this is good to merge from my point of view.

added 1 commit

• 9c2c49b3 - Fix issue with std::max

Compare with previous version

added 1 commit

• 1c44592a - Avoid issue with min/max macro

Compare with previous version

added 1 commit

• 99e251fc - Fix preprocessing bug

Compare with previous version

assigned to @mt4313

mentioned in commit 7702eef3

merged