Default compression profile mismatch between libjpeg and libjpeg-turbo APIs
PJK136 opened this issue · comments
Since f1d512d, there is a mismatch between the default compression profile for libjpeg api which is JCP_MAX_COMPRESSION (set by jpeg_create_compress in jcapimin.c and documented in README-mozilla.txt) and for turbojpeg api which has now JCP_FASTEST as default in turbojpeg.c.
Is it the intended behavior or a regression unintentionally introduced by fixing the tests ?
It's been done for tests. I didn't expect anyone to use this library for the turbo API.
I guess it will need a smarter switch. Maybe read an env var?