Miroirs/mame
1
0
Fork 0
mirror of https://github.com/mamedev/mame.git synced 2024-11-16 07:48:32 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mame/.appveyor.yml

59 lines
3.1 KiB
YAML
Raw Normal View History

Added AppVeyor config
2018-06-03 20:37:26 +02:00
version: 1.0.{build}
appveyor: another one (nw)
2018-11-23 11:00:24 +01:00
image:
Continuous integration improvements (#5703) * Add workaround for imgtool and jedutil failing vs2019 debug builds with /ZI * No longer allow msvc build to fail * Enable tools build for travis to make it more useful * Switch travis to Xcode 11 in order to fix nltool linking failure * Prefer 64-bit compiler with VS 2019 too * Setting PreferredToolArchitecture to x64 is not needed, genie puts it into the project files for vs2015 or later * OPTIMIZE=1 build is faster that OPTIMIZE=0 for some reason. So fast in fact, that TOOLS=1 can be enabled without hitting the 60 minute timeout * Switch MINGW build to VS 2017 image until appveyor figure out why builds on VS 2019 are almost twice as slow * Run pacman twice to account for core system upgrades
2019-10-18 16:30:48 +02:00
- Visual Studio 2017
appveyor: let's try vs2019 16.3.0 (nw)
2019-09-26 05:44:36 +02:00
- Visual Studio 2019
Added AppVeyor config
2018-06-03 20:37:26 +02:00
shallow_clone: true
clone_depth: 1
Add gcc build to appveyor (#5654) * Add gcc build to appveyor As tea-ci has been broken for quite a while now there has been no MINGW CI available. MINGW builds can be done in appveyor too. Tools build had to be disabled as it takes longer than the allowed 60 minutes. Wa,-mbig-obj was added to avoid "file too big" errors. * Align appveyor gcc build configuration with travis This will hopefully make the build fast enough not to miss the 60 minute maximum build time * Turns out non-debug build needs -mbig-obj too
2019-09-17 21:41:44 +02:00
environment:
matrix:
- BUILD: GCC
- BUILD: MSVC
Continuous integration improvements (#5703) * Add workaround for imgtool and jedutil failing vs2019 debug builds with /ZI * No longer allow msvc build to fail * Enable tools build for travis to make it more useful * Switch travis to Xcode 11 in order to fix nltool linking failure * Prefer 64-bit compiler with VS 2019 too * Setting PreferredToolArchitecture to x64 is not needed, genie puts it into the project files for vs2015 or later * OPTIMIZE=1 build is faster that OPTIMIZE=0 for some reason. So fast in fact, that TOOLS=1 can be enabled without hitting the 60 minute timeout * Switch MINGW build to VS 2017 image until appveyor figure out why builds on VS 2019 are almost twice as slow * Run pacman twice to account for core system upgrades
2019-10-18 16:30:48 +02:00
matrix:
exclude:
- image: Visual Studio 2017
BUILD: MSVC
- image: Visual Studio 2019
BUILD: GCC
Added AppVeyor config
2018-06-03 20:37:26 +02:00
install:
- set "PATH=C:\msys64\usr\bin;C:\msys64\mingw64\bin;C:\Windows\System32;C:\Windows;%PATH%"
- set MSYSTEM=MINGW64
appveyor: try this (nw)
2019-09-26 07:17:36 +02:00
Added AppVeyor config
2018-06-03 20:37:26 +02:00
build_script:
Fix non-x86 build and try to make sure it does not break silently again (#7041) * Do not build x64 DRC backend when C backend is forced * New CI target (mametiny + kinst) * Switch travis to CI target * Switch appveyor to CI target
2020-08-12 18:54:22 +02:00
- bash -lc "exec 0</dev/null && cd $APPVEYOR_BUILD_FOLDER && export MINGW64=/mingw64 && make SUBTARGET=ci PTR64=1 TOOLS=1 OPTIMIZE=0 vs2019 -j3"
- msbuild "build\projects\windows\mameci\vs2019\mameci.sln" /m /p:ContinueOnError=false /p:StopOnFirstFailure=true /property:Configuration=Debug /property:Platform=x64 /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
Add gcc build to appveyor (#5654) * Add gcc build to appveyor As tea-ci has been broken for quite a while now there has been no MINGW CI available. MINGW builds can be done in appveyor too. Tools build had to be disabled as it takes longer than the allowed 60 minutes. Wa,-mbig-obj was added to avoid "file too big" errors. * Align appveyor gcc build configuration with travis This will hopefully make the build fast enough not to miss the 60 minute maximum build time * Turns out non-debug build needs -mbig-obj too
2019-09-17 21:41:44 +02:00
for:
-
matrix:
only:
- BUILD: GCC
Synced with GENie upstream revision e78d6c1 (#5631) * Synced with GENie upstream revision e78d6c1 * Add Visual Studio 2019 support * Fix hardcoded -m64 * Switch appveyor to Visual Studio 2019 * Fix genie being built as 32-bit * MSVC build is known to be broken currently. Let it fail until all the known issues are fixed. * Update the packages before building * Build with 3 threads Appveyor VMs have only 2 cores and 8 GB RAM. * Enable caching of pacman cache
2019-09-29 15:30:18 +02:00
cache:
- C:\msys64\var\cache\pacman\pkg
install:
- set "PATH=C:\msys64\usr\bin;C:\msys64\mingw64\bin;C:\Windows\System32;C:\Windows;%PATH%"
- set MSYSTEM=MINGW64
Appveyor msys2 workaround (#7002) * Work around appveyor not being able to update msys2 There has been a change to msys2 package maintainers, meaning that the packages are now signed with a different key: https://www.msys2.org/news/#2020-06-29-new-packagers Import the new keys manually until appveyor image is updated with a new msys2-keyring package * Explicitly kill msys2 before the second pacman call
2020-07-25 23:20:29 +02:00
- bash -lc "curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz"
- bash -lc "curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig"
Fix redundancy in pacman-key --verify call Appveyor VS2017 image only ships with pacman 5.1.3 as of now. In that version pacman-key --verify only takes one argument, the signature.
2020-07-29 07:38:26 +02:00
- bash -lc "pacman-key --verify msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig"
Appveyor msys2 workaround (#7002) * Work around appveyor not being able to update msys2 There has been a change to msys2 package maintainers, meaning that the packages are now signed with a different key: https://www.msys2.org/news/#2020-06-29-new-packagers Import the new keys manually until appveyor image is updated with a new msys2-keyring package * Explicitly kill msys2 before the second pacman call
2020-07-25 23:20:29 +02:00
- bash -lc "pacman -U --noconfirm msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz"
Synced with GENie upstream revision e78d6c1 (#5631) * Synced with GENie upstream revision e78d6c1 * Add Visual Studio 2019 support * Fix hardcoded -m64 * Switch appveyor to Visual Studio 2019 * Fix genie being built as 32-bit * MSVC build is known to be broken currently. Let it fail until all the known issues are fixed. * Update the packages before building * Build with 3 threads Appveyor VMs have only 2 cores and 8 GB RAM. * Enable caching of pacman cache
2019-09-29 15:30:18 +02:00
- bash -lc "pacman -Syu --noconfirm"
Appveyor msys2 workaround (#7002) * Work around appveyor not being able to update msys2 There has been a change to msys2 package maintainers, meaning that the packages are now signed with a different key: https://www.msys2.org/news/#2020-06-29-new-packagers Import the new keys manually until appveyor image is updated with a new msys2-keyring package * Explicitly kill msys2 before the second pacman call
2020-07-25 23:20:29 +02:00
- taskkill /f /fi "MODULES eq msys-2.0.dll"
Continuous integration improvements (#5703) * Add workaround for imgtool and jedutil failing vs2019 debug builds with /ZI * No longer allow msvc build to fail * Enable tools build for travis to make it more useful * Switch travis to Xcode 11 in order to fix nltool linking failure * Prefer 64-bit compiler with VS 2019 too * Setting PreferredToolArchitecture to x64 is not needed, genie puts it into the project files for vs2015 or later * OPTIMIZE=1 build is faster that OPTIMIZE=0 for some reason. So fast in fact, that TOOLS=1 can be enabled without hitting the 60 minute timeout * Switch MINGW build to VS 2017 image until appveyor figure out why builds on VS 2019 are almost twice as slow * Run pacman twice to account for core system upgrades
2019-10-18 16:30:48 +02:00
- bash -lc "pacman -Syu --noconfirm"
Add gcc build to appveyor (#5654) * Add gcc build to appveyor As tea-ci has been broken for quite a while now there has been no MINGW CI available. MINGW builds can be done in appveyor too. Tools build had to be disabled as it takes longer than the allowed 60 minutes. Wa,-mbig-obj was added to avoid "file too big" errors. * Align appveyor gcc build configuration with travis This will hopefully make the build fast enough not to miss the 60 minute maximum build time * Turns out non-debug build needs -mbig-obj too
2019-09-17 21:41:44 +02:00
build_script:
Fix non-x86 build and try to make sure it does not break silently again (#7041) * Do not build x64 DRC backend when C backend is forced * New CI target (mametiny + kinst) * Switch travis to CI target * Switch appveyor to CI target
2020-08-12 18:54:22 +02:00
- bash -lc "exec 0</dev/null && cd $APPVEYOR_BUILD_FOLDER && export MINGW64=/mingw64 && make SUBTARGET=ci PTR64=1 TOOLS=1 OPTIMIZE=3 IGNORE_GIT=1 -j3"
Add gcc build to appveyor (#5654) * Add gcc build to appveyor As tea-ci has been broken for quite a while now there has been no MINGW CI available. MINGW builds can be done in appveyor too. Tools build had to be disabled as it takes longer than the allowed 60 minutes. Wa,-mbig-obj was added to avoid "file too big" errors. * Align appveyor gcc build configuration with travis This will hopefully make the build fast enough not to miss the 60 minute maximum build time * Turns out non-debug build needs -mbig-obj too
2019-09-17 21:41:44 +02:00
test_script:
Fix non-x86 build and try to make sure it does not break silently again (#7041) * Do not build x64 DRC backend when C backend is forced * New CI target (mametiny + kinst) * Switch travis to CI target * Switch appveyor to CI target
2020-08-12 18:54:22 +02:00
- \projects\mame\mameci64.exe -validate
Add gcc build to appveyor (#5654) * Add gcc build to appveyor As tea-ci has been broken for quite a while now there has been no MINGW CI available. MINGW builds can be done in appveyor too. Tools build had to be disabled as it takes longer than the allowed 60 minutes. Wa,-mbig-obj was added to avoid "file too big" errors. * Align appveyor gcc build configuration with travis This will hopefully make the build fast enough not to miss the 60 minute maximum build time * Turns out non-debug build needs -mbig-obj too
2019-09-17 21:41:44 +02:00
after_test:
Fix non-x86 build and try to make sure it does not break silently again (#7041) * Do not build x64 DRC backend when C backend is forced * New CI target (mametiny + kinst) * Switch travis to CI target * Switch appveyor to CI target
2020-08-12 18:54:22 +02:00
- 7z a mameci64-appveyor-%APPVEYOR_REPO_BRANCH%-%APPVEYOR_REPO_COMMIT%-%APPVEYOR_BUILD_NUMBER%.7z %APPVEYOR_BUILD_FOLDER%\*.exe %APPVEYOR_BUILD_FOLDER%\artwork %APPVEYOR_BUILD_FOLDER%\bgfx %APPVEYOR_BUILD_FOLDER%\ctrlr %APPVEYOR_BUILD_FOLDER%\docs %APPVEYOR_BUILD_FOLDER%\hash %APPVEYOR_BUILD_FOLDER%\hlsl %APPVEYOR_BUILD_FOLDER%\ini %APPVEYOR_BUILD_FOLDER%\language %APPVEYOR_BUILD_FOLDER%\nl_examples %APPVEYOR_BUILD_FOLDER%\plugins %APPVEYOR_BUILD_FOLDER%\roms %APPVEYOR_BUILD_FOLDER%\samples
- appveyor PushArtifact mameci64-appveyor-%APPVEYOR_REPO_BRANCH%-%APPVEYOR_REPO_COMMIT%-%APPVEYOR_BUILD_NUMBER%.7z
Add gcc build to appveyor (#5654) * Add gcc build to appveyor As tea-ci has been broken for quite a while now there has been no MINGW CI available. MINGW builds can be done in appveyor too. Tools build had to be disabled as it takes longer than the allowed 60 minutes. Wa,-mbig-obj was added to avoid "file too big" errors. * Align appveyor gcc build configuration with travis This will hopefully make the build fast enough not to miss the 60 minute maximum build time * Turns out non-debug build needs -mbig-obj too
2019-09-17 21:41:44 +02:00
Added AppVeyor config
2018-06-03 20:37:26 +02:00
test_script:
Fix non-x86 build and try to make sure it does not break silently again (#7041) * Do not build x64 DRC backend when C backend is forced * New CI target (mametiny + kinst) * Switch travis to CI target * Switch appveyor to CI target
2020-08-12 18:54:22 +02:00
- \projects\mame\mameci64d.exe -validate
Added AppVeyor config
2018-06-03 20:37:26 +02:00
after_test:
Fix non-x86 build and try to make sure it does not break silently again (#7041) * Do not build x64 DRC backend when C backend is forced * New CI target (mametiny + kinst) * Switch travis to CI target * Switch appveyor to CI target
2020-08-12 18:54:22 +02:00
- 7z a mameci64d-appveyor-%APPVEYOR_REPO_BRANCH%-%APPVEYOR_REPO_COMMIT%-%APPVEYOR_BUILD_NUMBER%.7z %APPVEYOR_BUILD_FOLDER%\*.exe %APPVEYOR_BUILD_FOLDER%\artwork %APPVEYOR_BUILD_FOLDER%\bgfx %APPVEYOR_BUILD_FOLDER%\ctrlr %APPVEYOR_BUILD_FOLDER%\docs %APPVEYOR_BUILD_FOLDER%\hash %APPVEYOR_BUILD_FOLDER%\hlsl %APPVEYOR_BUILD_FOLDER%\ini %APPVEYOR_BUILD_FOLDER%\language %APPVEYOR_BUILD_FOLDER%\nl_examples %APPVEYOR_BUILD_FOLDER%\plugins %APPVEYOR_BUILD_FOLDER%\roms %APPVEYOR_BUILD_FOLDER%\samples
- appveyor PushArtifact mameci64d-appveyor-%APPVEYOR_REPO_BRANCH%-%APPVEYOR_REPO_COMMIT%-%APPVEYOR_BUILD_NUMBER%.7z
Reference in a new issue Copy permalink