The appveyor script could stand to have sooooo many improvements. I cobbled it together by trial and error, with nothing to go on but trying things, pushing, and then revising when I saw what broke. I didn't even possess a local Windows machine to try builds on, it was appveyor only. And my assembly of dependencies is super ad-hoc. Also, I think the script currently only ensures that the build completes, but doesn't run the testsuite.
Any and all love given to the appveyor script from somebody who actually knows Windows development would be greatly appreciated. It would be phenomenal if it could publish the binaries of major releases. > On Feb 24, 2017, at 10:41 AM, Steven Caron <[email protected]> wrote: > > Just throwing it out there but we should be able to improve the Appveyor CI > to actually publish the result of the build ('artifacts') to GitHub. Do this > only for certain tags/releases and not for every commit and then have an > official location for at least the primary supported complier on Windows. > > On Fri, Feb 24, 2017 at 10:06 AM, Larry Gritz <[email protected] > <mailto:[email protected]>> wrote: > I think even more recent versions can be found here: > > https://svn.blender.org/svnroot/bf-blender/trunk/lib/ > <https://svn.blender.org/svnroot/bf-blender/trunk/lib/> > > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
