Tweak "python_common.cmake" script to fix the error reported
below. Since "ctest_empty_binary_directory" returns:
 (1) true if the directory does not exist
 (3) false if the directory exists and does NOT contain a CMakeCache.txt
this commit moves the directory creation after the "ctest_empty_binary_directory"
call.

//------------
Clearing build tree...
CMake Error at scratch/python_common.cmake:306 (ctest_empty_binary_directory):
ctest_empty_binary_directory problem removing the binary directory:
C:\projects\python-cmake-buildsystem/../python-cmake-buildsystem/build
Call Stack (most recent call first):
scratch/appveyor_dashboard.cmake:31 (include)
//------------

…riable

If not set, it default to 8.

In both case build name will be prepended with "2.7.<PY_VERSION_PATCH>-".

The pull request number is added as documented for Travis at
http://docs.travis-ci.com/user/environment-variables/#Default-Environment-Variables

The pull request title and number is added as documented for Appveyor at
http://www.appveyor.com/docs/environment-variables

…est-in-build-name

Indicate pull request source in CDash Build Name.

…ython-cmake-buildsystem#83

If the last commit topic includes the special comments of the form
"[cmake <ARGUMENT>]" without trailing spaces, the project will be
configured using all extracted arguments.

For example, using these comments:

[cmake -DFOO:STRING=Hello]
[cmake -DBAR:STRING=World]
[cmake -DANSWER=42 -DGOOD:STRING=Day]

The project will be built with -DFOO:STRING=Hello -DBAR=World -DANSWER=42 -DGOOD:STRING=Day

This commit will ensure CI builds (which are of type Experimental) do not
reset the source checkout to origin/master

…e commit

This will allow CMake comment used in python-cmake-buildsystem#98 to effectively be considered
when configuring the project.

…e < 3.1.0

This commit improve the fix introduced in 77f3479 to also work for
older version of CMake.

As explained in [1], for legacy reason setting variable like
LD_LIBRARY_PATH with paths containing spaces will not work even if
the spaces are escaped. For that reason, prefer build path without
spaces.

[1] http://ubuntuforums.org/showthread.php?t=1142062

…commit msg

This commit fixes the following error:

//------------
ctest -V -C %configuration% -S "%APPVEYOR_BUILD_FOLDER%\\scripts\\appveyor_dashboard.cmake"
CMake Error at scripts/appveyor_dashboard.cmake:10 (if):
  if given arguments:

    "STREQUAL" ""

  Unknown arguments specified


Error in read script: C:/projects/python-cmake-buildsystem/scripts/appveyor_dashboard.cmake
Command exited with code -1
//------------

…iables

…r and travis.

Default remains "Visual Studio 9 2008"

See http://www.appveyor.com/docs/environment-variables

…ontainer

This is not required since the dashboard branch is checked out
within circle.yml

…e-buildsystem#127

…#150

…make-buildsystem#164

…HON_VERSION

This commit fixes regression introduced in 99cb03a (Update python version
configuration based on python-cmake-buildsystem#150)

…cache.txt"

Follow-up of 6391889 ("cmake: Remove support for building CPython 2.7", 2025-04-28)
in which `appveyor.yml` was removed.

Adapted from:
* https://gitlab.kitware.com/cmake/dashboard-scripts/-/blob/79d271a96607c9edb99dd875a50484bcc5caa4f3/cmake_common.cmake
* https://github.com/Kitware/TeleSculptor/blob/32378009fe1499811812f1f1be23d30d43369a0a/CMake/dashboard-scripts/TeleSculptor_common.cmake#L60

Adapted from cmake/dashboard-scripts@aa51648 ("cmake_common: Enable launchers and make program for Ninja generator", 2014-05-20)

See https://gitlab.kitware.com/cmake/dashboard-scripts/-/commit/aa51648

Adapted from cmake/dashboard-scripts@353a27e ("cmake_common: Restore HOME after each run", 2022-08-05)
See https://gitlab.kitware.com/cmake/dashboard-scripts/-/commit/353a27e

Since minimum required CMake version was updated in fbc3a81 ("Update minimum required CMake version from 2.8.6 to 3.13.5", 2022-01-03),
this commit partially reverts 7e11eb9 ("Ensure Experimental build do not reset the local repo when using CMake < 3.1.0", 2015-09-03)

Adapted from cmake/dashboard-scripts@d5bd988 ("cmake_common: Update before initializing build tree", 2025-02-16)
See https://gitlab.kitware.com/cmake/dashboard-scripts/-/commit/d5bd988

…rd_no_test"

…ently

CDash misinterprets colons (:) in the `CTEST_SITE` string, causing the
"Update" and "Configure/Build/Test" steps to appear as separate rows
in the dashboard.

This patch replaces colons with underscores as a workaround to ensure
all submission parts are grouped correctly.

Related issue: Kitware/CDash#2905

Make the build directory after using ctest_empty_binary_directory
because the command reports an error if asked to delete a directory
that exists but does not contain `CMakeCache.txt`.

Adapted from cmake/dashboard-scripts@cb56d71 ("cmake_common: Fix use of ctest_empty_binary_directory", 2016-01-21)
See https://gitlab.kitware.com/cmake/dashboard-scripts/-/commit/cb56d71

Since the submission is done by part, this hook is irrelevant.

Adapted from cmake/dashboard-scripts@0272ca4 ("Store GIT_EXECUTABLE in CMake cache", 2010-06-15)
See https://gitlab.kitware.com/cmake/dashboard-scripts/-/commit/0272ca4

Translated to CMake from a patch on the Yocto project:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/python/python3/0002-Don-t-do-runtime-test-to-get-float-byte-order.patch?h=zeus
It avoids the execution of a program on the target device,
and produces a clearer endianness result.