libjpeg-turbo vs jpeg
ken.cunningham.webuse at gmail.com
Fri Jun 1 19:18:43 UTC 2018
I have a new game port done, Endless Sky <https://endless-sky.github.io <https://endless-sky.github.io/>>.
It requires "libjpeg-turbo" rather than “jpeg" and so I came across the mess with the conflict with jpeg:
Homebrew installs them in parallel, which I guess is all we can realistically do given the API9 vs API8 business.
We could do that easily enough. It doesn’t look like libjpeg-turbo can be a drop in replacement for jpeg any more as they now have different APIs.
Anyone have any ideas on [ how to / if we should ] try to resolve this?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev