Revert the removal of boost changes

See merge request !37

it breaks windows and some of Xdmf's own tests

Revert "removed a PARENT_SCOPE that was unessesary, added some missing includes, fixed cxx11 typecasting"
This reverts commit 583c14de.

Revert "changes to fix windows build"
This reverts commit 397e235f.

Revert "Updates to reduce library files needed for linking"
This reverts commit ff194c1f.

Revert "adjusting code away from regex to handle Apple systems"
This reverts commit 05124fbf.

Revert "Fixed typo"
This reverts commit bba7984f.

Revert "std::string compatibility"
This reverts commit 24ea357e.

Revert "fixes to handle boost not being available"
This reverts commit b21b735a.

Revert "removed print statement"
This reverts commit 44d1df0e.

Revert "Fixed typo in PushBack change"
This reverts commit 61df7337.

Revert "fixes for Windows Compilation"
This reverts commit 92313779.

Revert "Changes to remove boost dependency and add Cxx11 as an alternate"
This reverts commit f5300338.

make it easy to choose boost instead of the new cxx11 sptrs

See merge request !35

On some platforms, like windows, you don't have to do anything
special to get c++11. This change makes it easy to use the
older boost based implementation on them.

Windows and install fixes

See merge request !34

Don't explicitly link to Python on OS X

See merge request !24

Fix for invalid XPointer in XDMF output if `XdmfDomain::accept()` is called more than once...

See merge request !26

Added comment to explain how XdmfTopologyType is read

See merge request !22

While a development install needs to put them in place so that
users can compile new code against xdmf, a runtime install has
no need for them.

With these the built libraries get put into strange places and
ParaView won't start because it can't find them without PATH
assistance. Let's let cmake do its thing instead.

XdmfLibraries and XdmfDSMLinkLibraries are undefined and this we
get undefined symbol errors.

I have yet to find the case where this was necessary for Andrew.
With the __int64 block removed, it compiles on vs2013 and vs2016
64 bit, with it comp fails because of redefinition.

A simple test case below shows that the behavior is the same on
32 bit. If we find out where the test case compiles, we can add
it back in with appropriate guards to make it compile widely.

template <typename T> void setArrayType()
{ std::cout << "other" << std::endl; }
template <> void setArrayType<long long>()
{ std::cout << "long long" << std::endl; }
template <> void setArrayType<__int64>()
{ std::cout << "__int64" << std::endl; }
int main(int argc, char *argv[])
{ return 0; }

correct no boost reading of XML data

See merge request !33

Just fixed some typos in the CXX side or the ifdef to match the
boost side. With these (and a slight increase in temporal tolerance)
the VTK xdmf tests pass.

And finally no BOOST! Kudos to Andrew for doing the hard work.

removed a PARENT_SCOPE that was unessesary, added some missing includes, fixed cxx11 typecasting

See merge request !32

cleaning up optional includes

See merge request !31

proper SOVERSION and VERSION setting on libraries

See merge request !28

Cxx11 updates

See merge request !30

better installation directories

See merge request !29

Uses CMake's GNUInstallDirs.

BUG: Fix BUILD_SHARED_LIBS overwritting identical name flags.

The BUILD_SHARED_LIBS option for Xdmf was overwritting any flags having
the same name being used by other toolkits using Xdmf. Since
BUILD_SHARED_LIBS is a built-in CMake variable, this patch set
prevents xdmf overwritting the BUILD_SHARED_LIBS flag value by simply
removing the option.

See merge request !25

The BUILD_SHARED_LIBS option for Xdmf was overwritting any flags having
the same name being used by other toolkits using Xdmf. Since
BUILD_SHARED_LIBS is a built-in CMake variable, this patch set
prevents xdmf overwritting the BUILD_SHARED_LIBS flag value by simply
removing the option.

See http://blog.tim-smith.us/2015/09/python-extension-modules-os-x/.