This should be controlled by the build system.

The logic does not work with imported targets and CMake prefers to link
with absolute paths anyways.

For building shared and static libraries, using two different build
trees is best rather than trying to hack up a single build to do
multiple things.

There's no reason to special case this version of MSVC.

Set it only at the top-level and remove checks for policies which are
set to `NEW` and guaranteed to be so by the minimum version.

Revert the noboost work as it doesn't compile with visstudio 2013

See merge request xdmf/xdmf!48

the compiler warning seems to indicate something that might
bite us, the triangle inheritance pattern with several methods
named insert could be a problem but a proper fix isn't immediately
obvious without some substantial reworking

This brings us back to commit 605db515

Toward warning free windows compilation

See merge request !47

the compiler warning seems to indicate something that might
bite us, the triangle inheritance pattern with several methods
named insert could be a problem but a proper fix isn't immediately
obvious without some substantial reworking

misc style issues

See merge request !46

restore the whitespace trim, xdmf files in VTK's suite fail without

See merge request !45

Noboost2

See merge request !44

I'm unsure about the XdmfAttribute copy constructor merge conflict
resolution. For now I've left master's in but commented out as it
leads to a compile failure.

Fix to_string

See merge request !43

Add newline

See merge request !42