summaryrefslogtreecommitdiffstats
path: root/Utilities/Release/win
Commit message (Collapse)AuthorAgeFilesLines
* Utilities/Release: Use explicit digest for Win7-compatible signatureBrad King2022-11-301-1/+1
| | | | Otherwise `signtool` warns.
* Utilities/Release: Simplify script to build Qt 6.3.0 Windows binariesCristian Adam2022-06-172-135/+121
| | | | | | | | | Revise and simplify the script from commit d0c9225a7e (Utilities/Release: Add script to build Qt 6.3.0 Windows binaries, 2022-06-10, v3.24.0-rc1~4^2~5). For `cmake-gui` we only need QtBase. Also, convert to a `.cmake` script. Issue: #21902
* Utilities/Release: Add script to build Qt 6.3.0 Windows binariesBrad King2022-06-131-0/+135
| | | | These may be used to build CMake binaries for Windows.
* Utilities/Release: Drop docker specs for Windows binariesBrad King2022-06-0114-445/+0
| | | | | | | | | Since commit 4c7c66dcf5 (gitlab-ci: Add jobs to make Windows x86_64 and i386 packages, 2022-05-19), we use CI jobs to produce Windows binaries. Revert commit ff929badb3 (Utilities/Release: Add docker specs to build and test Windows binaries, 2020-05-05, v3.18.0-rc1~203^2~1). The filesystem inside Windows containers is too slow to support parallel builds efficiently.
* Utilities/Release: Add script to sign and package Windows binariesBrad King2022-05-191-0/+29
| | | | | | Windows binaries for official releases on `cmake.org` are signed manually by a maintainer with a suitable signing certificate. Add a script to sign the binaries, run CPack, and sign the installer.
* Utilities/Release: Add script to build Qt 5.12.1 Windows binariesBrad King2022-05-192-0/+144
| | | | | | | | These may be used to build CMake binaries for Windows `x86_64` and `i386`. Qt 5.12.1 supports Windows 7. Port the logic from `Utilities/Release/win/x86/deps/Dockerfile` and its helper scripts.
* CMake: Use FindPython instead of FindPythonInterp to build CMake itselfKyle Edwards2022-04-212-2/+2
| | | | Fixes: #23444
* Merge topic 'doc-qhelpgenerator'Brad King2022-04-082-2/+2
|\ | | | | | | | | | | | | | | bf69fa32c4 Utilities/Sphinx: Update qthelp generation to qhelpgenerator 37904abb58 Help: Add "Updates" section header in 3.22 release notes Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7150
| * Utilities/Sphinx: Update qthelp generation to qhelpgeneratorBrad King2022-04-072-2/+2
| | | | | | | | `qcollectiongenerator` is deprecated in favor of `qhelpgenerator`.
* | Merge topic 'rel-win-docker'Brad King2022-03-211-1/+3
|\ \ | |/ | | | | | | | | | | a6aa88e51f Utilities/Release: Add "source" stage to Windows docker spec Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7087
| * Utilities/Release: Add "source" stage to Windows docker specBrad King2022-03-181-1/+3
| | | | | | | | | | | | | | | | Revise the spec added by commit ff929badb3 (Utilities/Release: Add docker specs to build and test Windows binaries, 2020-05-05, v3.18.0-rc1~203^2~1) to add a `source` stage that stops just after copying the source tree into the image. This provides more granular control to driving scripts.
* | Tests: Run MFC test only when explicitly enabledBrad King2022-02-034-8/+0
|/ | | | | | | | Previously we used a complicated heuristic to decide whether or not to run the MFC test, but it sometimes decided incorrectly to run the test. Since that was first written, we have developed a convention for other tests to enable them via undocumented cache entries that are added only on machines known to meet the tests' requirements. Do that for MFC.
* Utilities/Release: Rename Windows packages to 'windows-$arch'Brad King2021-01-262-2/+2
|
* Utilities/Release: Add docker specs to build and test Windows binariesBrad King2020-05-0514-0/+451
These will allow anyone to produce portable binaries like those published on `cmake.org`. Follow the pattern from commit facc240a45 (Utilities/Release: Add docker specs to build and test Linux binaries, 2019-08-23, v3.16.0-rc1~184^2~2). Parameterize the architecture to support both `x86_64` and `i386`.