Hi,
Can we push our exr to 2.0? (+oiio +ocio +osl - due to dependancies)
I know we just recently updated it to 1.7.1 but 2.0 just came out with
multipart support.
Blender (trunk) itself will not benefit from it immediately, but the
multiview branch [1] requires exr 2.0. I don't know if part of th
Hey there,
compiling OpenEXR 2.0.0 and the dependent libs took me all day, so I had no
time to compile the VS2010 libs :(
I am currently uploading the whole bunch, this could take a while because my
internet connection is darn slow.
So stay tuned for the SVN commit mail ;)
/Jürgen
__
Some questions were raised no IRC, let me clarify some things:
Q: What does it change when we update for 2.0?
A: Nothing, absolutely nothing.
The saved files will be the same as before, and the same goes for reading.
As long as we don't change the Blender code the changes will be invisible
for th
Hi Dalai, I'll be building soon for the MinGW systems. Is the python part
of the library required?
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Hi Dalai,
I could provide builds for Vc2008 and VC2012 after the 2.67a release.
Just some questions:
- Do we have to recompile other libs that depend on OpenEXR too?
OSL for example relies on it.
- As we don't have boost python in the boost libs I guess we won't need the
python part in OpenEXR, r
Hi,
I don't see why we would need the python part of it.
Basically the same build settings we used for 1.71 should be used for 2.0 I
believe.
And yes other libs that depend on it will need to be recompiled:
That means primary openimageio. But I also believe OSL and OCIO are needed
(they depend on
Actually i'm really skeptical about such a bump. That'd introduce extra
pain building blender on linux -- seems only gentoo and arch switched to
openexr 2.0.
Also, some of the distros like ubuntu and fedora contains openimageio,
which is for sure linked against distro's openexr 1.6.
This is all l
We've discussed it in IRC today. Conclusion is:
1. Windows/OSX libs are safe for update, wouldn't lead to issues and
platform maintainers could just go ahead
2. I'll update linux build environment during next week.
3. Before merge the code to trunk, we'll need to update wiki page with
building ins
I should be able to see for install_deps.sh next week… ;)
Bastien
On 17/05/2013 20:36, Sergey Sharybin wrote:
> We've discussed it in IRC today. Conclusion is:
>
> 1. Windows/OSX libs are safe for update, wouldn't lead to issues and
> platform maintainers could just go ahead
> 2. I'll update linu
For the records, OSX libs are already committed and working fine (thanks
Jens).
For windows/linux the libs we will need are: openexr, openimageio and
openshadinglanguage.
opencolorio does not need to be updated.
Thanks,
Dalai
--
blendernetwork.org/member/dalai-felinto
www.dalaifelinto.com
2013
Hi Jurgen,
Is the new EXR2.0 entirely updated for windows32 and 64 (MSVC9 - cmake
and scons)?
I'm a bit confused by all the sparse emails on the latest windows
libraries and building systems updates.
I'm having a segfault on windows for some builds of the multiview
branch (building with scons if
Hi Dalai,
The EXR libs are entirely updated to 2.0.
I am having problems with scons too but I accounted this to my absolute
inability to be friends with scons ;)
you said the error is gone when you build with cmake so it's probably a problem
with scons because the libs are the same for both bui
Hi Jurgen,
I just re-confirmed here. If I build with cmake+msvc works fine.
The scons+msvc release build crashes when I open the EXR.
The scons+msvc debug crashes when I open Blender:
http://www.pasteall.org/42743
Now scons is really powerful. For me it's the more convenient way of
building blen
Hi Dalai,
You can build on the command line using CMake too, but you are right from the
users point if view scons is easier. But from the maintainers point if view...
I hope someone will have a look at this issue soon. I really can't find an
error...
/Jürgen
Am 02.06.2013 um 07:15 schrieb Dala
Hi Jurgen,
I think the problem is the release library.
Even with cmake+msvc the exr sample image fails when I build release.
And I just tested with the 1.2 oiio libraries and I still get the same
error with scons+msvc debug.
Remember that you forgot to include a header in your first commit of
the
Hi Dalai,
Thomas Dinges asked me to downgrade OIIO to 1.1.11 just today.
Please try to do a SVN update on your libs and compile again using these.
These problems are strange...
I will have a closer look on this tomorrow.
/Jürgen
Am 02.06.2013 um 20:16 schrieb Dalai Felinto :
> Hi Jurgen,
> I t
Hi again,
The new OIIO libraries don't make any difference. OIIO depends on
OpenEXR and not the other way around. So although that could I can't
see how they would change things.
I remember when you first uploaded the libraries you forgot a header
file (which I'm using in the code). I wonder if i
Hi Dalai,
I can recompile the libs tomorrow. I'll contact you when I am done.
I doubt that this will change anything though. The header that was missing
wasn't installed by the CMake build routine it was not missing at compile time.
It was just omitted by the install script.
But nevertheless I'll
I found where the crash is (still no idea why it's crashing):
#
openexr_api.cpp::imb_load_openexr (...)
(...)
Mem_IStream *membuf = new Mem_IStream(mem, size);
#
To get there I had to build a debug build and replace the linking to:
\lib\windows\openexr\lib\Il
Hi Dalai,
have you tried to build a "RelWithDebInfo" Build of OpenEXR?
This could help to track down the Error if the Debug Lib doesn't help.
/Jürgen
Am 05. Juni 2013 um 10:40 schrieb Dalai Felinto :
> I found where the crash is (still no idea why it's crashing):
>
> #
> openex
> have you tried to build a "RelWithDebInfo" Build of OpenEXR?
I tried, but if I build Blender as debug using the openexr build as
Release with Debug Info it crashes at launch:
http://www.pasteall.org/42864
I've been debugging via a computer I have access via RDC so it's
really annoying btw.
Lea
Update on windows bug:
The crash is actually in the new code inside
imb_exr_get_multiView_id() when I access the (*views).end() or even
simply *i. (this is part of a string const_iterator)
I tried different things (e.g., replacing the StringVector in the code
by std::vector ; to take the StringV
Problem solved ...
Apparently Windows release wasn't happy with my vector
returned from a static function.
Why everyone else could take it? No idea.
If anyone is curious about the fix:
https://github.com/dfelinto/blender/commit/181e780aa84122db540130e4cfbdf3240cf010d9
Jurgen, the new libs seem
Hi Dalai,
congrats on finding this nasty thing ;)
MSVC indeed is a bit picky about casting static return variables to pointers.
/Jürgen
Am 07. Juni 2013 um 09:54 schrieb Dalai Felinto :
> Problem solved ...
>
> Apparently Windows release wasn't happy with my vector
> returned from a static fu
24 matches
Mail list logo
