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 20:49:40 +0200 [thread overview]
Message-ID: <20150902184940.GH2470@jama> (raw)
In-Reply-To: <CAMKF1spnATGUXbzt8ymqgPjtqR2tkaeRybMiMG5MfgV-43GDCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Wed, Sep 02, 2015 at 11:25:07AM -0700, Khem Raj wrote:
> On Wed, Sep 2, 2015 at 6:23 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > 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.
>
> it uses PACKAGES =+ "jpeg-tools libturbojpeg" that could precede the
> default packages
yes, but FILES_libturbojpeg includes only one file, not the headers and
the staticdev files, so changing it to
FILES_libturbojpeg = "${libdir}/libturbojpeg${SOLIBS}"
should be enough to remove that INSANE_SKIP.
> --
> _______________________________________________
> 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 --]
next prev parent reply other threads:[~2015-09-02 18:49 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 [this message]
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=20150902184940.GH2470@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.