All good?

We're looking at releasing 2.1.0 in a matter of weeks so if there are issues 
please holler

(I am looking at the Alembic mailing list also in regards to the namespace 
symbol problems people have had and have a fix for the explicit use of Imath:: 
in one of the PyIlmBase files coming shortly... )


- Piotr
________________________________
From: openexr-devel-bounces+pstanczyk=ilm....@nongnu.org 
[openexr-devel-bounces+pstanczyk=ilm....@nongnu.org] on behalf of Christopher 
Horvath [blackenc...@gmail.com]
Sent: 28 October 2013 08:50
To: Richard Addison-Wood
Cc: openexr-devel@nongnu.org
Subject: Re: [Openexr-devel] Iex linking errors on OSX

The problem was that I didn't update my build system to include the new IexMath 
library.  Sorry for the noise!


On Sun, Oct 27, 2013 at 4:37 PM, Richard Addison-Wood 
<rich...@wetafx.co.nz<mailto:rich...@wetafx.co.nz>> wrote:
I wonder if your clang++ build would want:

IEXMATH_EXPORT
int getMathExcOn();

in IexMathFloatExc.h to have IEXMATH_EXPORT be #defined as extern instead of an 
empty string so that it treats getMathExcOn() as global?


On 10/26/13 12:35, Christopher Horvath wrote:
Hey Folks,

I get the following errors when trying to link PyAlembic on top of Iex using 
ilmbase 2.0.1, when building on OSX Mavericks with clang++ and -std=c++11:

Undefined symbols for architecture x86_64:
"Iex_2_0::getMathExcOn()"

I checked the link order, and the library is included in the right place. I 
checked the symbols in libIex.a, and they are plenty of Iex_2_0:: symbols, just 
not this one.

What might this be?

Chris

--
I think this situation absolutely requires that a really futile and stupid 
gesture be done on somebody's part. And we're just the guys to do it.




--
I think this situation absolutely requires that a really futile and stupid 
gesture be done on somebody's part. And we're just the guys to do it.
_______________________________________________
Openexr-devel mailing list
Openexr-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/openexr-devel

Reply via email to