Topics

Meeting today: Two Questions [Imath]

Owen T.
 

In today's meeting I want to get a sense of the group's impressions/concerns on two things:

1: Supporting Autoconf building in the new Imath repo (and consequentially OpenEXR as a whole)

    - i.e. is it still necessary or is cmake alone sufficient?

2: Using git submodules to manage Imath installation for OpenEXR

    - This permits: automatically cloning the source of Imath (if it's not detected) and otherwise building almost identically to how OpenEXR does already

    - Information about this can be found here

If there are any concerns I would like to hear them. I heir on the side of not supporting Autoconf, and using the submodules.

Owen Thompson

Larry Gritz
 

My answers would be:

1. Let's please DON'T support autoconf any more

2. Yes, submodule!


On Jun 4, 2020, at 8:34 AM, Owen T. via lists.aswf.io <ownthmpsn=protonmail.ch@...> wrote:

In today's meeting I want to get a sense of the group's impressions/concerns on two things:

1: Supporting Autoconf building in the new Imath repo (and consequentially OpenEXR as a whole)

    - i.e. is it still necessary or is cmake alone sufficient?

2: Using git submodules to manage Imath installation for OpenEXR

    - This permits: automatically cloning the source of Imath (if it's not detected) and otherwise building almost identically to how OpenEXR does already

    - Information about this can be found here

If there are any concerns I would like to hear them. I heir on the side of not supporting Autoconf, and using the submodules.

Owen Thompson

_

--
Larry Gritz




Cary Phillips
 


Also, we're assuming we lose the term "IlmBase" entirely, and the current subfolders of IlmBase move to the top level of the new repo.  So, the "Imath" repo has subfolders called Imath, ImathTest, Half, HalfTest, Iex, IexMath, IexTest:

...

And IlmThread stays with openexr.

Just confirming, is this what others are expecting?



On Thu, Jun 4, 2020 at 9:09 AM Larry Gritz <lg@...> wrote:
My answers would be:

1. Let's please DON'T support autoconf any more

2. Yes, submodule!


On Jun 4, 2020, at 8:34 AM, Owen T. via lists.aswf.io <ownthmpsn=protonmail.ch@...> wrote:

In today's meeting I want to get a sense of the group's impressions/concerns on two things:

1: Supporting Autoconf building in the new Imath repo (and consequentially OpenEXR as a whole)

    - i.e. is it still necessary or is cmake alone sufficient?

2: Using git submodules to manage Imath installation for OpenEXR

    - This permits: automatically cloning the source of Imath (if it's not detected) and otherwise building almost identically to how OpenEXR does already

    - Information about this can be found here

If there are any concerns I would like to hear them. I heir on the side of not supporting Autoconf, and using the submodules.

Owen Thompson

_

--
Larry Gritz






--
Cary Phillips | R&D Supervisor | ILM | San Francisco

Larry Gritz
 

We can talk about this on the call, but... must we really bring Iex into Imath?

Does Imath really need exceptions outside standard C++ ones? (Keeping in mind that we can use 'using' to alias the old names to preserve source compatibility.)

Grep says only the following are thrown by Imath (eliminating duplicates):

ImathFrustum.h:        throw IEX_NAMESPACE::ArgExc ("fovx and fovy cannot both be non-zero.");
ImathFrustum.h:        throw IEX_NAMESPACE::DivzeroExc ("Bad viewing frustum: "
ImathMatrix.h:                throw ::IMATH_INTERNAL_NAMESPACE::SingMatrixExc ("Cannot invert singular matrix.");
ImathVec.h: throw NullVecExc ("Cannot normalize null vector.");
ImathVec.h:            throw InfPointExc ("Cannot normalize point at infinity.");
ImathGL.h: throw IEX_NAMESPACE::OverflowExc ("GL matrix overflow");
ImathMatrixAlgo.h: throw IMATH_INTERNAL_NAMESPACE::ZeroScaleExc ("Cannot remove zero scaling "


These all look like they could be std::out_of_range, std::domain_error, std::overflow_error.


On Thu, Jun 4, 2020 at 11:44 AM Cary Phillips <cary@...> wrote:

Also, we're assuming we lose the term "IlmBase" entirely, and the current subfolders of IlmBase move to the top level of the new repo.  So, the "Imath" repo has subfolders called Imath, ImathTest, Half, HalfTest, Iex, IexMath, IexTest:

...

And IlmThread stays with openexr.

Just confirming, is this what others are expecting?



On Thu, Jun 4, 2020 at 9:09 AM Larry Gritz <lg@...> wrote:
My answers would be:

1. Let's please DON'T support autoconf any more

2. Yes, submodule!


On Jun 4, 2020, at 8:34 AM, Owen T. via lists.aswf.io <ownthmpsn=protonmail.ch@...> wrote:

In today's meeting I want to get a sense of the group's impressions/concerns on two things:

1: Supporting Autoconf building in the new Imath repo (and consequentially OpenEXR as a whole)

    - i.e. is it still necessary or is cmake alone sufficient?

2: Using git submodules to manage Imath installation for OpenEXR

    - This permits: automatically cloning the source of Imath (if it's not detected) and otherwise building almost identically to how OpenEXR does already

    - Information about this can be found here

If there are any concerns I would like to hear them. I heir on the side of not supporting Autoconf, and using the submodules.

Owen Thompson

_

--
Larry Gritz






--
Cary Phillips | R&D Supervisor | ILM | San Francisco



--
Larry Gritz
lg@...

Nick Porcino
 

I second the motion earlier in the thread to not support autoconf for Imath.


On Thu, Jun 4, 2020 at 12:43 PM Larry Gritz <lg@...> wrote:
We can talk about this on the call, but... must we really bring Iex into Imath?

Does Imath really need exceptions outside standard C++ ones? (Keeping in mind that we can use 'using' to alias the old names to preserve source compatibility.)

Grep says only the following are thrown by Imath (eliminating duplicates):

ImathFrustum.h:        throw IEX_NAMESPACE::ArgExc ("fovx and fovy cannot both be non-zero.");
ImathFrustum.h:        throw IEX_NAMESPACE::DivzeroExc ("Bad viewing frustum: "
ImathMatrix.h:                throw ::IMATH_INTERNAL_NAMESPACE::SingMatrixExc ("Cannot invert singular matrix.");
ImathVec.h: throw NullVecExc ("Cannot normalize null vector.");
ImathVec.h:            throw InfPointExc ("Cannot normalize point at infinity.");
ImathGL.h: throw IEX_NAMESPACE::OverflowExc ("GL matrix overflow");
ImathMatrixAlgo.h: throw IMATH_INTERNAL_NAMESPACE::ZeroScaleExc ("Cannot remove zero scaling "


These all look like they could be std::out_of_range, std::domain_error, std::overflow_error.


On Thu, Jun 4, 2020 at 11:44 AM Cary Phillips <cary@...> wrote:

Also, we're assuming we lose the term "IlmBase" entirely, and the current subfolders of IlmBase move to the top level of the new repo.  So, the "Imath" repo has subfolders called Imath, ImathTest, Half, HalfTest, Iex, IexMath, IexTest:

...

And IlmThread stays with openexr.

Just confirming, is this what others are expecting?



On Thu, Jun 4, 2020 at 9:09 AM Larry Gritz <lg@...> wrote:
My answers would be:

1. Let's please DON'T support autoconf any more

2. Yes, submodule!


On Jun 4, 2020, at 8:34 AM, Owen T. via lists.aswf.io <ownthmpsn=protonmail.ch@...> wrote:

In today's meeting I want to get a sense of the group's impressions/concerns on two things:

1: Supporting Autoconf building in the new Imath repo (and consequentially OpenEXR as a whole)

    - i.e. is it still necessary or is cmake alone sufficient?

2: Using git submodules to manage Imath installation for OpenEXR

    - This permits: automatically cloning the source of Imath (if it's not detected) and otherwise building almost identically to how OpenEXR does already

    - Information about this can be found here

If there are any concerns I would like to hear them. I heir on the side of not supporting Autoconf, and using the submodules.

Owen Thompson

_

--
Larry Gritz






--
Cary Phillips | R&D Supervisor | ILM | San Francisco



--
Larry Gritz
lg@...



--
--------------------------------
Nick Porcino @meshula
Virtual and augmented production, interactive applications, and robotics, since 1982