Fix build issues on OSX #35
Conversation
…nd only force it on mac since that seems to fail otherwise
|
However, for some reason on OS X, OpenEXR's exceptions aren't detected as derived from std::exception and don't get caught by the corresponding try/catch statements. I don't know why this is. |
|
FWIW, OpenEXR 2.3 no longer derives its exceptions from std::exception. |
|
Why would they do that exactly? |
|
It’s not a portable construction. On Windows, std::exception is not marked for symbol export, which means sub-classing exception and marking the subclass with __declspec export, will result in undefined behavior if static members are accessed. |
|
I’m sorry, I misspoke. Iex::BaseExc used to be multiply-derived from std::string, which introduced the problems because std::string is not marked for symbol export. It is of course still derived from std::exception. AcademySoftwareFoundation/openexr@fa59776 |
This is in reference to the errors described in #32, which was caused by the wrong standard library being used and not found by the compiler, due to python being built with an earlier version of OS X before that library was deprecated. This works around that by changing the target platform in the event that this is the case.