Am Donnerstag, den 26.10.2017, 13:55 +0900 schrieb Jose Fonseca: > > > If there's doubt, I suggest testing Visual Studio with AppVeyor by > pushing the changes as a feature branch to FDO's git -- I believe > that should trigger an AppVeyor build. (Push to a github repos > hooked into Appveyor, depending on what people are more confortable > with.)
Since I have AppVeyor set up, I tested it, but I applied only this patch (the series didn't apply on top of 16cfbef44cf0b1969). The build fails though, I guess since the setup is with MSVC 2013. I'll happily trigger another build, if someone points me to an AppVeyor file that uses a later version of MSVC (that would probably require LLVM build with that other version). Build log: https://ci.appveyor.com/project/gerddie/mesa/build/65 lp_context.c c:\projects\mesa\include\c11\threads_win32.h(151) : error C2037: left of 'tv_sec' specifies undefined struct/union 'timespec' c:\projects\mesa\include\c11\threads_win32.h(151) : error C2037: left of 'tv_nsec' specifies undefined struct/union 'timespec' c:\projects\mesa\include\c11\threads_win32.h(151) : warning C4033: 'impl_timespec2msec' must return a value c:\projects\mesa\include\c11\threads_win32.h(389) : error C2065: 'ts' : undeclared identifier c:\projects\mesa\include\c11\threads_win32.h(389) : warning C4047: 'function' : 'const timespec *' differs in levels of indirection from 'int' c:\projects\mesa\include\c11\threads_win32.h(389) : Best, Gert _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
