Commit Graph

18 Commits

Author SHA1 Message Date
Julian Sikorski
65b0df8761
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 12:54:22 -04:00
Julian Sikorski
2d1bf3ed5c 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-30 17:11:15 +02:00
Julian Sikorski
4b4016110a
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 17:20:29 -04:00
Julian Sikorski
ab45b2dba4
Switch appveyor GCC build to -O3 (issue 6804) (#6987) 2020-07-23 12:20:46 -04:00
Julian Sikorski
93a1cde67d 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 10:30:48 -04:00
Julian Sikorski
ed2b7e5ef1 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 09:30:18 -04:00
Patrick Mackinlay
9d4b7b02ac
another try (nw) 2019-09-26 13:58:19 +07:00
Patrick Mackinlay
7476957f69
try another way (nw) 2019-09-26 13:38:59 +07:00
Patrick Mackinlay
75ef4119f8
doh (nw) 2019-09-26 13:12:29 +07:00
Patrick Mackinlay
b3e3fd9b97
appveyor: and again (nw) 2019-09-26 13:08:11 +07:00
Patrick Mackinlay
d79b2fcf30
try again (nw) 2019-09-26 12:39:28 +07:00
Patrick Mackinlay
88dd01b95d
appveyor: try this (nw) 2019-09-26 12:17:36 +07:00
Patrick Mackinlay
6f0e4362e6
appveyor: let's try vs2019 16.3.0 (nw) 2019-09-26 10:44:36 +07:00
Julian Sikorski
461fb82524 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 15:41:44 -04:00
Patrick Mackinlay
0e75c994b8 appveyor: might as well (nw) 2018-12-20 12:57:02 +07:00
Patrick Mackinlay
0ac5f76c95 appveyor: another one (nw) 2018-11-23 17:00:24 +07:00
Patrick Mackinlay
f997feb4b9 appveyor: experiment (nw) 2018-11-23 16:38:58 +07:00
balr0g
832ba8b8b2 Rename appveyor.yml 2018-07-07 14:22:59 -04:00