Closed GoogleFrog closed 6 years ago
104.0.1-527-gf2536df++ compiled with gcc 5.4 (and probably new ABI). Current stable 104.0.1-287-gf7b0fcc was compiled with gcc 4.8 and old ABI. Have to update and test build-VMs for linux32, linux64, win32, win64.
Attempt to start CircuitAI-gcc-7.3.1 with 104.0.1-527-gf2536df-gcc-5.4 (new ABI) failed at init phase. CircuitAI and 104.0.1-541-g637eb5094 compiled with gcc-7.3.1 - works (apart from lua crash). So it's about using same gcc as official engine's buildbot, atm that is gcc 5.4
Made linux64 and win32 build-VMs, linux32 whouldn't be an issue either, but win64 fails with errors inside stl files (did i forgot to update mingwlibs64?), also the last available win64 engine build is 104.0.1-430-g4bab20282 (same issue?)
Abusing spring's buildbot, binary is bundled with spring now: https://github.com/spring/spring/commit/ce929ecc68726d7cd54a184712eaf9fad0573be1
To better handle circuit updates I think we need to package a dev version of circuit in chobby. This would be the latest build and would also be built for the latest engine. Most of the work would be chobby-side. This ticket is mostly to put forth the idea.