|
Re: OCIO 1.0.9 released
Not sure why distribute was added. I'm very comfortable switching
back if we believe it to be appropriate.
-- Jeremy
Not sure why distribute was added. I'm very comfortable switching
back if we believe it to be appropriate.
-- Jeremy
|
By
Jeremy Selan <jeremy...@...>
·
#1240
·
|
|
Re: OCIO 1.0.9 released
On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote:
Yah, I'm seeing that too. Looks like the docs build target is hosed
for 1.0.9; looking into it...
Can you confirm that everything
On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote:
Yah, I'm seeing that too. Looks like the docs build target is hosed
for 1.0.9; looking into it...
Can you confirm that everything
|
By
Richard Shaw <hobbe...@...>
·
#1241
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
Hi!
Just tested and added a link to buildlog in #318 issue.
Hope it helps, somehow.
Cheers.
--
Matteo F. Vescovi
Debian Maintainer
GnuPG KeyID: 0x83B2CF7A
Hi!
Just tested and added a link to buildlog in #318 issue.
Hope it helps, somehow.
Cheers.
--
Matteo F. Vescovi
Debian Maintainer
GnuPG KeyID: 0x83B2CF7A
|
By
"Matteo F. Vescovi" <mfv.d...@...>
·
#1239
·
|
|
Re: OCIO 1.0.9 released
On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote:
> 2. I got an error here:
> Building CXX object
> src/core_tests/CMakeFiles/ocio_core_tests.dir/__/core/GroupTransform.cpp.o
> --
On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote:
> 2. I got an error here:
> Building CXX object
> src/core_tests/CMakeFiles/ocio_core_tests.dir/__/core/GroupTransform.cpp.o
> --
|
By
Richard Shaw <hobbe...@...>
·
#1236
·
|
|
Re: OCIO 1.0.9 released
On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote:
> Ok, a couple of observations when trying to build for Fedora 19 x86_64
>
> 1. I was using the pull 300 patch which is still
On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote:
> Ok, a couple of observations when trying to build for Fedora 19 x86_64
>
> 1. I was using the pull 300 patch which is still
|
By
Richard Shaw <hobbe...@...>
·
#1235
·
|
|
Re: OCIO 1.0.9 released
Can you clarify what you mean by this? I'm not sure what the "pull 300
patch" refers to.
Yah, I'm seeing that too. Looks like the docs build target is hosed
for 1.0.9; looking into it...
Can you
Can you clarify what you mean by this? I'm not sure what the "pull 300
patch" refers to.
Yah, I'm seeing that too. Looks like the docs build target is hosed
for 1.0.9; looking into it...
Can you
|
By
Jeremy Selan <jeremy...@...>
·
#1232
·
|
|
Re: OCIO 1.0.9 released
Ok, a couple of observations when trying to build for Fedora 19 x86_64
1. I was using the pull 300 patch which is still open. It looks like parts of it were committed, but not all of it. I don't think
Ok, a couple of observations when trying to build for Fedora 19 x86_64
1. I was using the pull 300 patch which is still open. It looks like parts of it were committed, but not all of it. I don't think
|
By
Richard Shaw <hobbe...@...>
·
#1234
·
|
|
Re: OCIO 1.0.9 released
https://github.com/imageworks/OpenColorIO/tree/v1.0.9
Will send a link from now on! :)
(Docs are in the process of rebuilding, the website will be updated
momentarily).
https://github.com/imageworks/OpenColorIO/tree/v1.0.9
Will send a link from now on! :)
(Docs are in the process of rebuilding, the website will be updated
momentarily).
|
By
Jeremy Selan <jeremy...@...>
·
#1231
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
Hi again!
By
"Matteo F. Vescovi" <mfv.d...@...>
·
#1238
·
|
|
Re: OCIO 1.0.9 released
Guess I got there too quick, don't see it yet on github...
Also, although it's not difficult to find a link would be handy :)
Thanks,
Richard
Guess I got there too quick, don't see it yet on github...
Also, although it's not difficult to find a link would be handy :)
Thanks,
Richard
|
By
Richard Shaw <hobbe...@...>
·
#1233
·
|
|
OCIO 1.0.9 released
I've just tagged the latest OCIO master as 1.0.9. There had been a
bunch of bugfixes in there, and it had been hurting our distros to not
have a tagged release with the lates.
-- Jeremy
**Version
I've just tagged the latest OCIO master as 1.0.9. There had been a
bunch of bugfixes in there, and it had been hurting our distros to not
have a tagged release with the lates.
-- Jeremy
**Version
|
By
Jeremy Selan <jeremy...@...>
·
#1230
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
We've just put out the 1.0.9 tag. Please see if this fixes things?
We've just put out the 1.0.9 tag. Please see if this fixes things?
|
By
Jeremy Selan <jeremy...@...>
·
#1229
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
Oh - on further inspection I see you're compiling against yaml 0.5.1
This is a known issue, being tracked here:
https://github.com/imageworks/OpenColorIO/issues/318
-- Jeremy
<mfv.d...@...>
Oh - on further inspection I see you're compiling against yaml 0.5.1
This is a known issue, being tracked here:
https://github.com/imageworks/OpenColorIO/issues/318
-- Jeremy
<mfv.d...@...>
|
By
Jeremy Selan <jeremy...@...>
·
#1228
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
Hi!
Good to know ;-)
Well... I can test it, obviously ;-P
Gonna let you know the results of the build with that parameter set.
Thanks for your help.
Cheers.
--
Matteo F. Vescovi
Debian
Hi!
Good to know ;-)
Well... I can test it, obviously ;-P
Gonna let you know the results of the build with that parameter set.
Thanks for your help.
Cheers.
--
Matteo F. Vescovi
Debian
|
By
"Matteo F. Vescovi" <mfv.d...@...>
·
#1237
·
|
|
Re: Review: Nuke: OCIODisplay now has an implemented GPU path
Awesome, thanks Sean!
Does anyone on this list have experience working with the Nuke GPU
path? This API is new to us, and we'd love to get some experienced
eyes on this code. :)
-- Jeremy
Awesome, thanks Sean!
Does anyone on this list have experience working with the Nuke GPU
path? This API is new to us, and we'd love to get some experienced
eyes on this code. :)
-- Jeremy
|
By
Jeremy Selan <jeremy...@...>
·
#1227
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
Thanks for this report.
It looks to be a symbol visibility issue related to our use of
yaml-cpp, so this is probably fixable by editing the top-level
CMakeLists file's "USE_EXTERNAL_YAML" section.
I
Thanks for this report.
It looks to be a symbol visibility issue related to our use of
yaml-cpp, so this is probably fixable by editing the top-level
CMakeLists file's "USE_EXTERNAL_YAML" section.
I
|
By
Jeremy Selan <jeremy...@...>
·
#1226
·
|
|
Re: Thoughts on layering of multiple config files
Hi,
Apologies for bumping an old discussion, but I'm in looking for a similar set of features to the ones Nathan described, and as the discussion seemed to have fizzled out, I wanted to show my
Hi,
Apologies for bumping an old discussion, but I'm in looking for a similar set of features to the ones Nathan described, and as the discussion seemed to have fizzled out, I wanted to show my
|
By
Mark Boorer <mark...@...>
·
#1225
·
|
|
Re: ExpressionTransformation for OCIO?
Hi,
I've finished my proof of concept, and it seems to be working quite nicely.
I ended up needing to provide 3 strings for 3d transformations (which isn't too terrible) and I was able to implement
Hi,
I've finished my proof of concept, and it seems to be working quite nicely.
I ended up needing to provide 3 strings for 3d transformations (which isn't too terrible) and I was able to implement
|
By
Mark Boorer <mark...@...>
·
#1224
·
|
|
Review: Nuke: OCIODisplay now has an implemented GPU path
Modified CMake to only include this in the Linux builds. Contemplating implementing the GPU path on the other plugins, as well.
https://github.com/imageworks/OpenColorIO/pull/328
Here's the specific
Modified CMake to only include this in the Linux builds. Contemplating implementing the GPU path on the other plugins, as well.
https://github.com/imageworks/OpenColorIO/pull/328
Here's the specific
|
By
Sean Looper <sean....@...>
·
#1223
·
|
|
Re: OpenColorIO FTBFS on GNU/kFreeBSD boxes
UPDATE: a test build on a Debian GNU/kFreeBSD64 porterbox now gives the
results attached in the buildlog file, where fail is probably related to
the recent upgrade to boost 1.54 in Debian.
Hope it
UPDATE: a test build on a Debian GNU/kFreeBSD64 porterbox now gives the
results attached in the buildlog file, where fail is probably related to
the recent upgrade to boost 1.54 in Debian.
Hope it
|
By
"Matteo F. Vescovi" <mfv.d...@...>
·
#1222
·
|