yuzu/libusb
1
0
Fork 0
mirror of https://github.com/libusb/libusb synced 2024-11-21 14:29:12 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions
libusb/appveyor.yml

109 lines
3.6 KiB
YAML
Raw Normal View History

AppVeyor: initial configuration file Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 13:11:20 -07:00
version: 1.0.{build}
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
image:
- Visual Studio 2013
- Visual Studio 2015
- Visual Studio 2017
- Visual Studio 2019
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
- Visual Studio 2022
AppVeyor: initial configuration file Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 13:11:20 -07:00
platform:
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
- Win32
- x64
configuration:
- Debug
- Release
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: UNK
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
clone_depth: 1
AppVeyor: use a .bat file now - Changes in platform configuration, x86 breaks the build - Solution file does not contain platform for Any CPU,fixing it to Win32 - Added Multiple solutions to appveyor configuration file - Added batch script for VS2010 builds - Added fixes to appveyor.bat file and appveyor.yml - Fixes for Platform and Configuration in appveyor.bat - Fixed windows exit code, Appveyor reports exit on succesful build - Multiple Builds in same platform and configuration,fixed it
2016-03-03 04:31:37 -07:00
build:
parallel: true
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
for:
-
matrix:
only:
- image: Visual Studio 2013
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: v120
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
build:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
project: msvc\libusb.sln
AppVeyor: add cygwin and minGW support - Changes in platform configuration, x86 breaks the build - Solution file does not contain platform for Any CPU, fixing it to Win32 - Added Multiple solutions to appveyor configuration file - Added batch script for VS2010 builds - Added fixes to appveyor.bat file and appveyor.yml - Fixes for Platform and Configuration in appveyor.bat - Fixed windows exit code, Appveyor reports exit on succesful build - Multiple Builds in same platform and configuration, fixed it - Added appveyor configuration to compile using MinGW 32-bit and 64-bits - Minor Fixes for batch file and Added cygwin build script Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 04:31:37 -07:00
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
-
matrix:
only:
- image: Visual Studio 2015
configuration: Debug
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: v140
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
build:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
project: msvc\libusb.sln
AppVeyor: add cygwin and minGW support - Changes in platform configuration, x86 breaks the build - Solution file does not contain platform for Any CPU, fixing it to Win32 - Added Multiple solutions to appveyor configuration file - Added batch script for VS2010 builds - Added fixes to appveyor.bat file and appveyor.yml - Fixes for Platform and Configuration in appveyor.bat - Fixed windows exit code, Appveyor reports exit on succesful build - Multiple Builds in same platform and configuration, fixed it - Added appveyor configuration to compile using MinGW 32-bit and 64-bits - Minor Fixes for batch file and Added cygwin build script Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 04:31:37 -07:00
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
-
matrix:
only:
- image: Visual Studio 2015
platform: Win32
configuration: Release
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: v140
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
install:
- cmd: xcopy /S /I "%APPVEYOR_BUILD_FOLDER%" C:\msys64\home\appveyor\libusb
- cmd: xcopy /S /I "%APPVEYOR_BUILD_FOLDER%" C:\cygwin\home\appveyor\libusb
build_script:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
- cmd: msbuild "%APPVEYOR_BUILD_FOLDER%\msvc\libusb.sln" /m /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
Move CI-related files into .private directory and add unified build script The files needed for Continuous Integration (AppVeyor, Travis) are not meant for public consumption, so clean up the root directory by moving these files underneath .private. Create a single build script that is leveraged by both AppVeyor and Travis. This script replaces the previous 'travis-autogen.sh' file and enables additional compiler warnings that should provide additional coverage for all build environments. Update the Travis configuration file to absorb the Brewfile and update the Xcode images. Per warnings from Travis, Xcode6.4 is obsolete, thus replace it with Xcode7.3. Additionally remove the "gcc" variants for the macOS builds. The builds never used gcc to begin with and actually using gcc causes build errors due to Clang-specific pragmas in the IOKit header files. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-31 15:47:31 -07:00
- cmd: C:\msys64\usr\bin\bash -l "%APPVEYOR_BUILD_FOLDER%\.private\appveyor_build.sh" MinGW
- cmd: C:\cygwin\bin\bash -l "%APPVEYOR_BUILD_FOLDER%\.private\appveyor_build.sh" cygwin
appveyor: Retain MinGW and cygwin build artifacts Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
2022-02-09 03:41:26 -07:00
after_build:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
- cmd: 7z a "libusb-build_%APPVEYOR_BUILD_WORKER_IMAGE%_%PLATFORM%_%CONFIGURATION%.7z" tag_* README-build.txt build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\dll build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\lib build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\*.exe C:\msys64\home\appveyor\libusb-MinGW-Win32 C:\cygwin\home\appveyor\libusb-cygwin-Win32
AppVeyor: initial configuration file Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 13:11:20 -07:00
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
-
matrix:
only:
- image: Visual Studio 2015
platform: x64
configuration: Release
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: v140
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
install:
- cmd: xcopy /S /I "%APPVEYOR_BUILD_FOLDER%" C:\msys64\home\appveyor\libusb
- cmd: xcopy /S /I "%APPVEYOR_BUILD_FOLDER%" C:\cygwin64\home\appveyor\libusb
build_script:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
- cmd: msbuild "%APPVEYOR_BUILD_FOLDER%\msvc\libusb.sln" /m /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
Move CI-related files into .private directory and add unified build script The files needed for Continuous Integration (AppVeyor, Travis) are not meant for public consumption, so clean up the root directory by moving these files underneath .private. Create a single build script that is leveraged by both AppVeyor and Travis. This script replaces the previous 'travis-autogen.sh' file and enables additional compiler warnings that should provide additional coverage for all build environments. Update the Travis configuration file to absorb the Brewfile and update the Xcode images. Per warnings from Travis, Xcode6.4 is obsolete, thus replace it with Xcode7.3. Additionally remove the "gcc" variants for the macOS builds. The builds never used gcc to begin with and actually using gcc causes build errors due to Clang-specific pragmas in the IOKit header files. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-31 15:47:31 -07:00
- cmd: C:\msys64\usr\bin\bash -l "%APPVEYOR_BUILD_FOLDER%\.private\appveyor_build.sh" MinGW
- cmd: C:\cygwin64\bin\bash -l "%APPVEYOR_BUILD_FOLDER%\.private\appveyor_build.sh" cygwin
appveyor: Retain MinGW and cygwin build artifacts Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
2022-02-09 03:41:26 -07:00
after_build:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
- cmd: 7z a "libusb-build_%APPVEYOR_BUILD_WORKER_IMAGE%_%PLATFORM%_%CONFIGURATION%.7z" tag_* README-build.txt build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\dll build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\lib build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\*.exe C:\msys64\home\appveyor\libusb-MinGW-x64 C:\cygwin64\home\appveyor\libusb-cygwin-x64
AppVeyor: initial configuration file Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 13:11:20 -07:00
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
-
matrix:
only:
- image: Visual Studio 2017
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: v141
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
build:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
project: msvc\libusb.sln
AppVeyor: add cygwin and minGW support - Changes in platform configuration, x86 breaks the build - Solution file does not contain platform for Any CPU, fixing it to Win32 - Added Multiple solutions to appveyor configuration file - Added batch script for VS2010 builds - Added fixes to appveyor.bat file and appveyor.yml - Fixes for Platform and Configuration in appveyor.bat - Fixed windows exit code, Appveyor reports exit on succesful build - Multiple Builds in same platform and configuration, fixed it - Added appveyor configuration to compile using MinGW 32-bit and 64-bits - Minor Fixes for batch file and Added cygwin build script Signed-off-by: Ludovic Rousseau <ludovic.rousseau@free.fr>
2016-03-03 04:31:37 -07:00
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
-
matrix:
only:
- image: Visual Studio 2019
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
environment:
toolset: v142
appveyor: Increase build coverage to all VS solutions Using the 'for' construct allows the specification of a more complex build matrix. This additionally simplifies the builds using MinGW and Cygwin because the build script can be unified and does not require checking for the 'Release' configuration. This change also extends the MinGW builds to cover both 32-bit and 64-bit builds using GCC versions 6.3.0 and 8.1.0, respectively. The Cygwin builds were similarly extended to include 64-bit build coverage. Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
2020-03-26 15:40:23 -07:00
build:
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
project: msvc\libusb.sln
-
matrix:
only:
- image: Visual Studio 2022
environment:
toolset: v143
build:
project: msvc\libusb.sln
appveyor: Retain selected build artifacts Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
2022-01-29 14:04:08 -07:00
after_build:
- cmd: ECHO This was built by %APPVEYOR_BUILD_WORKER_IMAGE% from %APPVEYOR_REPO_NAME% commit %APPVEYOR_REPO_COMMIT% > README-build.txt
- cmd: ECHO > tag_%APPVEYOR_REPO_TAG_NAME%_commit_%APPVEYOR_REPO_COMMIT%
msvc: Rework msbuild files Refactor common settings into .props files. Enables building full PlatformToolset, Platform, Configuration matrix easily. Also update the appveyor file. Technically we no longer need different images (could just have a single vs2022 image which is executed multiple times in parallel, or so) Closes #1116
2022-02-26 20:29:43 -07:00
- cmd: 7z a "libusb-build_%APPVEYOR_BUILD_WORKER_IMAGE%_%PLATFORM%_%CONFIGURATION%.7z" tag_* README-build.txt build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\dll build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\lib build\%TOOLSET%\%PLATFORM%\%CONFIGURATION%\*.exe
appveyor: Retain selected build artifacts Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
2022-01-29 14:04:08 -07:00
artifacts:
- path: "libusb-build_%APPVEYOR_BUILD_WORKER_IMAGE%_%PLATFORM%_%CONFIGURATION%.7z"
Reference in a new issue Copy permalink