From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] libungif: add native build
Date: Tue, 11 Jun 2013 17:50:59 +0200 [thread overview]
Message-ID: <20130611155059.GH3233@jama> (raw)
In-Reply-To: <CAF6bG8fEUCPMp1RYrEZCvfrYsco3Wp6CZwmf52mFy=UuAxXn2w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Mon, Jun 10, 2013 at 08:07:43PM +0300, Marko Lindqvist wrote:
> Motivation for this patch: newer versions of liberation-fonts need
> fontforge to build, and fontforge depends on libungif.
This line should be in comment above BBCLASSEXTEND or in commit message.
I'll add it to commit message, no need to send v2.
>
>
> - ML
>
>
> On 10 June 2013 20:06, Marko Lindqvist <cazfi74@gmail.com> wrote:
> > Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
> > ---
> > meta-oe/recipes-extended/libungif/libungif_4.1.3.bb | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta-oe/recipes-extended/libungif/libungif_4.1.3.bb b/meta-oe/recipes-extended/libungif/libungif_4.1.3.bb
> > index 0e9bf9b..3e4b78b 100644
> > --- a/meta-oe/recipes-extended/libungif/libungif_4.1.3.bb
> > +++ b/meta-oe/recipes-extended/libungif/libungif_4.1.3.bb
> > @@ -12,3 +12,5 @@ inherit autotools lib_package
> > PACKAGES =+ "${PN}-utils"
> >
> > FILES_${PN}-utils = "${bindir}/*"
> > +
> > +BBCLASSEXTEND = "native"
> > --
> > 1.7.10.4
> >
> _______________________________________________
> 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: 205 bytes --]
prev parent reply other threads:[~2013-06-11 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 17:06 [meta-oe][PATCH] libungif: add native build Marko Lindqvist
2013-06-10 17:07 ` Marko Lindqvist
2013-06-11 15:50 ` Martin Jansa [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=20130611155059.GH3233@jama \
--to=martin.jansa@gmail.com \
--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