From: Rob Radtke <rob@st...> - 2006-04-06 05:01:51
The ecw package is fairly large -- the current source distribution (version
3.3 rc2) is ~18 MB uncompressed. That makes it bigger than all the other
packages in v3p combined.
We could probably trim that down a bit but it will still be rather large.
The JPEG 2000 compression standard (unlike regular jpeg) is extremely
complex, so the ecw package is also very complex (and large).
Also, the package is still under development (by ER Mapper). Even though it
seems very robust to me (it can handle all of the JPEG 2000 Part IV
compliance files and it also supports large files), I'd like to see it
mature some more before we clone it and stick it in the vxl repository.
Otherwise, we risk creating a fork.
For now, I think that making the JPEG 2000 capability available through a
cmake plugin is a good compromise between making it available and avoiding
Does anyone else have any other opinions?
PS - On the plus side, the Er Mapper folks seem pretty committed to
supporting a variety of platforms by using qmake (from trolltech). So, most
vxl users/developers ought to be able to get ecw built on their platform of
choice without too much trouble.
->From: Amitha Perera [mailto:perera@...]
->Sent: Wednesday, April 05, 2006 5:04 PM
->Subject: JPEG 2000 support
->Is the ECW package you used a pretty small library? Would it make
->sense to port it into v3p, with an optional build flag?