Hey there, I was going for windows here too recently and gave up after a while. I would prefer if we could have a joint effort to create proper build setups for the dependencies. Some come with CMake setups already and are easy targets. Quite some don't and it's even kind of obscure for some to be found due to weird windows port naming differences and whatnot.
The reason i would prefer that way is that chances are the compiler chosen for the binary dependencies don't match what i need and i have to recompile anyways and even more so now that i actually maintain different versions (runtime versions vs. architecture vs. python version etc.) of most things i compile i would prefer not having to set that all up manually but simply rebuild as needed. Here's a list of the ones i managed to get built rather straight forward (the first version being the one in the externals, the second the one i built). glew 1.5.1 1.13.0 ilmbase 1.0.1 2.2.0 openexr 1.6.1 2.2.0 libpng 1.2.3 1.6.23 zlib 1.2.3 1.2.8 tbb tbb21_200090511oss tbb44_20160526oss And here's the ones i am seeing issues with: * gtest (1.3.0) * jasper (1.900.1) * jpeg (6b) * openjpg (1.3) * tiff (3.8.2)? I wonder what the best way to tackle would be? On my end i am wrapping them all as rez packages, but that is hardly something to be useful to everyone. I am thinking standard cmake setups + rez wrappers as an additional repo, so one could also build without rez easily. Cheers, Thorsten ________________________________________ --- Thorsten Kaufmann Production Pipeline Architect Mackevision Medien Design GmbH Forststraße 7 70174 Stuttgart T +49 711 93 30 48 661 F +49 711 93 30 48 90 M +49 151 19 55 55 02 [email protected] www.mackevision.com<http://www.mackevision.com/?utm_source=E-Mail-Signatur&utm_medium=E-Mail&utm_campaign=Mackevision-Link> Geschäftsführer: Armin Pohl, Joachim Lincke, Jens Pohl --- NEW PRODUCT: Innovation in moving images - Motionbox<http://www.mackevision.com/motionbox/?utm_source=E-Mail-Signatur&utm_medium=E-Mail&utm_campaign=Motionbox-Signatur> VFX: Game of Thrones, Season 5 - VFX making of reel<http://www.mackevision.com/references/got-5-making-of/?utm_source=E-Mail-Signatur&utm_medium=E-Mail&utm_campaign=GoT-S5-making-of-Signatur>. SOCIAL: Follow us on Facebook<https://www.facebook.com/mackevision.global>, Twitter<https://twitter.com/Mackevision>, Behance<https://www.behance.net/mackevision> and Vimeo<https://vimeo.com/mackevision> HRB 243735 Amtsgericht Stuttgart Von: Oiio-dev <[email protected]> im Auftrag von Ben De Luca <[email protected]> Gesendet: Montag, 15. August 2016 19:27 An: OpenImageIO developers Betreff: Re: [Oiio-dev] Windows build instructions? I see the openEXR version, is very old in the external libs, but that the windows build is compiling from link in docs. I wondered if you might share? -Ben On 15 August 2016 at 20:05, Ben De Luca <[email protected]> wrote: > Hi, > I was reading the documentation here, > https://sites.google.com/site/openimageio/building-oiio-on-windows > which is linked from the main site. Which seems to be pretty different > than whats in the repo install instructions. > > In the repo it says look for latest windows build instructions in the > wiki, but that page > (http://openimageio.org/wiki/index.php?title=Building_OpenImageIO_on_Windows) > doesn't exist. > > In the notes, it says that the external project should be a sibling of > the trunk, but step 8 says some thing about setting > THIRD_PARTY_TOOLS_HOME, I looked in the cmake on master and there are > references lock files that don't appear to be in the external tools > windows zip. > > steps 5 and 6 seem to refer to the same thing, downloading boost but > the link to boost pro is dead now http://www.boostpro.com/download . _______________________________________________ Oiio-dev mailing list [email protected] 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
