mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-27 06:59:43 +08:00
Code Issues Packages Projects Releases Wiki Activity
abd8f2b78b
curl/appveyor.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

392 lines
14 KiB
YAML
Raw Normal View History

copyright: fix out-of-date copyright ranges and missing headers Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
2020-03-23 21:44:29 +08:00
#***************************************************************************
# _ _ ____ _
# Project ___| | | | _ \| |
# / __| | | | |_) | |
# | (__| |_| | _ <| |___
# \___|\___/|_| \_\_____|
#
copyright: update all copyright lines and remove year ranges - they are mostly pointless in all major jurisdictions - many big corporations and projects already don't use them - saves us from pointless churn - git keeps history for us - the year range is kept in COPYING checksrc is updated to allow non-year using copyright statements Closes #10205
2023-01-02 20:51:48 +08:00
# Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
copyright: fix out-of-date copyright ranges and missing headers Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
2020-03-23 21:44:29 +08:00
#
# This software is licensed as described in the file COPYING, which
# you should have received as part of this distribution. The terms
curl.se: new home Closes #6172
2020-11-04 21:02:01 +08:00
# are also available at https://curl.se/docs/copyright.html.
copyright: fix out-of-date copyright ranges and missing headers Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
2020-03-23 21:44:29 +08:00
#
# You may opt to use, copy, modify, merge, publish, distribute and/or sell
# copies of the Software, and permit persons to whom the Software is
# furnished to do so, under the terms of the COPYING file.
#
# This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
# KIND, either express or implied.
#
# SPDX-License-Identifier: curl
copyright: make repository REUSE compliant Add licensing and copyright information for all files in this repository. This either happens in the file itself as a comment header or in the file `.reuse/dep5`. This commit also adds a Github workflow to check pull requests and adapts copyright.pl to the changes. Closes #8869
2022-05-17 17:16:50 +08:00
#
copyright: fix out-of-date copyright ranges and missing headers Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
2020-03-23 21:44:29 +08:00
###########################################################################
CI: don't run CI jobs if only another CI was changed Also skip builds on non-Windows platforms when only Windows build files have changed. This should reduce the number of useless builds and the associated waiting time and chance of spurious failures, freeing resources for new PRs. Closes #10742
2023-03-11 08:58:21 +08:00
# https://ci.appveyor.com/project/curlorg/curl/history
# Appveyor configuration
# https://www.appveyor.com/docs/appveyor-yml/
copyright: fix out-of-date copyright ranges and missing headers Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
2020-03-23 21:44:29 +08:00
Appveyor: Updates for options - CURL_STATICLIB/BUILD_TESTING Closes #892
2016-06-22 20:42:10 +08:00
version: 7.50.0.{build}
CI: Added AppVeyor-CI for curl Closes #439
2015-09-17 21:34:47 +08:00
environment:
cmake: add support for "unity" builds Aka "jumbo" or "amalgamation" builds. It means to compile all sources per target as a single C source. This is experimental. You can enable it by passing `-DCMAKE_UNITY_BUILD=ON` to cmake. It requires CMake 3.16 or newer. It makes builds (much) faster, allows for better optimizations and tends to promote less ambiguous code. Also add a new AppVeyor CI job and convert an existing one to use "unity" mode (one MSVC, one MinGW), and enable it for one macOS CI job. Fix related issues: - add missing include guard to `easy_lock.h`. - rename static variables and functions (and a macro) with names reused across sources, or shadowed by local variables. - add an `#undef` after use. - add a missing `#undef` before use. - move internal definitions from `ftp.h` to `ftp.c`. - `curl_memory.h` fixes to make it work when included repeatedly. - stop building/linking curlx bits twice for a static-mode curl tool. These caused doubly defined symbols in unity builds. - silence missing extern declarations compiler warning for ` _CRT_glob`. - fix extern declarations for `tool_freq` and `tool_isVistaOrGreater`. - fix colliding static symbols in debug mode: `debugtime()` and `statename`. - rename `ssl_backend_data` structure to unique names for each TLS-backend, along with the `ssl_connect_data` struct member referencing them. This required adding casts for each access. - add workaround for missing `[P]UNICODE_STRING` types in certain Windows builds when compiling `lib/ldap.c`. To support "unity" builds, we had to enable `SCHANNEL_USE_BLACKLISTS` for Schannel (a Windows `schannel.h` option) _globally_. This caused an indirect inclusion of Windows `schannel.h` from `ldap.c` via `winldap.h` to have it enabled as well. This requires `[P]UNICODE_STRING` types, which is apperantly not defined automatically (as seen with both MSVS and mingw-w64). This patch includes `<subauth.h>` to fix it. Ref: https://github.com/curl/curl/runs/13987772013 Ref: https://dev.azure.com/daniel0244/curl/_build/results?buildId=15827&view=logs&jobId=2c9f582d-e278-56b6-4354-f38a4d851906&j=2c9f582d-e278-56b6-4354-f38a4d851906&t=90509b00-34fa-5a81-35d7-5ed9569d331c - tweak unity builds to compile `lib/memdebug.c` separately in memory trace builds to avoid PP confusion. - force-disable unity for test programs. - do not compile and link libcurl sources to libtests _twice_ when libcurl is built in static mode. KNOWN ISSUES: - running tests with unity builds may fail in cases. - some build configurations/env may not compile in unity mode. E.g.: https://ci.appveyor.com/project/curlorg/curl/builds/47230972/job/51wfesgnfuauwl8q#L250 Ref: https://github.com/libssh2/libssh2/issues/1034 Ref: https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html Ref: https://en.wikipedia.org/wiki/Unity_build Closes #11095
2023-05-09 18:10:40 +08:00
UNITY: "OFF"
CI: Added AppVeyor-CI for curl Closes #439
2015-09-17 21:34:47 +08:00
matrix:
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
# generated CMake-based Visual Studio Release builds
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, VS2008, Release x86, Schannel"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
AppVeyor: explicitly select worker image Currently, we're using the default Visual Studio 2015 image for everything. Closes https://github.com/curl/curl/pull/3606
2019-02-24 05:33:32 +08:00
PRJ_GEN: "Visual Studio 9 2008"
AppVeyor: add remaining Visual Studio versions This adds Visual Studio 9 and 10 builds. There's no 64-bit VC9 compiler on AppVeyor, so use it as the Win32 build. Also, VC9 cannot be used for running the test suite. Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:02:34 +08:00
PRJ_CFG: Release
AppVeyor: add WinSSL builds Use the oldest and latest Windows SDKs for them. Also, remove all but one OpenSSL build. Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:09:24 +08:00
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
HTTP_ONLY: OFF
Appveyor: Updates for options - CURL_STATICLIB/BUILD_TESTING Closes #892
2016-06-22 20:42:10 +08:00
TESTING: OFF
CMake: Respect BUILD_SHARED_LIBS Use standard CMake variable BUILD_SHARED_LIBS instead of introducing custom option CURL_STATICLIB. Use '-DBUILD_SHARED_LIBS=%SHARED%' in appveyor.yml. Reviewed-by: Sergei Nikulov Closes #2755
2018-07-10 17:54:34 +08:00
SHARED: ON
AppVeyor: add MinGW-w64 build Add a MinGW-w64 build using CMake's MSYS Makefiles generator. Use the Visual Studio 2015 image as it has GCC 8, while the Visual Studio 2017 image only has GCC 7.2. Closes https://github.com/curl/curl/pull/3623
2018-10-11 04:22:06 +08:00
DISABLED_TESTS: ""
cmake: add support for "unity" builds Aka "jumbo" or "amalgamation" builds. It means to compile all sources per target as a single C source. This is experimental. You can enable it by passing `-DCMAKE_UNITY_BUILD=ON` to cmake. It requires CMake 3.16 or newer. It makes builds (much) faster, allows for better optimizations and tends to promote less ambiguous code. Also add a new AppVeyor CI job and convert an existing one to use "unity" mode (one MSVC, one MinGW), and enable it for one macOS CI job. Fix related issues: - add missing include guard to `easy_lock.h`. - rename static variables and functions (and a macro) with names reused across sources, or shadowed by local variables. - add an `#undef` after use. - add a missing `#undef` before use. - move internal definitions from `ftp.h` to `ftp.c`. - `curl_memory.h` fixes to make it work when included repeatedly. - stop building/linking curlx bits twice for a static-mode curl tool. These caused doubly defined symbols in unity builds. - silence missing extern declarations compiler warning for ` _CRT_glob`. - fix extern declarations for `tool_freq` and `tool_isVistaOrGreater`. - fix colliding static symbols in debug mode: `debugtime()` and `statename`. - rename `ssl_backend_data` structure to unique names for each TLS-backend, along with the `ssl_connect_data` struct member referencing them. This required adding casts for each access. - add workaround for missing `[P]UNICODE_STRING` types in certain Windows builds when compiling `lib/ldap.c`. To support "unity" builds, we had to enable `SCHANNEL_USE_BLACKLISTS` for Schannel (a Windows `schannel.h` option) _globally_. This caused an indirect inclusion of Windows `schannel.h` from `ldap.c` via `winldap.h` to have it enabled as well. This requires `[P]UNICODE_STRING` types, which is apperantly not defined automatically (as seen with both MSVS and mingw-w64). This patch includes `<subauth.h>` to fix it. Ref: https://github.com/curl/curl/runs/13987772013 Ref: https://dev.azure.com/daniel0244/curl/_build/results?buildId=15827&view=logs&jobId=2c9f582d-e278-56b6-4354-f38a4d851906&j=2c9f582d-e278-56b6-4354-f38a4d851906&t=90509b00-34fa-5a81-35d7-5ed9569d331c - tweak unity builds to compile `lib/memdebug.c` separately in memory trace builds to avoid PP confusion. - force-disable unity for test programs. - do not compile and link libcurl sources to libtests _twice_ when libcurl is built in static mode. KNOWN ISSUES: - running tests with unity builds may fail in cases. - some build configurations/env may not compile in unity mode. E.g.: https://ci.appveyor.com/project/curlorg/curl/builds/47230972/job/51wfesgnfuauwl8q#L250 Ref: https://github.com/libssh2/libssh2/issues/1034 Ref: https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html Ref: https://en.wikipedia.org/wiki/Unity_build Closes #11095
2023-05-09 18:10:40 +08:00
- job_name: "CMake, VS2022, Release x64, OpenSSL, WebSockets, Unity"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
appveyor: update images from VS 2019 to 2022 Closes https://github.com/curl/curl/pull/8265
2022-01-10 20:57:44 +08:00
PRJ_GEN: "Visual Studio 17 2022"
appveyor: upgrade VS2017 to VS2019 Closes #4383
2019-09-19 22:34:06 +08:00
TARGET: "-A x64"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
PRJ_CFG: Release
OPENSSL: ON
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: OFF
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
HTTP_ONLY: OFF
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
TESTING: OFF
SHARED: ON
DISABLED_TESTS: ""
appveyor: enable websockets
2022-09-09 21:11:15 +08:00
WEBSOCKETS: ON
cmake: add support for "unity" builds Aka "jumbo" or "amalgamation" builds. It means to compile all sources per target as a single C source. This is experimental. You can enable it by passing `-DCMAKE_UNITY_BUILD=ON` to cmake. It requires CMake 3.16 or newer. It makes builds (much) faster, allows for better optimizations and tends to promote less ambiguous code. Also add a new AppVeyor CI job and convert an existing one to use "unity" mode (one MSVC, one MinGW), and enable it for one macOS CI job. Fix related issues: - add missing include guard to `easy_lock.h`. - rename static variables and functions (and a macro) with names reused across sources, or shadowed by local variables. - add an `#undef` after use. - add a missing `#undef` before use. - move internal definitions from `ftp.h` to `ftp.c`. - `curl_memory.h` fixes to make it work when included repeatedly. - stop building/linking curlx bits twice for a static-mode curl tool. These caused doubly defined symbols in unity builds. - silence missing extern declarations compiler warning for ` _CRT_glob`. - fix extern declarations for `tool_freq` and `tool_isVistaOrGreater`. - fix colliding static symbols in debug mode: `debugtime()` and `statename`. - rename `ssl_backend_data` structure to unique names for each TLS-backend, along with the `ssl_connect_data` struct member referencing them. This required adding casts for each access. - add workaround for missing `[P]UNICODE_STRING` types in certain Windows builds when compiling `lib/ldap.c`. To support "unity" builds, we had to enable `SCHANNEL_USE_BLACKLISTS` for Schannel (a Windows `schannel.h` option) _globally_. This caused an indirect inclusion of Windows `schannel.h` from `ldap.c` via `winldap.h` to have it enabled as well. This requires `[P]UNICODE_STRING` types, which is apperantly not defined automatically (as seen with both MSVS and mingw-w64). This patch includes `<subauth.h>` to fix it. Ref: https://github.com/curl/curl/runs/13987772013 Ref: https://dev.azure.com/daniel0244/curl/_build/results?buildId=15827&view=logs&jobId=2c9f582d-e278-56b6-4354-f38a4d851906&j=2c9f582d-e278-56b6-4354-f38a4d851906&t=90509b00-34fa-5a81-35d7-5ed9569d331c - tweak unity builds to compile `lib/memdebug.c` separately in memory trace builds to avoid PP confusion. - force-disable unity for test programs. - do not compile and link libcurl sources to libtests _twice_ when libcurl is built in static mode. KNOWN ISSUES: - running tests with unity builds may fail in cases. - some build configurations/env may not compile in unity mode. E.g.: https://ci.appveyor.com/project/curlorg/curl/builds/47230972/job/51wfesgnfuauwl8q#L250 Ref: https://github.com/libssh2/libssh2/issues/1034 Ref: https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html Ref: https://en.wikipedia.org/wiki/Unity_build Closes #11095
2023-05-09 18:10:40 +08:00
UNITY: "ON"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, VS2022, Release arm64, Schannel, Static"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
appveyor: update images from VS 2019 to 2022 Closes https://github.com/curl/curl/pull/8265
2022-01-10 20:57:44 +08:00
PRJ_GEN: "Visual Studio 17 2022"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
TARGET: "-A ARM64"
AppVeyor: updated to handle OpenSSL/WinSSL builds Closes #621
2016-01-28 20:57:28 +08:00
PRJ_CFG: Release
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
HTTP_ONLY: OFF
Appveyor: Updates for options - CURL_STATICLIB/BUILD_TESTING Closes #892
2016-06-22 20:42:10 +08:00
TESTING: OFF
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
SHARED: OFF
AppVeyor: add MinGW-w64 build Add a MinGW-w64 build using CMake's MSYS Makefiles generator. Use the Visual Studio 2015 image as it has GCC 8, while the Visual Studio 2017 image only has GCC 7.2. Closes https://github.com/curl/curl/pull/3623
2018-10-11 04:22:06 +08:00
DISABLED_TESTS: ""
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
# generated CMake-based Visual Studio Debug builds
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, VS2010, Debug x64, no SSL, Static"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
AppVeyor: explicitly select worker image Currently, we're using the default Visual Studio 2015 image for everything. Closes https://github.com/curl/curl/pull/3606
2019-02-24 05:33:32 +08:00
PRJ_GEN: "Visual Studio 10 2010 Win64"
AppVeyor: use Debug builds to run tests This enables more tests. Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:14:23 +08:00
PRJ_CFG: Debug
Appveyor: Updates for options - CURL_STATICLIB/BUILD_TESTING Closes #892
2016-06-22 20:42:10 +08:00
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: OFF
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
HTTP_ONLY: OFF
Appveyor: Updates for options - CURL_STATICLIB/BUILD_TESTING Closes #892
2016-06-22 20:42:10 +08:00
TESTING: ON
CMake: Respect BUILD_SHARED_LIBS Use standard CMake variable BUILD_SHARED_LIBS instead of introducing custom option CURL_STATICLIB. Use '-DBUILD_SHARED_LIBS=%SHARED%' in appveyor.yml. Reviewed-by: Sergei Nikulov Closes #2755
2018-07-10 17:54:34 +08:00
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "!1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, VS2022, Debug x64, Schannel, Static, Unicode"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
BUILD_SYSTEM: CMake
appveyor: update images from VS 2019 to 2022 Closes https://github.com/curl/curl/pull/8265
2022-01-10 20:57:44 +08:00
PRJ_GEN: "Visual Studio 17 2022"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
TARGET: "-A x64"
PRJ_CFG: Debug
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: ON
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
HTTP_ONLY: OFF
TESTING: ON
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "~571 !1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, VS2022, Debug x64, no SSL, Static"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
appveyor: update images from VS 2019 to 2022 Closes https://github.com/curl/curl/pull/8265
2022-01-10 20:57:44 +08:00
PRJ_GEN: "Visual Studio 17 2022"
appveyor: upgrade VS2017 to VS2019 Closes #4383
2019-09-19 22:34:06 +08:00
TARGET: "-A x64"
AppVeyor: use Debug builds to run tests This enables more tests. Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:14:23 +08:00
PRJ_CFG: Debug
appveyor: add a win32 build
2017-10-28 05:40:04 +08:00
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: OFF
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
HTTP_ONLY: OFF
TESTING: ON
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "~571 !1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, VS2022, Debug x64, no SSL, Static, HTTP only"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
appveyor: update images from VS 2019 to 2022 Closes https://github.com/curl/curl/pull/8265
2022-01-10 20:57:44 +08:00
PRJ_GEN: "Visual Studio 17 2022"
appveyor: upgrade VS2017 to VS2019 Closes #4383
2019-09-19 22:34:06 +08:00
TARGET: "-A x64"
AppVeyor: use Debug builds to run tests This enables more tests. Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:14:23 +08:00
PRJ_CFG: Debug
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: OFF
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add HTTP_ONLY build Closes https://github.com/curl/curl/pull/3104
2018-10-05 19:12:13 +08:00
HTTP_ONLY: ON
appveyor: add a win32 build
2017-10-28 05:40:04 +08:00
TESTING: ON
CMake: Respect BUILD_SHARED_LIBS Use standard CMake variable BUILD_SHARED_LIBS instead of introducing custom option CURL_STATICLIB. Use '-DBUILD_SHARED_LIBS=%SHARED%' in appveyor.yml. Reviewed-by: Sergei Nikulov Closes #2755
2018-07-10 17:54:34 +08:00
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "!1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
appveyor: update comments to be clear about toolchain - CMake-based MSYS builds use mingw-w64 to cross-compile. - autotools-based builds are compiled using msys2-devel. The difference is that the later ones are not cross-compiled to Windows and instead require the msys2 runtime to be present. At the moment only the Azure Pipelines CI builds actually run autotools-based cross-compilation builds for Windows.
2020-05-10 00:04:38 +08:00
# generated CMake-based MSYS Makefiles builds (mingw cross-compiling)
CI: make Appveyor job names unique Two otherwise identical mingw-w64 jobs now have their differing compiler versions mentioned in their names.
2023-06-28 16:07:21 +08:00
- job_name: "CMake, mingw-w64, gcc 8, Debug x64, Schannel, Static, Unicode"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
AppVeyor: add MinGW-w64 build Add a MinGW-w64 build using CMake's MSYS Makefiles generator. Use the Visual Studio 2015 image as it has GCC 8, while the Visual Studio 2017 image only has GCC 7.2. Closes https://github.com/curl/curl/pull/3623
2018-10-11 04:22:06 +08:00
PRJ_GEN: "MSYS Makefiles"
PRJ_CFG: Debug
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: ON
AppVeyor: add MinGW-w64 build Add a MinGW-w64 build using CMake's MSYS Makefiles generator. Use the Visual Studio 2015 image as it has GCC 8, while the Visual Studio 2017 image only has GCC 7.2. Closes https://github.com/curl/curl/pull/3623
2018-10-11 04:22:06 +08:00
HTTP_ONLY: OFF
TESTING: ON
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "!1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin;C:\\msys64\\usr\\bin"
AppVeyor: add MinGW-w64 build Add a MinGW-w64 build using CMake's MSYS Makefiles generator. Use the Visual Studio 2015 image as it has GCC 8, while the Visual Studio 2017 image only has GCC 7.2. Closes https://github.com/curl/curl/pull/3623
2018-10-11 04:22:06 +08:00
MSYS2_ARG_CONV_EXCL: "/*"
appveyor: pass on -k to make
2019-07-31 23:17:52 +08:00
BUILD_OPT: -k
CI: make Appveyor job names unique Two otherwise identical mingw-w64 jobs now have their differing compiler versions mentioned in their names.
2023-06-28 16:07:21 +08:00
- job_name: "CMake, mingw-w64, gcc 7, Debug x64, Schannel, Static, Unicode"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
BUILD_SYSTEM: CMake
PRJ_GEN: "MSYS Makefiles"
PRJ_CFG: Debug
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: ON
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
HTTP_ONLY: OFF
TESTING: ON
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "!1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\mingw-w64\\x86_64-7.2.0-posix-seh-rt_v5-rev1\\mingw64\\bin;C:\\msys64\\usr\\bin"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
MSYS2_ARG_CONV_EXCL: "/*"
BUILD_OPT: -k
cmake: add support for "unity" builds Aka "jumbo" or "amalgamation" builds. It means to compile all sources per target as a single C source. This is experimental. You can enable it by passing `-DCMAKE_UNITY_BUILD=ON` to cmake. It requires CMake 3.16 or newer. It makes builds (much) faster, allows for better optimizations and tends to promote less ambiguous code. Also add a new AppVeyor CI job and convert an existing one to use "unity" mode (one MSVC, one MinGW), and enable it for one macOS CI job. Fix related issues: - add missing include guard to `easy_lock.h`. - rename static variables and functions (and a macro) with names reused across sources, or shadowed by local variables. - add an `#undef` after use. - add a missing `#undef` before use. - move internal definitions from `ftp.h` to `ftp.c`. - `curl_memory.h` fixes to make it work when included repeatedly. - stop building/linking curlx bits twice for a static-mode curl tool. These caused doubly defined symbols in unity builds. - silence missing extern declarations compiler warning for ` _CRT_glob`. - fix extern declarations for `tool_freq` and `tool_isVistaOrGreater`. - fix colliding static symbols in debug mode: `debugtime()` and `statename`. - rename `ssl_backend_data` structure to unique names for each TLS-backend, along with the `ssl_connect_data` struct member referencing them. This required adding casts for each access. - add workaround for missing `[P]UNICODE_STRING` types in certain Windows builds when compiling `lib/ldap.c`. To support "unity" builds, we had to enable `SCHANNEL_USE_BLACKLISTS` for Schannel (a Windows `schannel.h` option) _globally_. This caused an indirect inclusion of Windows `schannel.h` from `ldap.c` via `winldap.h` to have it enabled as well. This requires `[P]UNICODE_STRING` types, which is apperantly not defined automatically (as seen with both MSVS and mingw-w64). This patch includes `<subauth.h>` to fix it. Ref: https://github.com/curl/curl/runs/13987772013 Ref: https://dev.azure.com/daniel0244/curl/_build/results?buildId=15827&view=logs&jobId=2c9f582d-e278-56b6-4354-f38a4d851906&j=2c9f582d-e278-56b6-4354-f38a4d851906&t=90509b00-34fa-5a81-35d7-5ed9569d331c - tweak unity builds to compile `lib/memdebug.c` separately in memory trace builds to avoid PP confusion. - force-disable unity for test programs. - do not compile and link libcurl sources to libtests _twice_ when libcurl is built in static mode. KNOWN ISSUES: - running tests with unity builds may fail in cases. - some build configurations/env may not compile in unity mode. E.g.: https://ci.appveyor.com/project/curlorg/curl/builds/47230972/job/51wfesgnfuauwl8q#L250 Ref: https://github.com/libssh2/libssh2/issues/1034 Ref: https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html Ref: https://en.wikipedia.org/wiki/Unity_build Closes #11095
2023-05-09 18:10:40 +08:00
- job_name: "CMake, mingw-w64, Debug x64, Schannel, Static, Unity"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
BUILD_SYSTEM: CMake
PRJ_GEN: "MSYS Makefiles"
PRJ_CFG: Debug
OPENSSL: OFF
SCHANNEL: ON
ENABLE_UNICODE: OFF
HTTP_ONLY: OFF
TESTING: OFF
SHARED: OFF
ADD_PATH: "C:\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin;C:\\msys64\\usr\\bin"
MSYS2_ARG_CONV_EXCL: "/*"
BUILD_OPT: -k
UNITY: "ON"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, mingw-w64, Debug x86, Schannel, Static"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
AppVeyor: add 32-bit MinGW-w64 build With WinSSL and testing enabled so that it would have detected most of the warnings fixed in [0] and [1]. [0] https://github.com/curl/curl/pull/4398 [1] https://github.com/curl/curl/pull/4415 Closes https://github.com/curl/curl/pull/4433
2019-09-25 01:26:51 +08:00
BUILD_SYSTEM: CMake
PRJ_GEN: "MSYS Makefiles"
PRJ_CFG: Debug
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add 32-bit MinGW-w64 build With WinSSL and testing enabled so that it would have detected most of the warnings fixed in [0] and [1]. [0] https://github.com/curl/curl/pull/4398 [1] https://github.com/curl/curl/pull/4415 Closes https://github.com/curl/curl/pull/4433
2019-09-25 01:26:51 +08:00
HTTP_ONLY: OFF
TESTING: ON
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "!1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\mingw-w64\\i686-6.3.0-posix-dwarf-rt_v5-rev1\\mingw32\\bin;C:\\msys64\\usr\\bin"
AppVeyor: add 32-bit MinGW-w64 build With WinSSL and testing enabled so that it would have detected most of the warnings fixed in [0] and [1]. [0] https://github.com/curl/curl/pull/4398 [1] https://github.com/curl/curl/pull/4415 Closes https://github.com/curl/curl/pull/4433
2019-09-25 01:26:51 +08:00
MSYS2_ARG_CONV_EXCL: "/*"
BUILD_OPT: -k
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "CMake, mingw, Debug x86, no SSL, Static"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
BUILD_SYSTEM: CMake
AppVeyor: add classic MinGW build But use the MSYS2 shell rather than the default MSYS shell because of POSIX path conversion issues. Classic MinGW is only available on the Visual Studio 2015 image. Closes https://github.com/curl/curl/pull/3623
2019-02-27 00:38:14 +08:00
PRJ_GEN: "MSYS Makefiles"
PRJ_CFG: Debug
OPENSSL: OFF
TLS naming: fix more Winssl and Darwinssl leftovers The CMake option is now called CMAKE_USE_SCHANNEL The winbuild flag is USE_SCHANNEL The CI jobs and build scripts only use the new names and the new name options Tests now require 'Schannel' (when necessary) Closes #5795
2020-08-07 23:11:52 +08:00
SCHANNEL: OFF
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
ENABLE_UNICODE: OFF
AppVeyor: add classic MinGW build But use the MSYS2 shell rather than the default MSYS shell because of POSIX path conversion issues. Classic MinGW is only available on the Visual Studio 2015 image. Closes https://github.com/curl/curl/pull/3623
2019-02-27 00:38:14 +08:00
HTTP_ONLY: OFF
TESTING: ON
SHARED: OFF
cmake: set HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID on Windows `lib/config-win32.h` enables this configuration option unconditionally. Make it apply to CMake builds as well. While here, delete a broken check for `HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID` from `CMakeLists.txt`. This came with the initial commit [1], but did not include the actual verification code inside `CMake/CurlTests.c`, so it always failed. A later commit [2] added a second test, for non-Windows platforms. Enabling this flag causes test 1056 to fail with CMake builds, as they do with autotools builds. Let's apply the same solution and ignore the results here as well. [1] 4c5307b45655ba75ab066564afdc0c111a8b9291 [2] aec7c5a87c8482b6ddffa352d7d220698652262e Reviewed-by: Daniel Stenberg Assisted-by: Marcel Raad Closes #9726
2022-10-15 03:06:37 +08:00
DISABLED_TESTS: "!1139 !1501 ~1056"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\MinGW\\bin;C:\\msys64\\usr\\bin"
AppVeyor: add classic MinGW build But use the MSYS2 shell rather than the default MSYS shell because of POSIX path conversion issues. Classic MinGW is only available on the Visual Studio 2015 image. Closes https://github.com/curl/curl/pull/3623
2019-02-27 00:38:14 +08:00
MSYS2_ARG_CONV_EXCL: "/*"
appveyor: pass on -k to make
2019-07-31 23:17:52 +08:00
BUILD_OPT: -k
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
# winbuild-based builds
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2015, Debug"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
BUILD_SYSTEM: winbuild_vs2015
DEBUG: yes
PATHPART: debug
TESTING: OFF
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
ENABLE_UNICODE: no
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2015, Release"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
BUILD_SYSTEM: winbuild_vs2015
DEBUG: no
PATHPART: release
appveyor: add a winbuild Assisted-by: Marcel Raad Assisted-by: Jay Satiro Closes #4324
2019-09-11 19:57:32 +08:00
TESTING: OFF
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
ENABLE_UNICODE: no
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2017, Debug"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
BUILD_SYSTEM: winbuild_vs2017
DEBUG: yes
PATHPART: debug
TESTING: OFF
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
ENABLE_UNICODE: no
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2017, Release"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
BUILD_SYSTEM: winbuild_vs2017
DEBUG: no
PATHPART: release
appveyor: add a winbuild that uses VS2017 Closes #4482
2019-10-12 22:33:30 +08:00
TESTING: OFF
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
ENABLE_UNICODE: no
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2015, Debug, Unicode"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
BUILD_SYSTEM: winbuild_vs2015
DEBUG: yes
PATHPART: debug
TESTING: OFF
ENABLE_UNICODE: yes
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2015, Release, Unicode"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2015"
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
BUILD_SYSTEM: winbuild_vs2015
DEBUG: no
PATHPART: release
TESTING: OFF
ENABLE_UNICODE: yes
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2017, Debug, Unicode"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
BUILD_SYSTEM: winbuild_vs2017
DEBUG: yes
PATHPART: debug
TESTING: OFF
ENABLE_UNICODE: yes
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "winbuild, VS2017, Release, Unicode"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
BUILD_SYSTEM: winbuild_vs2017
DEBUG: no
PATHPART: release
TESTING: OFF
ENABLE_UNICODE: yes
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
# generated VisualStudioSolution-based builds
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "VisualStudioSolution, VS2017, Debug"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: add Visual Studio solution build Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:55:09 +08:00
BUILD_SYSTEM: VisualStudioSolution
PRJ_CFG: "DLL Debug - DLL Windows SSPI - DLL WinIDN"
TESTING: OFF
projects: Update VC version names for VS2017, VS2022 - Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files uses VC<ver> to indicate the MSVC version. At some point support for Visual Studio 2017 (Visual Studio version 15 which uses MSVC 14.10) was added as VC15. Visual Studio 2022 (Visual Studio version 17 which uses MSVC 14.30) project files were recently added and followed that same format using VC17. There is no such MSVC version (yet) as VC15 or VC17. For VS 2017 for example, the name we use is correct as either VS17, VS2017, VC14.10. I opted for the latter since we use VC for earlier versions (eg VC10, VC12, etc). Ref: https://github.com/curl/curl/pull/8438#issuecomment-1037070192 Closes https://github.com/curl/curl/pull/8447
2022-02-14 05:58:04 +08:00
VC_VERSION: VC14.10
appveyor: update comments to be clear about toolchain - CMake-based MSYS builds use mingw-w64 to cross-compile. - autotools-based builds are compiled using msys2-devel. The difference is that the later ones are not cross-compiled to Windows and instead require the msys2 runtime to be present. At the moment only the Azure Pipelines CI builds actually run autotools-based cross-compilation builds for Windows.
2020-05-10 00:04:38 +08:00
# autotools-based builds (NOT mingw cross-compiling, but msys2 native)
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "autotools, msys2, Debug, no Proxy, no SSL"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: add --disable-proxy autotools build This would have caught issue #3926. Also make formatting more consistent. Closes https://github.com/curl/curl/pull/4526
2019-10-12 19:27:51 +08:00
BUILD_SYSTEM: autotools
TESTING: ON
test1238: avoid tftpd being busy for tests shortly following The tftpd server may still be busy if the total timeout of 25 seconds has not been reached or no sread error was received during or after the execution of the timeout test 1238. Once the next TFTP test comes around (eg. 1242 or 1243), those will fail because the tftpd server is still waiting on data from curl due to the UDP protocol being stateless and having no connection close. On Linux this error may not happen, because ICMP errors generated due to a swrite error can also be returned async on the next sread call instead. Therefore we will now just kill the tftpd server after test 1238 to make sure that the following tests are not affected. This enables us to no longer ignore tests 1242, 1243, 2002 and 2003 on the CI platforms CirrusCI and AppVeyor. Assisted-by: Peter Wu Closes #5364
2020-05-11 00:40:24 +08:00
DISABLED_TESTS: "!19 ~1056 !1233"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
appveyor: enable websockets
2022-09-09 21:11:15 +08:00
CONFIG_ARGS: "--enable-debug --enable-werror --disable-threaded-resolver --disable-proxy --without-ssl --enable-websockets"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "autotools, msys2, Debug, no SSL"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: sort builds by type and add two new variants Related to #5034 and #5063
2020-03-07 04:02:18 +08:00
BUILD_SYSTEM: autotools
TESTING: ON
test1238: avoid tftpd being busy for tests shortly following The tftpd server may still be busy if the total timeout of 25 seconds has not been reached or no sread error was received during or after the execution of the timeout test 1238. Once the next TFTP test comes around (eg. 1242 or 1243), those will fail because the tftpd server is still waiting on data from curl due to the UDP protocol being stateless and having no connection close. On Linux this error may not happen, because ICMP errors generated due to a swrite error can also be returned async on the next sread call instead. Therefore we will now just kill the tftpd server after test 1238 to make sure that the following tests are not affected. This enables us to no longer ignore tests 1242, 1243, 2002 and 2003 on the CI platforms CirrusCI and AppVeyor. Assisted-by: Peter Wu Closes #5364
2020-05-11 00:40:24 +08:00
DISABLED_TESTS: "!19 !504 !704 !705 ~1056 !1233"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
appveyor: enable websockets
2022-09-09 21:11:15 +08:00
CONFIG_ARGS: "--enable-debug --enable-werror --disable-threaded-resolver --without-ssl --enable-websockets"
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "autotools, msys2, Release, no SSL"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2017"
appveyor: add non-debug plain autotools-based build This should enable us to catch linking issues with the testsuite early, like the one described/fixed in #5475. Reviewed-by: Daniel Stenberg Reviewed-by: Marcel Raad Closes #5477
2020-05-30 15:46:04 +08:00
BUILD_SYSTEM: autotools
TESTING: ON
DISABLED_TESTS: "!19 !504 !704 !705 ~1056 !1233"
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
ADD_PATH: "C:\\msys64\\usr\\bin"
appveyor: enable websockets
2022-09-09 21:11:15 +08:00
CONFIG_ARGS: "--enable-warnings --enable-werror --without-ssl --enable-websockets"
appveyor: add Cygwin build Closes https://github.com/curl/curl/pull/8693
2022-04-09 16:26:37 +08:00
# autotools-based Cygwin build
CI: report AppVeyor build status for each job Also give each job on AppVeyor CI a human-readable name. This aims to make job and therefore build failures more visible. Reviewed-by: Marcel Raad Closes #9769
2022-10-18 04:20:42 +08:00
- job_name: "autotools, cygwin, Debug, no SSL"
APPVEYOR_BUILD_WORKER_IMAGE: "Visual Studio 2022"
appveyor: add Cygwin build Closes https://github.com/curl/curl/pull/8693
2022-04-09 16:26:37 +08:00
BUILD_SYSTEM: autotools
TESTING: ON
DISABLED_TESTS: "~1056"
ADD_PATH: "C:\\cygwin64\\bin"
appveyor: enable websockets
2022-09-09 21:11:15 +08:00
CONFIG_ARGS: "--enable-debug --enable-werror --disable-threaded-resolver --without-ssl --enable-websockets"
appveyor: add Cygwin build Closes https://github.com/curl/curl/pull/8693
2022-04-09 16:26:37 +08:00
POSIX_PATH_PREFIX: "/cygdrive"
AppVeyor: add MinGW-w64 build Add a MinGW-w64 build using CMake's MSYS Makefiles generator. Use the Visual Studio 2015 image as it has GCC 8, while the Visual Studio 2017 image only has GCC 7.2. Closes https://github.com/curl/curl/pull/3623
2018-10-11 04:22:06 +08:00
install:
appveyor: only add MSYS2 to PATH where required Closes https://github.com/curl/curl/pull/8693
2019-03-02 18:53:33 +08:00
- if not "%ADD_PATH%"=="" (
set "PATH=%ADD_PATH%;%PATH%" )
CI: Added AppVeyor-CI for curl Closes #439
2015-09-17 21:34:47 +08:00
build_script:
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
- if %BUILD_SYSTEM%==CMake (
cmake .
-G"%PRJ_GEN%"
appveyor: upgrade VS2017 to VS2019 Closes #4383
2019-09-19 22:34:06 +08:00
%TARGET%
cmake: private identifiers use CURL_ instead of CMAKE_ prefix Since the 'CMAKE_' prefix is reserved for cmake's own private use. Ref: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html Reported-by: Boris Rasin Fixes #7988 Closes #8044
2021-11-23 00:39:46 +08:00
-DCURL_USE_OPENSSL=%OPENSSL%
-DCURL_USE_SCHANNEL=%SCHANNEL%
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
-DHTTP_ONLY=%HTTP_ONLY%
-DBUILD_SHARED_LIBS=%SHARED%
-DBUILD_TESTING=%TESTING%
appveyor: enable websockets
2022-09-09 21:11:15 +08:00
-DENABLE_WEBSOCKETS=%WEBSOCKETS%
cmake: add support for "unity" builds Aka "jumbo" or "amalgamation" builds. It means to compile all sources per target as a single C source. This is experimental. You can enable it by passing `-DCMAKE_UNITY_BUILD=ON` to cmake. It requires CMake 3.16 or newer. It makes builds (much) faster, allows for better optimizations and tends to promote less ambiguous code. Also add a new AppVeyor CI job and convert an existing one to use "unity" mode (one MSVC, one MinGW), and enable it for one macOS CI job. Fix related issues: - add missing include guard to `easy_lock.h`. - rename static variables and functions (and a macro) with names reused across sources, or shadowed by local variables. - add an `#undef` after use. - add a missing `#undef` before use. - move internal definitions from `ftp.h` to `ftp.c`. - `curl_memory.h` fixes to make it work when included repeatedly. - stop building/linking curlx bits twice for a static-mode curl tool. These caused doubly defined symbols in unity builds. - silence missing extern declarations compiler warning for ` _CRT_glob`. - fix extern declarations for `tool_freq` and `tool_isVistaOrGreater`. - fix colliding static symbols in debug mode: `debugtime()` and `statename`. - rename `ssl_backend_data` structure to unique names for each TLS-backend, along with the `ssl_connect_data` struct member referencing them. This required adding casts for each access. - add workaround for missing `[P]UNICODE_STRING` types in certain Windows builds when compiling `lib/ldap.c`. To support "unity" builds, we had to enable `SCHANNEL_USE_BLACKLISTS` for Schannel (a Windows `schannel.h` option) _globally_. This caused an indirect inclusion of Windows `schannel.h` from `ldap.c` via `winldap.h` to have it enabled as well. This requires `[P]UNICODE_STRING` types, which is apperantly not defined automatically (as seen with both MSVS and mingw-w64). This patch includes `<subauth.h>` to fix it. Ref: https://github.com/curl/curl/runs/13987772013 Ref: https://dev.azure.com/daniel0244/curl/_build/results?buildId=15827&view=logs&jobId=2c9f582d-e278-56b6-4354-f38a4d851906&j=2c9f582d-e278-56b6-4354-f38a4d851906&t=90509b00-34fa-5a81-35d7-5ed9569d331c - tweak unity builds to compile `lib/memdebug.c` separately in memory trace builds to avoid PP confusion. - force-disable unity for test programs. - do not compile and link libcurl sources to libtests _twice_ when libcurl is built in static mode. KNOWN ISSUES: - running tests with unity builds may fail in cases. - some build configurations/env may not compile in unity mode. E.g.: https://ci.appveyor.com/project/curlorg/curl/builds/47230972/job/51wfesgnfuauwl8q#L250 Ref: https://github.com/libssh2/libssh2/issues/1034 Ref: https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html Ref: https://en.wikipedia.org/wiki/Unity_build Closes #11095
2023-05-09 18:10:40 +08:00
-DCMAKE_UNITY_BUILD=%UNITY%
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
-DCURL_WERROR=ON
-DENABLE_DEBUG=ON
AppVeyor: switch 64-bit Schannel Debug CMake builds to Unicode The Schannel builds are the most useful to verify as they make the most use of the Windows API. Classic MinGW doesn't support Unicode at all, only MinGW-w64 and MSVC do. Closes https://github.com/curl/curl/pull/5843
2020-08-22 16:16:13 +08:00
-DENABLE_UNICODE=%ENABLE_UNICODE%
appveyor: add support for other build systems Introduce BUILD_SYSTEM variable, which is currently always CMake. Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:38:17 +08:00
-DCMAKE_RUNTIME_OUTPUT_DIRECTORY_RELEASE=""
-DCMAKE_RUNTIME_OUTPUT_DIRECTORY_DEBUG=""
-DCMAKE_INSTALL_PREFIX="C:/CURL"
-DCMAKE_BUILD_TYPE=%PRJ_CFG% &&
appveyor: add --disable-proxy autotools build This would have caught issue #3926. Also make formatting more consistent. Closes https://github.com/curl/curl/pull/4526
2019-10-12 19:27:51 +08:00
cmake --build . --config %PRJ_CFG% --parallel 2 --clean-first -- %BUILD_OPT%
) else (
appveyor: add Visual Studio solution build Closes https://github.com/curl/curl/pull/3941
2019-05-25 14:55:09 +08:00
if %BUILD_SYSTEM%==VisualStudioSolution (
cd projects &&
.\\generate.bat %VC_VERSION% &&
appveyor: add --disable-proxy autotools build This would have caught issue #3926. Also make formatting more consistent. Closes https://github.com/curl/curl/pull/4526
2019-10-12 19:27:51 +08:00
msbuild.exe /p:Configuration="%PRJ_CFG%" "Windows\\%VC_VERSION%\\curl-all.sln"
) else (
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
if %BUILD_SYSTEM%==winbuild_vs2015 (
appveyor: add a winbuild Assisted-by: Marcel Raad Assisted-by: Jay Satiro Closes #4324
2019-09-11 19:57:32 +08:00
call buildconf.bat &&
cd winbuild &&
call "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x64 &&
call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86_amd64 &&
appveyor: add Unicode winbuild jobs These are cheap as they don't build tests. Closes https://github.com/curl/curl/pull/5063
2020-01-03 08:59:58 +08:00
nmake /f Makefile.vc mode=dll VC=14 "SSL_PATH=C:\OpenSSL-v111-Win64" WITH_SSL=dll MACHINE=x64 DEBUG=%DEBUG% ENABLE_UNICODE=%ENABLE_UNICODE% &&
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
..\builds\libcurl-vc14-x64-%PATHPART%-dll-ssl-dll-ipv6-sspi\bin\curl.exe -V
appveyor: add a winbuild that uses VS2017 Closes #4482
2019-10-12 22:33:30 +08:00
) else (
appveyor: make winbuilds with DEBUG=no/yes and VS 2015/2017 ... and invoke "curl -V" once done Co-Authored-By: Jay Satiro Closes #4523
2019-10-24 22:23:45 +08:00
if %BUILD_SYSTEM%==winbuild_vs2017 (
appveyor: add a winbuild that uses VS2017 Closes #4482
2019-10-12 22:33:30 +08:00
call buildconf.bat &&
cd winbuild &&
call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat" &&
projects: Update VC version names for VS2017, VS2022 - Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files uses VC<ver> to indicate the MSVC version. At some point support for Visual Studio 2017 (Visual Studio version 15 which uses MSVC 14.10) was added as VC15. Visual Studio 2022 (Visual Studio version 17 which uses MSVC 14.30) project files were recently added and followed that same format using VC17. There is no such MSVC version (yet) as VC15 or VC17. For VS 2017 for example, the name we use is correct as either VS17, VS2017, VC14.10. I opted for the latter since we use VC for earlier versions (eg VC10, VC12, etc). Ref: https://github.com/curl/curl/pull/8438#issuecomment-1037070192 Closes https://github.com/curl/curl/pull/8447
2022-02-14 05:58:04 +08:00
nmake /f Makefile.vc mode=dll VC=14.10 "SSL_PATH=C:\OpenSSL-v111-Win64" WITH_SSL=dll MACHINE=x64 DEBUG=%DEBUG% ENABLE_UNICODE=%ENABLE_UNICODE% &&
..\builds\libcurl-vc14.10-x64-%PATHPART%-dll-ssl-dll-ipv6-sspi\bin\curl.exe -V
appveyor: add --disable-proxy autotools build This would have caught issue #3926. Also make formatting more consistent. Closes https://github.com/curl/curl/pull/4526
2019-10-12 19:27:51 +08:00
) else (
if %BUILD_SYSTEM%==autotools (
appveyor: add Cygwin build Closes https://github.com/curl/curl/pull/8693
2022-04-09 16:26:37 +08:00
bash.exe -e -l -c "cd %POSIX_PATH_PREFIX%/c/projects/curl && autoreconf -fi && ./configure %CONFIG_ARGS% && make V=1 && make V=1 examples && cd tests && make V=1"
appveyor: add --disable-proxy autotools build This would have caught issue #3926. Also make formatting more consistent. Closes https://github.com/curl/curl/pull/4526
2019-10-12 19:27:51 +08:00
)))))
CI/tests: fix invocation of tests for CMake builds Update appveyor.yml to set env variable TFLAGS and run tests Remove curly braces due to CMake error (${TFLAGS} -> $TFLAGS) Move testdeps build to build step (per review comments) Reviewed-by: Marc Hörsken Closes #6066 Fixes #6052
2020-10-13 03:44:37 +08:00
- if %TESTING%==ON (
if %BUILD_SYSTEM%==CMake (
cmake --build . --config %PRJ_CFG% --parallel 2 --target testdeps
))
ci: whitelist branches to avoid testing feature branches twice
2017-06-21 05:00:49 +08:00
AppVeyor: run test suite Use the preinstalled MSYS2 bash for that. Disable test 1139 as the CMake build doesn't generate curl.1. Ref: https://github.com/curl/curl/issues/3070#issuecomment-425922224 Closes https://github.com/curl/curl/pull/3100
2018-10-02 23:47:39 +08:00
test_script:
CI/runtests.pl: add param for dedicated curl to talk to APIs This should make it possible to also report test failures if our freshly build curl binary is not fully functional. Reviewed-by: Daniel Stenberg Closes #9360
2022-08-25 03:46:25 +08:00
- if exist C:/msys64/usr/bin/curl.exe (
set ACURL=-ac %POSIX_PATH_PREFIX%/c/msys64/usr/bin/curl.exe )
- if exist C:/Windows/System32/curl.exe (
set ACURL=-ac %POSIX_PATH_PREFIX%/c/Windows/System32/curl.exe )
AppVeyor: run test suite Use the preinstalled MSYS2 bash for that. Disable test 1139 as the CMake build doesn't generate curl.1. Ref: https://github.com/curl/curl/issues/3070#issuecomment-425922224 Closes https://github.com/curl/curl/pull/3100
2018-10-02 23:47:39 +08:00
- if %TESTING%==ON (
CI/tests: fix invocation of tests for CMake builds Update appveyor.yml to set env variable TFLAGS and run tests Remove curly braces due to CMake error (${TFLAGS} -> $TFLAGS) Move testdeps build to build step (per review comments) Reviewed-by: Marc Hörsken Closes #6066 Fixes #6052
2020-10-13 03:44:37 +08:00
if %BUILD_SYSTEM%==CMake (
CI/runtests.pl: add param for dedicated curl to talk to APIs This should make it possible to also report test failures if our freshly build curl binary is not fully functional. Reviewed-by: Daniel Stenberg Closes #9360
2022-08-25 03:46:25 +08:00
set TFLAGS=%ACURL% %DISABLED_TESTS% &&
CI/makefiles: introduce dedicated test target Make it easy to use the same set of test flags throughout all current and future CI builds. Reviewed-by: Jay Satiro Follow up to #7690 Closes #7785
2021-09-28 03:17:29 +08:00
cmake --build . --config %PRJ_CFG% --target test-ci
CI/tests: fix invocation of tests for CMake builds Update appveyor.yml to set env variable TFLAGS and run tests Remove curly braces due to CMake error (${TFLAGS} -> $TFLAGS) Move testdeps build to build step (per review comments) Reviewed-by: Marc Hörsken Closes #6066 Fixes #6052
2020-10-13 03:44:37 +08:00
) else (
CI: align make and test flags in various config files 1. Use Makefile target to run tests in autotools builds on AppVeyor. 2. Disable testing of SCP protocol on native Windows environments. 3. Remove redundant parameters -a -p from target test-nonflaky. 4. Don't use -vc parameter which is reserved for debugging. Replaces #7591 Closes #7690
2021-09-28 02:59:29 +08:00
if %BUILD_SYSTEM%==autotools (
CI/runtests.pl: add param for dedicated curl to talk to APIs This should make it possible to also report test failures if our freshly build curl binary is not fully functional. Reviewed-by: Daniel Stenberg Closes #9360
2022-08-25 03:46:25 +08:00
bash.exe -e -l -c "cd %POSIX_PATH_PREFIX%/c/projects/curl && make V=1 TFLAGS='%ACURL% %DISABLED_TESTS%' test-ci"
CI: align make and test flags in various config files 1. Use Makefile target to run tests in autotools builds on AppVeyor. 2. Disable testing of SCP protocol on native Windows environments. 3. Remove redundant parameters -a -p from target test-nonflaky. 4. Don't use -vc parameter which is reserved for debugging. Replaces #7591 Closes #7690
2021-09-28 02:59:29 +08:00
) else (
CI/runtests.pl: add param for dedicated curl to talk to APIs This should make it possible to also report test failures if our freshly build curl binary is not fully functional. Reviewed-by: Daniel Stenberg Closes #9360
2022-08-25 03:46:25 +08:00
bash.exe -e -l -c "cd %POSIX_PATH_PREFIX%/c/projects/curl/tests && ./runtests.pl -a -p !flaky -r -rm %ACURL% %DISABLED_TESTS%"
CI: align make and test flags in various config files 1. Use Makefile target to run tests in autotools builds on AppVeyor. 2. Disable testing of SCP protocol on native Windows environments. 3. Remove redundant parameters -a -p from target test-nonflaky. 4. Don't use -vc parameter which is reserved for debugging. Replaces #7591 Closes #7690
2021-09-28 02:59:29 +08:00
))
)
AppVeyor: run test suite Use the preinstalled MSYS2 bash for that. Disable test 1139 as the CMake build doesn't generate curl.1. Ref: https://github.com/curl/curl/issues/3070#issuecomment-425922224 Closes https://github.com/curl/curl/pull/3100
2018-10-02 23:47:39 +08:00
wording: avoid blacklist/whitelist stereotypes Instead of discussing if there's value or meaning (implied or not) in the colors, let's use words without the same possibly negative associations. Closes #5546
2020-06-09 22:08:11 +08:00
# select branches to avoid testing feature branches twice (as branch and as pull request)
ci: whitelist branches to avoid testing feature branches twice
2017-06-21 05:00:49 +08:00
branches:
only:
- master
appveyor: also build "/ci" branches like travis
2019-05-10 21:52:57 +08:00
- /\/ci$/
appveyor: publish artifacts on appveyor This allows obtaining upstream builds of curl directly from appveyor for all the available configurations Closes #4509
2019-10-20 02:37:06 +08:00
CI: don't run CI jobs if only another CI was changed A few paths were missed in the last commit, as well as a job added since then. Followup-to 395b9175
2023-04-25 07:34:26 +08:00
skip_commits:
files:
- '.azure-pipelines.yml'
CI: use another glob syntax for matching files on Appveyor The previous globbing syntax was not matching files recursively in directories, so try appending a /* to more closely match the examples at https://www.appveyor.com/docs/how-to/filtering-commits/
2023-04-29 01:28:06 +08:00
- '.circleci/**/*'
CI: don't run CI jobs if only another CI was changed A few paths were missed in the last commit, as well as a job added since then. Followup-to 395b9175
2023-04-25 07:34:26 +08:00
- '.cirrus.yml'
CI: use another glob syntax for matching files on Appveyor The previous globbing syntax was not matching files recursively in directories, so try appending a /* to more closely match the examples at https://www.appveyor.com/docs/how-to/filtering-commits/
2023-04-29 01:28:06 +08:00
- '.github/**/*'
- 'packages/**/*'
- 'plan9/**/*'
CI: don't run CI jobs if only another CI was changed A few paths were missed in the last commit, as well as a job added since then. Followup-to 395b9175
2023-04-25 07:34:26 +08:00
appveyor: publish artifacts on appveyor This allows obtaining upstream builds of curl directly from appveyor for all the available configurations Closes #4509
2019-10-20 02:37:06 +08:00
artifacts:
- path: '**/curl.exe'
name: curl
appveyor: collect libcurl.dll variants with prefix or suffix On some platforms libcurl is build with a platform-specific prefix and/or a version number suffix. Assisted-by: Jay Satiro Closes #5659
2020-07-13 04:04:00 +08:00
- path: '**/*curl*.dll'
cmake: add support for "unity" builds Aka "jumbo" or "amalgamation" builds. It means to compile all sources per target as a single C source. This is experimental. You can enable it by passing `-DCMAKE_UNITY_BUILD=ON` to cmake. It requires CMake 3.16 or newer. It makes builds (much) faster, allows for better optimizations and tends to promote less ambiguous code. Also add a new AppVeyor CI job and convert an existing one to use "unity" mode (one MSVC, one MinGW), and enable it for one macOS CI job. Fix related issues: - add missing include guard to `easy_lock.h`. - rename static variables and functions (and a macro) with names reused across sources, or shadowed by local variables. - add an `#undef` after use. - add a missing `#undef` before use. - move internal definitions from `ftp.h` to `ftp.c`. - `curl_memory.h` fixes to make it work when included repeatedly. - stop building/linking curlx bits twice for a static-mode curl tool. These caused doubly defined symbols in unity builds. - silence missing extern declarations compiler warning for ` _CRT_glob`. - fix extern declarations for `tool_freq` and `tool_isVistaOrGreater`. - fix colliding static symbols in debug mode: `debugtime()` and `statename`. - rename `ssl_backend_data` structure to unique names for each TLS-backend, along with the `ssl_connect_data` struct member referencing them. This required adding casts for each access. - add workaround for missing `[P]UNICODE_STRING` types in certain Windows builds when compiling `lib/ldap.c`. To support "unity" builds, we had to enable `SCHANNEL_USE_BLACKLISTS` for Schannel (a Windows `schannel.h` option) _globally_. This caused an indirect inclusion of Windows `schannel.h` from `ldap.c` via `winldap.h` to have it enabled as well. This requires `[P]UNICODE_STRING` types, which is apperantly not defined automatically (as seen with both MSVS and mingw-w64). This patch includes `<subauth.h>` to fix it. Ref: https://github.com/curl/curl/runs/13987772013 Ref: https://dev.azure.com/daniel0244/curl/_build/results?buildId=15827&view=logs&jobId=2c9f582d-e278-56b6-4354-f38a4d851906&j=2c9f582d-e278-56b6-4354-f38a4d851906&t=90509b00-34fa-5a81-35d7-5ed9569d331c - tweak unity builds to compile `lib/memdebug.c` separately in memory trace builds to avoid PP confusion. - force-disable unity for test programs. - do not compile and link libcurl sources to libtests _twice_ when libcurl is built in static mode. KNOWN ISSUES: - running tests with unity builds may fail in cases. - some build configurations/env may not compile in unity mode. E.g.: https://ci.appveyor.com/project/curlorg/curl/builds/47230972/job/51wfesgnfuauwl8q#L250 Ref: https://github.com/libssh2/libssh2/issues/1034 Ref: https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html Ref: https://en.wikipedia.org/wiki/Unity_build Closes #11095
2023-05-09 18:10:40 +08:00
name: libcurl dll
Reference in New Issue Copy Permalink