https://github.com/imageworks/OpenColorIO/pull/187 This is mostly about the JNI Java interface, you need to run cmake with (-D OCIO_BUILD_JNIGLUE=TRUE) for the binding to be built. Their is no install

Will do - I'll try and get everything humming along on Windows too, at least with the core tools. I'm hoping I'll have a few days this coming week to tackle this. cheers

I'm not sure you can assume tr1 on Windows. It first showed up in VS2008 SP1, but some people (including us) aren't using SP1, for compatibility reasons with certain runtimes. However, if you need tr1

Oh - one other dependency consideration I forgot is our use of an external shared_ptr header. Currently the default is to look for tr1, and if it's not enabled you can optionally specify boost. What

On the RPM side (including Suse and other RPM systems), it's easy. The spec file supports a %check section and a failure in this area (non-zero exit) will fail the build. I'm sure Debian based

So i've learned a lot about packaging these last few days! Who knew there was so much to it? ;) For those who want to come up to speed as well, these links are great places to

Also worth mentioning... Although Toshio (from Fedora devel list) thought it was strange for the python library to serve a dual purpose, he agreed that the most appropriate action was to put the

<malcolmh...@...> wrote: Usually it's the packagers job to decide on how to break up the packages as the guidelines differ somewhat between distros, but documented suggestions are very

Off list Jeremy, Colin and myself were chatting about this when talking about the windows build. .... We need to have a consensus on how the project will be split up into packages (ie different sets

Placeholder for continued discussion from: https://github.com/imageworks/OpenColorIO/pull/183

https://github.com/imageworks/OpenColorIO/pull/183

I did start to play around with using cpack for this to create the relevant installers (rpm, deb, tar, exe etc..) I should have some free time to get around to cleaning this up and committing

Awesome! And now that I have a Windows machine available, once we get the process sorted out I'm happy to post pre-built installers (mac, windows, linux?) for each dot release. --

Hi there - If no one else beats me to it I'll try to put together a fork of the project that should work out of the box on Windows together in the next week or two along with some pre-built binaries

Hi guys! Just want to second that some more windows-friendly documentation/ precompiles would really be appreciated. Not very experienced in this, but I`m trying to compile thru cygwin and I am almost

Yes, 1.0.1. 1.) I saw errors that patch is not a recognized program. (As Colin mentioned I downloaded cygwin and put it on the path). 2.) Finding the OCIO_USE_BOOST_PTR Cmake setting cleared out

This works like a charm now! Thanks, Jordan

As far as I know, Windows should be building right out of the box. I presume you're using 1.0.X, correct? Colin's email you cite below is from May. In August, the Foundry committed 2 changes should

Hi all, I'm resurrecting this thread to see about the current state of building OCIO for Windows. I was able to get Cmake to generate a VS 2008 solution, but it isn't compiling. Colin's list of fixes

I've just rolled this patch into master. Jordan / dbr, please let me know if you encounter any further issues on Lion. -- Jeremy