miniupnp/appveyor.yml

environment:
  APP_VERSION: '2.1'


version: '$(APP_VERSION).{build}'

image: Visual Studio 2017

install:
  - set PATH=%PATH%;C:\msys64\mingw32\bin

build_script:
  - cd miniupnpc
  - appveyor AddCompilationMessage "Building miniupnpc"
  - mingw32-make -f Makefile.mingw
  - mingw32-make -f Makefile.mingw pythonmodule PYTHON=C:\Python37\python

after_build:
  - 7z a ..\miniupnpc-%APPVEYOR_BUILD_VERSION%.zip *.exe *.dll *.a *.lib

artifacts:
  - path: miniupnpc-$(appveyor_build_version).zip
    name: miniupnpc binaries
  - path: miniupnpc/dist/miniupnpc-$(APP_VERSION)-py3.7-win32.egg
    name: miniupnpc python module
Changed appveyor.yml to deliver only egg for python module on windows. 2019-04-25 14:51:47 +00:00			`environment:`
			`APP_VERSION: '2.1'`


			`version: '$(APP_VERSION).{build}'`
appveyor: version 2018-04-30 14:35:07 +00:00
Attempt to have a working build for Python 3.7 under windows with appveyor. - Python 3.7 is built using Visual Studio 2017 so we use the corresponding image. - Python 3.7 replaces Python 2.7 when building the module. - Adding the library legacy_stdio_definitions to the linker input as starting with VS 2015 some symbols have been inlined but may be expected by older binaries. This compatibility library exposes these symbols so they can be dynamically linked when required (Cf. https://stackoverflow.com/a/32418900). 2019-04-25 13:27:44 +00:00			`image: Visual Studio 2017`

add MinGW to %PATH% 2015-09-15 21:58:11 +00:00			`install:`
Fix appveyor builds 2016-07-31 03:03:48 +00:00			`- set PATH=%PATH%;C:\msys64\mingw32\bin`
add MinGW to %PATH% 2015-09-15 21:58:11 +00:00
adding appveyor.yml 2015-09-15 21:48:14 +00:00			`build_script:`
Fix appveyor builds 2016-07-31 03:03:48 +00:00			`- cd miniupnpc`
appveyor: message 2018-04-26 20:49:06 +00:00			`- appveyor AddCompilationMessage "Building miniupnpc"`
Fix appveyor builds 2016-07-31 03:03:48 +00:00			`- mingw32-make -f Makefile.mingw`
Attempt to have a working build for Python 3.7 under windows with appveyor. - Python 3.7 is built using Visual Studio 2017 so we use the corresponding image. - Python 3.7 replaces Python 2.7 when building the module. - Adding the library legacy_stdio_definitions to the linker input as starting with VS 2015 some symbols have been inlined but may be expected by older binaries. This compatibility library exposes these symbols so they can be dynamically linked when required (Cf. https://stackoverflow.com/a/32418900). 2019-04-25 13:27:44 +00:00			`- mingw32-make -f Makefile.mingw pythonmodule PYTHON=C:\Python37\python`
appveyor: push artifacts 2018-04-26 20:35:32 +00:00
			`after_build:`
test2 2018-04-30 14:39:28 +00:00			`- 7z a ..\miniupnpc-%APPVEYOR_BUILD_VERSION%.zip .exe .dll .a .lib`
appveyor: push artifacts 2018-04-26 20:35:32 +00:00
			`artifacts:`
appveyor: version 2018-04-30 14:35:07 +00:00			`- path: miniupnpc-$(appveyor_build_version).zip`
appveyor: push artifacts 2018-04-26 20:35:32 +00:00			`name: miniupnpc binaries`
Changed appveyor.yml to deliver only egg for python module on windows. 2019-04-25 14:51:47 +00:00			`- path: miniupnpc/dist/miniupnpc-$(APP_VERSION)-py3.7-win32.egg`
appveyor: push artifacts 2018-04-26 20:35:32 +00:00			`name: miniupnpc python module`