Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libjpeg-turbo: fix libturbojpeg packaging
Date: Thu, 3 Sep 2015 11:29:44 +0200	[thread overview]
Message-ID: <ms93u8$45f$1@ger.gmane.org> (raw)
In-Reply-To: <20150902132330.GC2470@jama>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 02-09-15 om 15:23 schreef Martin Jansa:
> 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).

The "one -dev package to rule them all" lead to the "why does my rootfs
suddenly have systemd?!?!" earlier on. I advocate doing the proper splitting
like Jack does above, but with a small change: RDEPENDS_${PN}-dev +=
libturbojpeg-dev.
I admit that I don't have a strong opinion on the split in this specific
case, though.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFV6BMIMkyGM64RGpERAlZ3AJ9VqAy7Y+dNKcouMHPdUoh/9YqjbgCfVhAz
3vd4pqQozNXCBvm7ULIyMcI=
=UfL0
-----END PGP SIGNATURE-----



      parent reply	other threads:[~2015-09-03  9:30 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
2015-09-02 18:25   ` Khem Raj
2015-09-02 18:49     ` Martin Jansa
2015-09-03  9:29   ` Koen Kooi [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='ms93u8$45f$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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