Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] libfslcodec: add missing configure options
Date: Fri, 4 Mar 2016 10:17:58 +0100	[thread overview]
Message-ID: <20160304091758.GA20721@t450s.lan> (raw)
In-Reply-To: <20151214212854.GB10029@t450s.lan>

Yann, All,

On Mon, Dec 14, 2015 at 10:28:54PM +0100, Gary Bisson wrote:
> Yann, All,
> 
> On Sun, Dec 13, 2015 at 09:32:24PM +0100, Yann E. MORIN wrote:
> > Gary, All,
> > 
> > On 2015-12-10 14:52 +0100, Gary Bisson spake thusly:
> > > Enable VPU and hard float support when the proper configuration is setup.
> > > BR2_ARM_EABIHF=y
> > > BR2_PACKAGE_IMX_VPU=y
> > > 
> > > See Yocto equivalent:
> > > https://github.com/Freescale/meta-fsl-arm/blob/fido/recipes-
> > > multimedia/libfslcodec/libfslcodec.inc
> > > 
> > > Tested with the Linaro ARM 2014.09 toolchain.
> > > 
> > > Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> > > ---
> > > 
> > > Thanks to those options, I could see that:
> > > - lib_jpeg_dec_arm11_elinux_novpu.so isn't copied
> > > - lib_peq_arm11_elinux.so.1.fhw is copied instead of the fsw version
> > > 
> > > Regards,
> > > Gary
> > > 
> > > ---
> > >  package/libfslcodec/libfslcodec.mk | 8 ++++++++
> > >  1 file changed, 8 insertions(+)
> > > 
> > > diff --git a/package/libfslcodec/libfslcodec.mk b/package/libfslcodec/libfslcodec.mk
> > > index f8c6aa8..05e5edb 100644
> > > --- a/package/libfslcodec/libfslcodec.mk
> > > +++ b/package/libfslcodec/libfslcodec.mk
> > > @@ -13,6 +13,14 @@ LIBFSLCODEC_LICENSE = Freescale Semiconductor Software License Agreement, BSD-3c
> > >  LIBFSLCODEC_LICENSE_FILES = EULA COPYING
> > >  LIBFSLCODEC_REDISTRIBUTE = NO
> > >  
> > > +ifeq ($(BR2_ARM_EABIHF),y)
> > > +LIBFSLCODEC_CONF_OPTS += --enable-fhw
> > > +endif
> > 
> > What about adding --disable-fhw when not EABIhf?
> 
> The configure only looks for enable-fhw and therefore considers the
> features is disabled by default.
> 
> > > +ifeq ($(BR2_PACKAGE_IMX_VPU),y)
> > > +LIBFSLCODEC_CONF_OPTS += --enable-vpu
> > > +endif
> > 
> > Ditto when imx-vpu is not enabled?
> 
> Same here for the vpu option, configure only looks for the enable
> option.

Sorry for reviving this thread (again), but I was thinking that maybe we
could merge the two "missing configure options" patches from the series
since they do not depend on the libraries location fix.

Then I could offer another version of the series with only the path fix.
I'm still unclear on which option would get those patches approved. I
understand the symbolic links aren't great. I'm considering removing
gst-fsl-plugins for GStreamer0.10 since Yocto did it:
https://github.com/Freescale/meta-fsl-arm/commit/83b240e7

Let me know your thoughts.

Thanks,
Gary

  reply	other threads:[~2016-03-04  9:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 13:52 [Buildroot] [PATCH v2 0/4] libfsl*: fix install path + update conf opts Gary Bisson
2015-12-10 13:52 ` [Buildroot] [PATCH v2 1/4] libfslcodec: add install hooks to fix libraries path Gary Bisson
2015-12-13 20:31   ` Yann E. MORIN
2015-12-14 21:34     ` Gary Bisson
2015-12-13 20:36   ` Yann E. MORIN
2015-12-14 21:25     ` Gary Bisson
2016-01-24 20:55       ` Gary Bisson
2015-12-10 13:52 ` [Buildroot] [PATCH v2 2/4] libfslcodec: add missing configure options Gary Bisson
2015-12-13 20:32   ` Yann E. MORIN
2015-12-14 21:28     ` Gary Bisson
2016-03-04  9:17       ` Gary Bisson [this message]
2015-12-10 13:52 ` [Buildroot] [PATCH v2 3/4] libfslparser: add install hooks to fix libraries path Gary Bisson
2015-12-13 20:38   ` Yann E. MORIN
2015-12-10 13:52 ` [Buildroot] [PATCH v2 4/4] libfslparser: add missing configure options Gary Bisson
2015-12-13 20:39   ` Yann E. MORIN

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=20160304091758.GA20721@t450s.lan \
    --to=gary.bisson@boundarydevices.com \
    --cc=buildroot@busybox.net \
    /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