the SCM information that gets appended at the end of the buildname string.
The buildname string is the string that will identify your test run when
published on the foam-extend CDash service.
When using git, this SCM information is picked up automatically from the CTest
script: -git-branch=the_git_branch_name-git-rev=the_git_revision_number.
But when using a non-git SCM (mercurial, etc), when the foam-extend source
code you are testing is not under a valid git repository, or simply when a user
needs to add more details to the standard SCM information (branch name and
revision number), then setting the environment variable CDASH_SCM_INFO to the
proper information will allow you to override the suffix we add at the end of
the buildname.
Please note that in order to keep the CMake script simple, for non-git
repositories, the fallback solution to try grabbing the information through
Mercurial has been removed. Please use the CDASH_SCM_INFO environment
varible instead.
I am proposing an improved ThirdParty packages selection mechanism based on a set of package-specific, pre-defined environment variables.
Using those environment variables, one can control the selection of the full list of ThirdParty packages he/she want to compile/use by simply editing the etc/prefs.sh or etc/prefs.csh file.
Using this new approach, you will no longer have to edit the ThirdParty/AllMake.stageXXX files or the etc/settings.[sh,csh] to suit your needs; every supported package is selectable from a single environment variable specified in your prefs.[sh,csh] file, or in one of your script file.
Another benefit from this improvement will also come from supplying a set of predefined prefs.[sh,csh]-EXAMPLE files for both generic or specialized configurations and/or for specific Operating Systems. For example:
prefs.sh-EXAMPLE-Centos-7
prefs.sh-EXAMPLE-Ubuntu-14.02
prefs.sh-EXAMPLE-MacOSX_Yosemite_without_MacPorts
prefs.sh-EXAMPLE-RaspberryPi2
I also took the liberty of bumping many ThirdParty packages to the latest version available.
