Gonzalo Garramuño
2007-12-07 05:11:41 UTC
Hi, Florian.
I would like to request some features for the build of openexr on=
=20
windows. Currently, the standard projects and build drops everything=
in=20
a Deploy directory.
Unfortunately, this is true of both the vc8 and vc7 projects. The is=
sue=20
is that Microsoft, in its infinite wisdom, has broken ABI compatabili=
ty=20
yet again. This makes it problematic to use the latest cutting edge=
=20
openexr while supporting different versions that need different=20
compilers. It means manually modifying 5 or so project files.
The actual requests are that:
=09a) The OpenEXR .sln files deploy elements in specific subdirs for =
vc8=20
and vc7.
=09b) The .sln files become deprecated in favor of a multiplatform bu=
ild=20
tool like cmake, which allows easily running all command-line and=
=20
automating builds on all different platforms consistently. Using=
=20
microsoft crappy gui is a big disadvantage (and cmake can automatical=
ly=20
generate a .sln file from .cmake build rules).
=09c) The OpenEXR DLLs become versioned so rather than IlmImf.dll you=
get=20
IlmImf.1.5.dll like on unix. Currently, I am integrating my products=
=20
with other vendors that may be shipping older openexr versions. Whil=
e=20
no conflict has yet appeared (magically), I think this is just waitin=
g=20
to happen and I know when it does, it will be a nightmare to figure o=
ut=20
the issue.
--=20
Gonzalo Garramu=F1o
***@advancedsl.com.ar
AMD4400 - ASUS48N-E
GeForce7300GT
Xubuntu Gutsy
I would like to request some features for the build of openexr on=
=20
windows. Currently, the standard projects and build drops everything=
in=20
a Deploy directory.
Unfortunately, this is true of both the vc8 and vc7 projects. The is=
sue=20
is that Microsoft, in its infinite wisdom, has broken ABI compatabili=
ty=20
yet again. This makes it problematic to use the latest cutting edge=
=20
openexr while supporting different versions that need different=20
compilers. It means manually modifying 5 or so project files.
The actual requests are that:
=09a) The OpenEXR .sln files deploy elements in specific subdirs for =
vc8=20
and vc7.
=09b) The .sln files become deprecated in favor of a multiplatform bu=
ild=20
tool like cmake, which allows easily running all command-line and=
=20
automating builds on all different platforms consistently. Using=
=20
microsoft crappy gui is a big disadvantage (and cmake can automatical=
ly=20
generate a .sln file from .cmake build rules).
=09c) The OpenEXR DLLs become versioned so rather than IlmImf.dll you=
get=20
IlmImf.1.5.dll like on unix. Currently, I am integrating my products=
=20
with other vendors that may be shipping older openexr versions. Whil=
e=20
no conflict has yet appeared (magically), I think this is just waitin=
g=20
to happen and I know when it does, it will be a nightmare to figure o=
ut=20
the issue.
--=20
Gonzalo Garramu=F1o
***@advancedsl.com.ar
AMD4400 - ASUS48N-E
GeForce7300GT
Xubuntu Gutsy