22 Feb
2012
22 Feb
'12
4:59 a.m.
On 21 February 2012 16:51, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
it doesn't matter, libjpeg-turbo replaces it. the API the same, code
won't break... it's sort of an drop in replacement.:)
Calvin
As long as it
doesn't introduce any issues, and as long as
it can coexist with normal libjpeg, why not compile a
version for TDE just for the distros/versions that don't
already have it?
We should not repackage anything still actively maintained upstream and is not a direct
dependency for Trinity.
Serghei said he would add a detection test to the cmake files.
One note: if packagers build with libjpeg-turbo installed but downstream users do not
have libjpeg-turbo installed, everything should still work. That is, using libjpeg-turbo
should be optional in the code but still use the expected default libjpeg libraries when
libjpeg-turbo is not installed.
Darrell