Re: openexr on windows

Hello,

You will find enclosed my modded Makefile for a 1.4.0 build on cygwin.
If I remember correctly, I just added "-mno-cygwin" to LDFLAGS and it
compiled correctly. It has been a while tough.

Regards,

Daniel Léonard
--

-- 
Entre Ce que je pense, Ce que je veux dire, Ce que je crois dire, Ce
que je dis, Ce que vous avez envie d'entendre, Ce que vous entendez,
Ce que vous comprenez... il y a dix possibilités qu'on ait des
difficultés à communiquer. Mais essayons quand même... - Bernard
Werber

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel

Python bindings for OpenEXR

Hi all,

I've been working on some Python bindings for OpenEXR.  This is a
first cut:

http://www.excamera.com/articles/26/openexr.html

Comments welcome!

--

-- 
James Bowman

Re: Python bindings for OpenEXR

This sounds really exciting.
Is there documentation on the Python API?

Florian

James Bowman wrote:
> Hi all,
> 
> I've been working on some Python bindings for OpenEXR.  This is a
> first cut:
> 
> http://www.excamera.com/articles/26/openexr.html
> 
> Comments welcome!
> 

Re: Python bindings for OpenEXR

Thanks... there is now.  I wrote some preliminary docs on the web page.

> This sounds really exciting.
> Is there documentation on the Python API?
> 
> Florian
> 
> James Bowman wrote:
> >Hi all,
> >
> >I've been working on some Python bindings for OpenEXR.  This is a
> >first cut:
> >
> >http://www.excamera.com/articles/26/openexr.html
> >
> >Comments welcome!
> >

--

-- 
James Bowman
http://acelere.net      1-877-ACELERE

static link

Hello,

How can I link OpenEXR library as static? I had tried it many times
and many ways, but with no luck. And nobody know how to do it.

I'm try to write mental ray output shader.
My Makefile looks like this:

CC = g++
INC = -I/usr/autodesk/maya8.5/devkit/mentalray/include -I../../../openexr-1.4.0/IlmImf
-I../../../openexr-1.4.0/IlmThread -I../../../openexr-1.4.0/Imath
-I../../../openexr-1.4.0/Iex -I../../../openexr-1.4.0/Half -I../../../zlib-1.2.3
LIB = -L../lib -lstdc++ ../../../openexr-1.4.0/IlmImf/.libs/libIlmImf.a
../../../openexr-1.4.0/IlmThread/.libs/libIlmThread.a
../../../openexr-1.4.0/Imath/.libs/libImath.a  ../../../openexr-1.4.0/Iex/.libs/libIex.a
../../../openexr-1.4.0/Half/.libs/libHalf.a -L../../../zlib-1.2.3 -lz
CFLAGS = -O2 -fPIC -shared -export-dynamic

shaders_p.so : p_OpenEXR_saver.cpp p_MegaTK_pass.cpp p_constant.cpp

        $(CC) $(INC) $(LIB) $(CFLAGS) -o shaders_p.so p_OpenEXR_saver.cpp p_MegaTK_pass.cpp p_constant.cpp

local: shaders_p.so

Shader comiled fine without any errors, but
I always get Maya crash and this error during call my shader:
/usr/autodesk/maya8.5/bin/maya.bin: symbol lookup error:
/usr/autodesk/maya8.5/mentalray/lib/shaders_p.so: undefined symbol: _ZN3Imf5SliceC1ENS_9PixelTypeEPcjjiidbb

What's wrong?

Re[2]: static link

_______________________________________________
Openexr-devel mailing list
Openexr-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/openexr-devel

Re: static link

Am 15.06.07, 13:03 +0400 schrieb Pavel Ledin:

> How can I link OpenEXR library as static? I had tried it many times
> and many ways, but with no luck. And nobody know how to do it.

Many apps are distributed in bundle style. osX has system support for it.
This is, put all your fancy stuff into one directory and provide a script 
which sets variables and loads the main executable. Then register your app 
to the OS for menues, file types and so on.

I did not try it for plug-ins, just an idea which might work.

kind regards
Kai-Uwe Behrmann
--
developing for colour management 
www.behrmann.name + www.oyranos.org + www.cinepaint.org

Re: static link

--- Pavel Ledin <puppet <at> rambler.ru> wrote:

>         $(CC) $(INC) $(LIB) $(CFLAGS) -o
> shaders_p.so p_OpenEXR_saver.cpp p_MegaTK_pass.cpp
> p_constant.cpp

Hi Pavel,

Could you try changing your command line to:

$(CC) $(INC) $(CFLAGS) -o shaders_p.so
p_OpenEXR_saver.cpp p_MegaTK_pass.cpp p_constant.cpp
$(LIB)

The symbols for static libraries are resolved from
left to right on the command line, so the static
libraries should come after your code.

Darby

Re[2]: static link

Hello darby,

Friday, June 15, 2007, 8:04:32 PM, you wrote:

>$(CC) $(INC) $(CFLAGS) -o shaders_p.so
>p_OpenEXR_saver.cpp p_MegaTK_pass.cpp p_constant.cpp
>$(LIB)

>The symbols for static libraries are resolved from
>left to right on the command line, so the static
>libraries should come after your code.

Many thanks, it's works fine!

I'm using now this construction:

$(CC) $(INC) $(CFLAGS) $(LIB) -o shaders_p.so
p_OpenEXR_saver.cpp p_MegaTK_pass.cpp p_constant.cpp
$(LIB_STATIC)

Thanks!

--

-- 
Best regards,
 Pavel Ledin aka Puppet                     mailto:puppet <at> rambler.ru
 Moscow, Russia

Re[2]: static link

Hello,

I managed to do it for small test programs.

Once the distribution has been compiled "normally" (to have the
generated files generated), I copied all the header and implementation
files in a single directory and compiled everything as an archive file
(.a). My test programs are linked to that archive.

It is not pretty but it does works.

Daniel Léonard
--
Entre Ce que je pense, Ce que je veux dire, Ce que je crois dire, Ce
que je dis, Ce que vous avez envie d'entendre, Ce que vous entendez,
Ce que vous comprenez... il y a dix possibilités qu'on ait des
difficultés à communiquer. Mais essayons quand même... - Bernard
Werber

--

-- 
Entre Ce que je pense, Ce que je veux dire, Ce que je crois dire, Ce
que je dis, Ce que vous avez envie d'entendre, Ce que vous entendez,
Ce que vous comprenez... il y a dix possibilités qu'on ait des
difficultés à communiquer. Mais essayons quand même... - Bernard
Werber