libjpeg-turbo vs jpeg

[Ken Cunningham]

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: 

<https://trac.macports.org/ticket/38907 <https://trac.macports.org/ticket/38907>>

and 

<https://libjpeg-turbo.org/About/Jpeg-9 <https://libjpeg-turbo.org/About/Jpeg-9>>

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?

Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180601/a524df7b/attachment.html>