kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Utilities/Release/create-cmake-release.cmake

79 lines
2.7 KiB
CMake
Raw Normal View History

ENH: change to use CMAKE_CREATE_VERSION from CMAKE_VERSION as CMAKE_VERSION is auto-defined now
2009-01-27 18:34:14 +03:00
if(NOT DEFINED CMAKE_CREATE_VERSION)
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
set(CMAKE_CREATE_VERSION "release")
message("Using default value of 'release' for CMAKE_CREATE_VERSION")
endif()
ENH: add a xterm script create script
2006-05-09 21:49:18 +04:00
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
file(MAKE_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/logs)
set(RELEASE_SCRIPTS_BATCH_1
Utilities/Release: Switch to .msi builder for Windows binary Use a new build machine to produce the Windows binary using the CPack WiX generator to produce a `.msi` installer.
2015-12-10 22:59:09 +03:00
dash3win7_release.cmake # Windows
Utilities/Release: Switch to OS X 10.7 and Qt 5.5 for Mac binary Use a new build machine to produce the OS X binary targeting OS X 10.7 and using Qt 5.5.
2016-02-18 23:32:38 +03:00
bigmac_release.cmake # OS X x86_64
ENH: add test that builds a nightly windows cmake binary
2007-09-10 18:49:05 +04:00
magrathea_release.cmake # Linux
Utilities/Release: Add build of binary for Linux x86_64
2014-12-02 22:00:39 +03:00
linux64_release.cmake # Linux x86_64
ENH: add a xterm script create script
2006-05-09 21:49:18 +04:00
)
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
set(RELEASE_SCRIPTS_BATCH_2
dash2win64_cygwin.cmake # Cygwin
)
ENH: add a xterm script create script
2006-05-09 21:49:18 +04:00
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
function(write_batch_shell_script filename)
set(scripts ${ARGN})
set(i 0)
file(WRITE ${filename} "#!/bin/bash")
foreach(f ${scripts})
math(EXPR x "420*(${i}/4)")
math(EXPR y "160*(${i}%4)")
file(APPEND ${filename}
ENH: add a xterm script create script
2006-05-09 21:49:18 +04:00
"
Utilities/Release: Pass pre-built docs tarball Avoid requiring all build machines for the upstream packaging process to have Python and Sphinx installed. Instead create a way to build the documentation once on the host machine and copy it to each build machine as a tarball with content to include in the installation tree for packaging.
2014-01-28 19:41:56 +04:00
\"${CMAKE_COMMAND}\" -DCMAKE_CREATE_VERSION=${CMAKE_CREATE_VERSION} -DCMAKE_DOC_TARBALL=\"${CMAKE_DOC_TARBALL}\" -P \"${CMAKE_ROOT}/Utilities/Release/${f}\" < /dev/null >& \"${CMAKE_CURRENT_SOURCE_DIR}/logs/${f}-${CMAKE_CREATE_VERSION}.log\" &
Utilities/Release: Fix for spaces in host path Quote paths in the generated shell scripts so they work with spaces.
2014-01-28 19:40:52 +04:00
xterm -geometry 64x6+${x}+${y} -sb -sl 2000 -T ${f}-${CMAKE_CREATE_VERSION}.log -e tail -f \"${CMAKE_CURRENT_SOURCE_DIR}/logs/${f}-${CMAKE_CREATE_VERSION}.log\" &
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
")
math(EXPR i "${i}+1")
Remove CMake-language block-end command arguments Ancient versions of CMake required else(), endif(), and similar block termination commands to have arguments matching the command starting the block. This is no longer the preferred style. Run the following shell code: for c in else endif endforeach endfunction endmacro endwhile; do echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | egrep -z -v 'Tests/CMakeTests/While-Endwhile-' | xargs -0 sed -i -f convert.sed && rm convert.sed
2012-08-13 21:50:14 +04:00
endforeach()
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
execute_process(COMMAND chmod a+x ${filename})
endfunction()
Utilities/Release: Pass pre-built docs tarball Avoid requiring all build machines for the upstream packaging process to have Python and Sphinx installed. Instead create a way to build the documentation once on the host machine and copy it to each build machine as a tarball with content to include in the installation tree for packaging.
2014-01-28 19:41:56 +04:00
function(write_docs_shell_script filename)
find_program(SPHINX_EXECUTABLE
NAMES sphinx-build sphinx-build.py
DOC "Sphinx Documentation Builder (sphinx-doc.org)"
)
if(NOT SPHINX_EXECUTABLE)
message(FATAL_ERROR "SPHINX_EXECUTABLE (sphinx-build) is not found!")
endif()
set(name cmake-${CMAKE_CREATE_VERSION}-docs)
file(WRITE "${filename}" "#!/usr/bin/env bash
name=${name} &&
inst=\"\$PWD/\$name\"
(GIT_WORK_TREE=x git archive --prefix=\${name}-src/ ${CMAKE_CREATE_VERSION}) | tar x &&
rm -rf \${name}-build &&
mkdir \${name}-build &&
cd \${name}-build &&
\"${CMAKE_COMMAND}\" ../\${name}-src/Utilities/Sphinx \\
-DCMAKE_INSTALL_PREFIX=\"\$inst/\" \\
Utilities/Release: Install docs in unversioned directory (#15692) Our upstream-built release tarballs already contain many unversioned paths and so will never overlap with another version of CMake in the same installation prefix. Therefore we do not need a versioned name for the documentation directory. Configure our release binaries to place the documentation in an unversioned directory so that one can use the same path to refer to the documentation locally even after updating CMake. For example, on OS X one may see the documentation in `/Applications/CMake.app/Contents/doc/cmake/html/index.html`.
2015-09-02 21:15:59 +03:00
-DCMAKE_DOC_DIR=doc/cmake \\
Utilities/Release: Pass pre-built docs tarball Avoid requiring all build machines for the upstream packaging process to have Python and Sphinx installed. Instead create a way to build the documentation once on the host machine and copy it to each build machine as a tarball with content to include in the installation tree for packaging.
2014-01-28 19:41:56 +04:00
-DSPHINX_EXECUTABLE=\"${SPHINX_EXECUTABLE}\" \\
-DSPHINX_HTML=ON -DSPHINX_MAN=ON &&
make install &&
cd .. &&
tar czf \${name}.tar.gz \${name} ||
echo 'Failed to create \${name}.tar.gz'
")
execute_process(COMMAND chmod a+x ${filename})
set(CMAKE_DOC_TARBALL "${name}.tar.gz" PARENT_SCOPE)
endfunction()
write_docs_shell_script("create-${CMAKE_CREATE_VERSION}-docs.sh")
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
write_batch_shell_script("create-${CMAKE_CREATE_VERSION}-batch1.sh" ${RELEASE_SCRIPTS_BATCH_1})
Utilities/Release: Pass pre-built docs tarball Avoid requiring all build machines for the upstream packaging process to have Python and Sphinx installed. Instead create a way to build the documentation once on the host machine and copy it to each build machine as a tarball with content to include in the installation tree for packaging.
2014-01-28 19:41:56 +04:00
unset(CMAKE_DOC_TARBALL) # No pre-built docs in second batch.
CMake: eliminate use of cvs in the Release scripts Set GIT_COMMAND to "git" -- each machine involved in building the CMake release binaries has the right "git" in the PATH. Separate the release scripts into two batches so we can build multiple releases on the same machine, in serial, if necessary. We currnetly do this with the Windows and Cygwin release binaries on dash2win64. Sort the files to be uploaded, so that sorting them by modification time (file copy / upload time) is equivalent to sorting them alphabetically.
2011-06-02 06:32:42 +04:00
write_batch_shell_script("create-${CMAKE_CREATE_VERSION}-batch2.sh" ${RELEASE_SCRIPTS_BATCH_2})
Utilities/Release: Pass pre-built docs tarball Avoid requiring all build machines for the upstream packaging process to have Python and Sphinx installed. Instead create a way to build the documentation once on the host machine and copy it to each build machine as a tarball with content to include in the installation tree for packaging.
2014-01-28 19:41:56 +04:00
message("Run one at a time:
./create-${CMAKE_CREATE_VERSION}-docs.sh &&
./create-${CMAKE_CREATE_VERSION}-batch1.sh &&
./create-${CMAKE_CREATE_VERSION}-batch2.sh &&
echo done
")