Source tarball does not build with CMake

[Martyn Gigg]

The source tarball created by the RPM scripts will not build with CMake as it is not a subversion working copy.

In this case we should write out the version necessary header files and include them in the source and then update the CMake scripts so that they can run on a non-svn copy.

[Russell Taylor]

(In [10315]) Switch SVN_WORKING_COPY default to OFF. Buildservers creating install kits will need to be sure to turn it on or the revision number will show zero. Re #2565.

[Russell Taylor]

The changed default on the flag above will allow builds out of the box on the source tarball. However, it will create the version headers with 0 for the revision number, which may not be what we want in this particular situation.

[Russell Taylor]

This problem can be solved by using a source tarball created by cmake/cpack. This will contain the already-generated MantidVersion.h. We just need to modify the CMakeLists to not overwrite it with a zero in this circumstance (i.e. test for not a working copy, but MantidVersion.h already exists).

[Nick Draper]

Bulk move of tickets at the end of iteration 28

[Russell Taylor]

(In [11120]) Only generate MantidVersion if SVN_WORKING_COPY is set or it doesn't already exist. This will mean the right version number is there when building off the source tarball. Fixes #2565.

[Stuart Campbell]

I get a source tarball, but it contains files with strange paths like:

mantid-1.28.11131-Source/usr/local/Framework/UserAlgorithms/PropertyAlgorithm.cpp

[Stuart Campbell]

follow up ticket #2881

[Stuart Campbell]

This ticket has been transferred to github issue ​3412