libtiff update again
Vadim Zeitlin
vadim at wxwidgets.org
Sat Jun 2 07:22:42 PDT 2007
Hello,
I'm looking at Steven's patch upgrading libtiff to 3.8.2:
http://sourceforge.net/tracker/index.php?func=detail&aid=1726085&group_id=9863&atid=309863
but there are several problems/questions with it.
First is the obvious one: this patch simply rewrites our version with the
pristine 3.8.2 sources. Except for a wxjpeg_boolean hack all the other
changes are discarded. So the question is whether anyone remembers any
changes that are still needed, especially for the systems and build
environments which I can't test myself (OS/2, wxMac with Xcode, ...)?
Second, after applying this patch, the compilation will almost certainly
be broken for everything except VC++ and Unix systems using configure. I'll
need help with fixing this after applying the patch -- or ideally even
before. So if anybody can test the compilation of this patch with the other
compilers/Xcode even before it's applied and provide the supplemental
fixes, it would be great.
Third, at the cvs level it doesn't seem to be possible to import libtiff
sources into an existing directory (src/tiff). But I'd really like to use
the import mechanism to simplify upgrading in the future. So what can we do
(short of switching to svn right now (whose management of vendor branches
is quite suboptimal too IMHO))? I see either switching to src/libtiff
(which will, of course, be inconsistent with src/{jpeg,png,zlib}) or moving
3rd party stuff out of src all together into some new 3rdparty top level
directory. For me having 3rdparty/{png,jpeg,tiff,zlib} would be more
logical but this would require updating all distribution scripts and I
don't know who is going to do it...
Please let's decide what are we going to do with this. And please make no
mistake; we must do something as upgrading to 3.8.2 is a high priority
task, being able to crash any wx program working with images by just
feeding it a bitmap is not acceptable.
TIA,
VZ
More information about the wx-dev
mailing list