Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Jack Mitchell <jack@embed.me.uk>
Subject: Re: [PATCH] libjpeg-turbo: fix libturbojpeg packaging
Date: Wed, 2 Sep 2015 15:23:30 +0200	[thread overview]
Message-ID: <20150902132330.GC2470@jama> (raw)
In-Reply-To: <1441192259-20483-1-git-send-email-ml@communistcode.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2513 bytes --]

On Wed, Sep 02, 2015 at 12:10:59PM +0100, ml@communistcode.co.uk wrote:
> From: Jack Mitchell <jack@embed.me.uk>
> 
> put libjpegturbo library files and headers into correct packages rather
> than them being in the main libjpeg-turbo package.
> 
> remove INSANE_SKIP[dev-so]
> move .so, .a into -dev package
> move .la into -staticdev
> move .so.* into main library package
> 
> Signed-off-by: Jack Mitchell <jack@embed.me.uk>
> ---
>  meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.0.bb | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.0.bb b/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.0.bb
> index 8e214c9..16f62c5 100644
> --- a/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.0.bb
> +++ b/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.0.bb
> @@ -25,13 +25,14 @@ inherit autotools pkgconfig
>  
>  EXTRA_OECONF = "--with-jpeg8 "
>  
> -PACKAGES =+ "jpeg-tools libturbojpeg"
> +PACKAGES =+ "jpeg-tools libturbojpeg libturbojpeg-staticdev libturbojpeg-dev"
>  
>  DESCRIPTION_jpeg-tools = "The jpeg-tools package includes client programs to access libjpeg functionality.  These tools allow for the compression, decompression, transformation and display of JPEG files and benchmarking of the libjpeg library."
>  FILES_jpeg-tools = "${bindir}/*"
>  
> -FILES_libturbojpeg = "${libdir}/libturbojpeg.so"
> -INSANE_SKIP_libturbojpeg = "dev-so"
> +FILES_libturbojpeg = "${libdir}/libturbojpeg.so.*"

You can use libturbojpeg*${SOLIBS}

> +FILES_libturbojpeg-staticdev = "${libdir}/libturbojpeg.a"
> +FILES_libturbojpeg-dev = "${libdir}/libturbojpeg.la ${incdir}/turbojpeg.h ${libdir}/libturbojpeg.so"

libturbojpeg.so -> lib*${SOLIBSDEV} and we should use only one
-dev/-staticdev package for recipe (people who need to install
-dev/-staticdef package to rootfs usually don't mind getting few more
files installed as well).

But more importantly I don't understand how dev-so and other files got
into libturbojpeg package when it's using:

FILES_libturbojpeg = "${libdir}/libturbojpeg.so"

So I think the problem is somewhere else.
>  
>  BBCLASSEXTEND = "native"
>  DEPENDS = "nasm-native"
> -- 
> 2.5.1
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-09-02 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 11:10 [PATCH] libjpeg-turbo: fix libturbojpeg packaging ml
2015-09-02 13:23 ` Martin Jansa [this message]
2015-09-02 18:25   ` Khem Raj
2015-09-02 18:49     ` Martin Jansa
2015-09-03  9:29   ` Koen Kooi

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=20150902132330.GC2470@jama \
    --to=martin.jansa@gmail.com \
    --cc=jack@embed.me.uk \
    --cc=openembedded-devel@lists.openembedded.org \
    /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