interesting
/
libui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
libui/azure-pipelines.yml

379 lines
12 KiB
YAML
Raw Permalink Normal View History

Added codedate to azure-pipelines.yml.
2019-03-31 22:45:53 -05:00
# 31 march 2019
Set up CI with Azure Pipelines [skip ci]
2019-03-31 22:38:39 -05:00
And set up tagging and GitHub releases. That'll be all for the Azure Pipelines configuration; now we just need the AppVeyor configuration.
2019-04-07 16:47:30 -05:00
trigger:
branches:
include:
- '*'
tags:
include:
- '*'
Split the example names into a variable and echoed the commands for archiving so I can make sure everything is right.
2019-04-05 23:46:18 -05:00
variables:
Split the Linux artifact rules into a template and try them on macOS and static builds too.
2019-04-06 18:26:35 -05:00
releaseExamples: 'controlgallery cpp-multithread datetime drawtext histogram tester timer'
Split the example names into a variable and echoed the commands for archiving so I can make sure everything is right.
2019-04-05 23:46:18 -05:00
Wrong backup
2019-04-07 16:22:10 -05:00
jobs:
# linux {
- job: linux_386_shared
displayName: 'Linux 386 Shared'
pool:
Okay, so it seems I can't insert template names as matrix fields, and I'd rather not have a bunch of tiny jobs for all these different templates. So forget it for now.
2019-04-07 16:20:52 -05:00
vmImage: 'ubuntu-16.04'
Wrong backup
2019-04-07 16:22:10 -05:00
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
- template: azure-pipelines/linux-386-install-gtk-dev.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: export CFLAGS=-m32 CXXFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig
defaultLibrary: shared
- template: azure-pipelines/build.yml
- template: azure-pipelines/artifacts.yml
parameters:
os: linux
arch: 386
libtype: shared
libfiles: libui.so.0
osHeader: ui_unix.h
Merged all the files back together.
2019-04-07 15:11:59 -05:00
Wrong backup
2019-04-07 16:22:10 -05:00
- job: linux_386_static
displayName: 'Linux 386 Static'
pool:
vmImage: 'ubuntu-16.04'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
- template: azure-pipelines/linux-386-install-gtk-dev.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: export CFLAGS=-m32 CXXFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig
defaultLibrary: static
- template: azure-pipelines/build.yml
- template: azure-pipelines/artifacts.yml
parameters:
os: linux
arch: 386
libtype: static
libfiles: libui.a
osHeader: ui_unix.h
- job: linux_amd64_shared
displayName: 'Linux amd64 Shared'
pool:
vmImage: 'ubuntu-16.04'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
- template: azure-pipelines/linux-install-gtk-dev.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/configure.yml
parameters:
defaultLibrary: shared
- template: azure-pipelines/build.yml
- template: azure-pipelines/artifacts.yml
parameters:
os: linux
arch: amd64
libtype: shared
libfiles: libui.so.0
osHeader: ui_unix.h
- job: linux_amd64_static
displayName: 'Linux amd64 Static'
pool:
vmImage: 'ubuntu-16.04'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
- template: azure-pipelines/linux-install-gtk-dev.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/configure.yml
parameters:
defaultLibrary: static
- template: azure-pipelines/build.yml
- template: azure-pipelines/artifacts.yml
parameters:
os: linux
arch: amd64
libtype: static
libfiles: libui.a
osHeader: ui_unix.h
# }
# windows vs2015 {
- job: windows_386_msvc2015_shared
displayName: 'Windows 386 MSVC2015 Shared'
pool:
vmImage: 'vs2015-win2012r2'
workspace:
clean: all
steps:
- template: azure-pipelines/vs2015-install-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86
defaultLibrary: shared
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: 386
toolchain: msvc2015
libtype: shared
libfiles: libui.dll libui.exp libui.lib
osHeader: ui_windows.h
- job: windows_386_msvc2015_static
displayName: 'Windows 386 MSVC2015 Static'
Okay, so it seems I can't insert template names as matrix fields, and I'd rather not have a bunch of tiny jobs for all these different templates. So forget it for now.
2019-04-07 16:20:52 -05:00
pool:
Wrong backup
2019-04-07 16:22:10 -05:00
vmImage: 'vs2015-win2012r2'
Okay, so it seems I can't insert template names as matrix fields, and I'd rather not have a bunch of tiny jobs for all these different templates. So forget it for now.
2019-04-07 16:20:52 -05:00
workspace:
clean: all
steps:
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/vs2015-install-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
Okay, so it seems I can't insert template names as matrix fields, and I'd rather not have a bunch of tiny jobs for all these different templates. So forget it for now.
2019-04-07 16:20:52 -05:00
- template: azure-pipelines/configure.yml
Wrong backup
2019-04-07 16:22:10 -05:00
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86
defaultLibrary: static
Okay, so it seems I can't insert template names as matrix fields, and I'd rather not have a bunch of tiny jobs for all these different templates. So forget it for now.
2019-04-07 16:20:52 -05:00
- template: azure-pipelines/build.yml
parameters:
Wrong backup
2019-04-07 16:22:10 -05:00
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86
afterBuild: ren build\meson-out\libui.a libui.lib
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: 386
toolchain: msvc2015
libtype: static
libfiles: libui.lib
osHeader: ui_windows.h
- job: windows_amd64_msvc2015_shared
displayName: 'Windows amd64 MSVC2015 Shared'
pool:
vmImage: 'vs2015-win2012r2'
workspace:
clean: all
steps:
- template: azure-pipelines/vs2015-install-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
defaultLibrary: shared
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: amd64
toolchain: msvc2015
libtype: shared
libfiles: libui.dll libui.exp libui.lib
osHeader: ui_windows.h
- job: windows_amd64_msvc2015_static
displayName: 'Windows amd64 MSVC2015 Static'
pool:
vmImage: 'vs2015-win2012r2'
workspace:
clean: all
steps:
- template: azure-pipelines/vs2015-install-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
defaultLibrary: static
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
afterBuild: ren build\meson-out\libui.a libui.lib
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: amd64
toolchain: msvc2015
libtype: static
libfiles: libui.lib
osHeader: ui_windows.h
# }
# windows vs2017 {
- job: windows_386_msvc2017_shared
displayName: 'Windows 386 MSVC2017 Shared'
pool:
vmImage: 'vs2017-win2016'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86
defaultLibrary: shared
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: 386
toolchain: msvc2017
libtype: shared
libfiles: libui.dll libui.exp libui.lib
osHeader: ui_windows.h
- job: windows_386_msvc2017_static
displayName: 'Windows 386 MSVC2017 Static'
pool:
vmImage: 'vs2017-win2016'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86
defaultLibrary: static
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86
afterBuild: ren build\meson-out\libui.a libui.lib
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: 386
toolchain: msvc2017
libtype: static
libfiles: libui.lib
osHeader: ui_windows.h
- job: windows_amd64_msvc2017_shared
displayName: 'Windows amd64 MSVC2017 Shared'
pool:
vmImage: 'vs2017-win2016'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" amd64
defaultLibrary: shared
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" amd64
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: amd64
toolchain: msvc2017
libtype: shared
libfiles: libui.dll libui.exp libui.lib
osHeader: ui_windows.h
- job: windows_amd64_msvc2017_static
displayName: 'Windows amd64 MSVC2017 Static'
pool:
vmImage: 'vs2017-win2016'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/windows-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
beforeConfigure: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" amd64
defaultLibrary: static
- template: azure-pipelines/build.yml
parameters:
beforeBuild: call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" amd64
afterBuild: ren build\meson-out\libui.a libui.lib
- template: azure-pipelines/windows-artifacts.yml
parameters:
os: windows
arch: amd64
toolchain: msvc2017
libtype: static
libfiles: libui.lib
osHeader: ui_windows.h
# }
# mac {
# TODO beforeConfigure/beforeBuild: export SDKROOT=$(xcodebuild -version -sdk macosx10.13 Path)?
- job: darwin_amd64_shared
displayName: 'Darwin amd64 Shared'
pool:
vmImage: 'macos-10.13'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/darwin-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
defaultLibrary: shared
- template: azure-pipelines/build.yml
- template: azure-pipelines/artifacts.yml
parameters:
os: darwin
arch: amd64
libtype: shared
libfiles: libui.A.dylib
osHeader: ui_darwin.h
- job: darwin_amd64_static
displayName: 'Darwin amd64 Static'
pool:
vmImage: 'macos-10.13'
workspace:
clean: all
steps:
- template: azure-pipelines/setup-python3.yml
Looks like meson now requires a newer ninja than what ships with whatever version of whatever Debian-derived distribution Azure Pipelines uses. Use ninja from pip instead (it's a special distribution maintained by the SciPy guys, apparently).
2020-06-07 20:05:16 -05:00
- template: azure-pipelines/install-latest-meson-ninja.yml
Wrong backup
2019-04-07 16:22:10 -05:00
- template: azure-pipelines/darwin-install-ninja.yml
- template: azure-pipelines/configure.yml
parameters:
defaultLibrary: static
- template: azure-pipelines/build.yml
- template: azure-pipelines/artifacts.yml
Okay, so it seems I can't insert template names as matrix fields, and I'd rather not have a bunch of tiny jobs for all these different templates. So forget it for now.
2019-04-07 16:20:52 -05:00
parameters:
Wrong backup
2019-04-07 16:22:10 -05:00
os: darwin
arch: amd64
libtype: static
libfiles: libui.a
osHeader: ui_darwin.h
Merged all the files back together.
2019-04-07 15:11:59 -05:00
Wrong backup
2019-04-07 16:22:10 -05:00
# }