If I can get approval from our legal dept, I’m more than happy to share the mods I’ve made to get the project buildable. Part of that was also making a large number of fixes to the test suites in order to run on windows.
I largely based our build from the blender site someone posted, but still had to make a few modifications here and there to get everything working. For simplicity sake, we mainly build statically, but link to the msvc shared runtimes. One thing to note about Python: - Python 2.x on windows is bound to VS2008. If you want to build that for a target, I think you’ll be limited to the last pre-Cpp11 version (which I think is 1.17) From: Oiio-dev [mailto:[email protected]] On Behalf Of Steven Caron Sent: Friday, February 24, 2017 11:09 AM To: OpenImageIO developers <[email protected]> Subject: Re: [Oiio-dev] Building on Windows Exactly, it just makes sense to take everyone's 'build notes' and actually turn them in something that BUILDS. I have experience like yours with Appveyor with OpenVDB. So I might not be the best to help either... On Fri, Feb 24, 2017 at 10:46 AM, Larry Gritz <[email protected]<mailto:[email protected]>> wrote: 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]<mailto:[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]<mailto:[email protected]> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org<http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> -- Larry Gritz [email protected]<mailto:[email protected]> _______________________________________________ Oiio-dev mailing list [email protected]<mailto:[email protected]> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org<http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
