What you have to understand is that I'm not a Windows programmer (not since the 80's and early 90's, when I guess it would be more proper to call me an MSDOS programmer), and I neither own a Windows-running machine nor even have access to one. I'm not saying this with any sense of superiority, it simply is a fact, like saying I don't speak French.
Setting up Appveyor was an arduous process of remote control trial and error -- fail a build, make a change, come back again in 30 minutes and see if the new appveyor build made it any farther. It was probably on the order of a couple hundred failed builds before I got something close to a full build working on Appveyor. I started with a minimal build and minimal dependencies, and tried to widen it bit by bit, but at some point I had gotten all the dependencies working that I could figure out, and didn't know where to begin or how to proceed on the others, and had to move on to other things. OCIO, FFMPEG, and probably several others are not left out intentionally. I would love for the appveyor build to successfully install all dependencies, so that every last bit of OIIO gets built and tested and none is excluded for lack of dependencies. For that matter, even the dependencies I managed to cobble together are, I assume, done so in baroque, inefficient, ugly ways that would horrify an experienced Windows developer. As a novice, I've taken it about as far as I can myself given my lack of time and expertise. I would welcome submissions from more knowledgable people of fixes to the appveyor.yml file, up to and including a complete rewrite. The great thing about having a really elegant, fully working appveyor.yml would be that it would serve as a recipe for anybody else needing to set up all the dependencies and do a full build and test. > On Oct 8, 2016, at 4:49 PM, [email protected] wrote: > > > Hi Larry ! > > First of all thanks for all the hard work on 1.7. I’m trying to get RB-1.7 > compiled for Windows and instead of spending weeks on it I decided to make > use of the YAML file you provided with this release. > > I was able to successfully compile the RB-1.7 branch using AppVeyor (the > build seems to work minus a few warning messages) I noticed however that you > commented out the OpenColorIO (and FFMPEG) lines in the YML file and I was > wondering if it was done because OCIO and FFMPEG aren’t working yet or if you > commented it out to make it an optional dependence. > > I “un-commented” the OpenImageIO and FFMPEG lines and the build failed so I’m > assuming it’s not ready yet. > Getting OCIO and FFMPEG to work in there would be awesome since it would make > building OIIO fairly painless. > > Do you know if anybody got OCIO and FFMPEG to work using the YAML file ? > Thanks ! > > Renaud > > _______________________________________________ > 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]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
