Re: [Openexr-devel] Future versions: (WAS: RE: OpenEXR 1.7.1 release)

[Christopher Horvath]

Hey Piotr,

I think this is a really good idea, and in fact, I really think they should be combined into a single package. It's perfectly reasonable to just not link against libraries you don't need - but by having them separate, it implies that you can mix & match OpenEXR versions and IlmBase versions, which obviously you can't.  You could even have:

--disable-openexr

--disable-pyilmbase

in the autoconf stuff for people who didn't have tiff or jpeg installed and didn't want build errors.

On Tue, Jul 31, 2012 at 3:46 PM, Piotr Stanczyk <address@hidden> wrote:

Hi All,

I am thinking about standardising on a single version for the different components that make up OpenEXR.
Thus, for the next v2 release we would have

OpenEXR v2.0.0
IlmBase v2.0.0
PyIlmBase v2.0.0
etc

Any strong feeling about this approach?


Piotr

---

From: openexr-devel-bounces+pstanczyk=address@hidden [openexr-devel-bounces+pstanczyk=address@hidden] on behalf of Piotr Stanczyk [address@hidden]
Sent: 31 July 2012 15:36
To: address@hidden; address@hidden
Subject: [Openexr-devel] OpenEXR 1.7.1 release

Tuesday, July 31st, 2012

OpenEXR v1.7.1 has been released and is available for download.
Tarballs can be obtained from the downloads section on github: https://github.com/openexr/openexr/downloads

This release includes the following components:

  OpenEXR: v1.7.1
  IlmBase: v1.0.3
  PyIlmBase: v1.0.0 (introduces a Boost dependency)
  OpenEXR_Viewers: v1.0.2

Please see the Changelog for additional information in each of the modules.


For the developer community:  The master branch in git hub has been tagged as v1.7.1.

_______________________________________________
Openexr-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/openexr-devel

--
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.