mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libjpeg-turbo and libjpeg
Date: Wed, 14 Feb 2018 12:44:38 +0100	[thread overview]
Message-ID: <20180214114438.jtss7sxe6enwxbps@pengutronix.de> (raw)
In-Reply-To: <CABDcavbJ6F9REd_Namn9+jCJr6Ke-ph2yOd0aGAdJNdppd10tA@mail.gmail.com>

Hi,

On Wed, Feb 14, 2018 at 10:57:06AM +0100, Guillermo Rodriguez Garcia wrote:
> 2018-02-14 10:22 GMT+01:00 Guillermo Rodriguez Garcia <
> guille.rodriguez@gmail.com>:
> > No build issues here and I can confirm that both gst-plugins-good1 (with
> > the jpeg plugin) and imagemagick both work fine with libjpeg-turbo on my
> > target platform.
> >
> > Some comments:
> >
> > - According to the documentation (https://github.com/libjpeg-
> > turbo/libjpeg-turbo/blob/master/BUILDING.md), NASM or YASM are required
> > if building x86 or x86-64 SIMD extensions. I have not verified this ,yself
> > (I'm building for an ARM target) but since we are enabling SIMD, shouldn't
> > the .in file select HOST_NASM? (ideally for ARCH_X86 only but it seems that
> > this can't be checked in the .in file?)

Yes the dependency should be there. Hopefully my build tests will tell me
the same thing :-).
It's true, that we cannot define the dependency for x86 only, but maybe I
can hack this. I didn't bother with it for gst-libav but libjpeg is
significantly smaller. I need to think about this.

> > - For ARM targets, --with-simd requires NEON support. Perhaps the .make
> > file should do something like this:
> >
> > # For ARM, enable SIMD extensions only if NEON is available
> > ifdef PTXCONF_ARCH_ARM_NEON
> > LIBJPEG_CONF_OPT += --with-simd
> > endif
> > # For architectures other than ARM, enable SIMD extensions unconditionally
> > ifndef PTXCONF_ARCH_ARM
> > LIBJPEG_CONF_OPT += --with-simd
> > endif

Indeed.

> BTW one more comment:
> 
> If --with-jpeg8 is specified, --with-jpeg7 has no effect. See configure.ac:
> 
>   if test "x${with_jpeg8}" = "xyes"; then
>     JPEG_LIB_VERSION=80
>   else
>     if test "x${with_jpeg7}" = "xyes"; then
>       JPEG_LIB_VERSION=70
>     else
>       JPEG_LIB_VERSION=62
>     fi
>   fi
> 
> So you may want to remove --with-jpeg7 from the .make file.

We try to set all regular options, even if they are no-ops. This way, the
next person doing a version bump won't have to recheck existing options.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-02-14 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13  9:23 Guillermo Rodriguez Garcia
2018-02-13 15:37 ` Michael Olbrich
2018-02-13 16:12   ` Guillermo Rodriguez Garcia
2018-02-14  7:49     ` Michael Olbrich
2018-02-14  9:22       ` Guillermo Rodriguez Garcia
2018-02-14  9:57         ` Guillermo Rodriguez Garcia
2018-02-14 11:44           ` Michael Olbrich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180214114438.jtss7sxe6enwxbps@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox