| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The machine name we happen to use for the build is less informative than
its platform.
|
| | |
|
| |
|
|
|
| |
Pass needed bootstrap arguments directly instead of constructing them
from various conditions.
|
| |
|
|
|
|
|
|
| |
Disable the CMake_INSTALL_DEPENDENCIES option by default and turn it on
explicitly in our packaging scripts. This simplifies packaging in
distributions that provide the dependencies for us without having to
install them. We only need 3rd-party runtime dependencies to be
installed for packaging with redistributable binaries.
|
| |
|
|
|
| |
Configure the build on dash2win64 cygwin to run Sphinx and generate our
documentation.
|
| |
|
|
|
| |
Tell Git not to perform newline conversion by configuring
'core.autocrlf' to 'false'. Cygwin wants newlines like UNIX.
|
| |
|
|
|
|
|
|
| |
Only temporarily until we can setup a new cygwin build machine
for making releases. It's specific to the script that runs on
dash2win64 anyhow. When we add a new script to run it on a
different machine, and stop building the cygwin releases on
dash2win64, this change will naturally no longer apply.
|
| |
|
|
|
|
|
|
| |
The parent commit only added DART_TESTING_TIMEOUT to the cache.
Also add CTEST_TEST_TIMEOUT because the logic in
CMake/Tests/CMakeLists.txt uses that variable in its "long test
timeout" computation. Now the cygwin build really does have 7200
seconds before it calls timeout death on a test.
|
| |
|
|
|
|
| |
Previously, the ExternalProject test was timing out at the
default timeout value of 1500 seconds. Give it time, little
one, it will finish if you learn patience.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
