[Bf-committers] platform maintainers: request to update exr lib to 2.0

Jürgen Herrmann shadowrom at me.com
Wed Jun 5 10:57:18 CEST 2013


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 <dfelinto at gmail.com>:

> 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\IlmImf.lib
> instead of:
> \lib\windows\openexr\lib\IlmImf_d.lib
>
> And it consistently breaks on Release for windows and 64, but not for Debug.
> Any clues on how to debug this?
>
> --
> Dalai
>
> --
> blendernetwork.org/member/dalai-felinto
> www.dalaifelinto.com
>
>
> 2013/6/3 Jürgen Herrmann <shadowrom at me.com>:
> > 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 try to recompile them for you.
> > Otherwise we should try to report a bug to the OpenEXR devs. It could be an error in the libs.
> >
> > /Jürgen
> >
> > Am 03.06.2013 um 20:58 schrieb Dalai Felinto <dfelinto at gmail.com>:
> >
> >> 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 it's related and the
> >> first "release" build is buggy. The ideal would be to rebuild OpenEXR
> >> for release and hope it fixes the problem.
> >>
> >> If you don't want to commit the libs without knowing they will fix the
> >> problem you can put them on blender.org ftp incoming folder. (or poke
> >> me on IRC and we can find a solution).
> >>
> >> (or checkout the svn code for multiview, it should be easy to
> >> reproduce the problem in your windows station)
> >>
> >> Thanks,
> >> Dalai
> >>
> >>
> >> --
> >> blendernetwork.org/member/dalai-felinto
> >> www.dalaifelinto.com
> >>
> >>
> >> 2013/6/2 Jürgen Herrmann <shadowrom at me.com>:
> >>> 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 <dfelinto at gmail.com>:
> >>>
> >>>> 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 library? I wonder if that was somehow also missing when you built
> >>>> it. I don't know.
> >>>>
> >>>> --
> >>>> Dalai
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list