Closed h-vetinari closed 1 year ago
yeah, we have a libjpeg turbo mapped out, just nobody had time to go through it. can we revert the use of libjpeg turbo here?
@ocefpaf decided to merge #132 after thinking about it (see thread starting here). I don't mind what we do either way.
We probably need to full migration. Hopefully this will be the trigger for us to discuss this. We should phase out the jpeg library and move to the better maintained libjpeg-turbo.
Can we do something like blas
?
Recall this was complicated before because of version compatibility/feature support, but am hoping that gap has closed over time to make this easier
as a Pillow specific question, can today's pillow be built with standard jpeg (i.e. not libjpeg-turbo)
I somewhat see this move to using jpeg turbo has counter to the open discussion we had referenced above.
I think it would be good if we reverted the merge with turbo, see https://github.com/conda-forge/pillow-feedstock/pull/134, and made pillow depend on jpeg
instead until the conversation at https://github.com/conda-forge/conda-forge.github.io/issues/673 is resolved.
From discussion in #126:
From #132:
ClobberWarning: This transaction has incompatible packages due to a shared path. packages: conda-forge/win-64::jpeg-9e-h8ffe710_2, conda-forge/win-64::libjpeg-turbo-2.1.4-hcfcfb64_0 path: 'library/lib/jpeg.lib'