From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wm0-x230.google.com ([2a00:1450:400c:c09::230]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1elWnv-0001cL-A5 for ptxdist@pengutronix.de; Tue, 13 Feb 2018 10:23:11 +0100 Received: by mail-wm0-x230.google.com with SMTP id x4so12369287wmc.0 for ; Tue, 13 Feb 2018 01:23:11 -0800 (PST) MIME-Version: 1.0 From: Guillermo Rodriguez Garcia Date: Tue, 13 Feb 2018 10:23:09 +0100 Message-ID: Subject: [ptxdist] libjpeg-turbo and libjpeg List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============1497780993==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============1497780993== Content-Type: multipart/alternative; boundary="001a1144e6900a94380565148b31" --001a1144e6900a94380565148b31 Content-Type: text/plain; charset="UTF-8" Hi all, I need to use libjpeg-turbo for some apps that rely on specific libjpeg-turbo extensions that are not available in the standard (IJG's) libjpeg library. So I started to create a set of ptxdist rules for libjpeg-turbo. libjpeg-turbo is supposed to provide a drop-in replacement for the standard IJG's libjpeg, and in fact many Linux distributions have already switched to it. So most packages that currently depend on LIBJPEG should be able to use libjpeg-turbo as well without any changes. Example: gst-plugins-good1.in currently does the following: select LIBJPEG if GST_PLUGINS_GOOD1_JPEG However, gst-plugins-good1 should work just fine with libjpeg-turbo as well. In fact the upstream gst-plugins already switched to libjpeg-turbo some time ago (see the Cerbero scripts) So, what is the recommended way to approach this in ptxdist? I can imagine some options: 1. Provide a separate set of .in/.make files for libjpeg-turbo and a separate LIBJPEG_TURBO package. So new packages that want to use libjpeg-turbo would need to explicitly select LIBJPEG_TURBO (instead of LIBJPEG). But this means that packages that currently use libjpeg would not be able to benefit from the performance improvements in libjpeg-turbo. Also I am not sure whether these two libraries (libjpeg and libjpeg-turbo) can actually coexist in the same system. 2. Modify the LIBJPEG rules to provide an option to select between the standard (IJG) libjpeg, or libjpeg-turbo. This would be similar to what is done in alsa.in/alsa.make to select between the "full" and "light" versions of the library. 3. Other? Thank you, Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --001a1144e6900a94380565148b31 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I need to use libjpeg-turbo for= some apps that rely on specific libjpeg-turbo extensions that are not avai= lable in the standard (IJG's) libjpeg library. So I started to create a= set of ptxdist rules for libjpeg-turbo.

libjpeg-t= urbo is supposed to provide a drop-in replacement for the standard IJG'= s libjpeg, and in fact many Linux distributions have already switched to it= . So most packages that currently depend on LIBJPEG should be able to use l= ibjpeg-turbo as well without any changes.

Example:= gst-plugins-good1.in currently= does the following:

select LIBJPEG if GST_PLUGINS_GOOD1_= JPEG

However, gst-plugins-good1 should work ju= st fine with libjpeg-turbo as well. In fact the upstream gst-plugins alread= y switched to libjpeg-turbo some time ago (see the Cerbero scripts)

So, what is the recommended way to approach this in ptxdi= st? I can imagine some options:

1. Provide a separ= ate set of .in/.make files for libjpeg-turbo and a separate LIBJPEG_TURBO p= ackage. So new packages that want to use libjpeg-turbo would need to explic= itly select LIBJPEG_TURBO (instead of LIBJPEG). But this means that package= s that currently use libjpeg would not be able to benefit from the performa= nce improvements in libjpeg-turbo. Also I am not sure whether these two lib= raries (libjpeg and libjpeg-turbo) can actually coexist in the same system.=

2. Modify the LIBJPEG rules to provide an option = to select between the standard (IJG) libjpeg, or libjpeg-turbo. This would = be similar to what is done in alsa.in/= alsa.make to select between the "full" and "light" = versions of the library.

3. Other?

<= /div>
Thank you,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
--001a1144e6900a94380565148b31-- --===============1497780993== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============1497780993==--