All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Christian Eggers <ceggers@arri.de>,
	openembedded-devel@lists.openembedded.org
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
	"Andreas Müller" <schnitzeltony@gmail.com>
Subject: Re: [oe] [meta-oe][PATCH 2/4] ttf-dejavu: Extend for native and nativesdk
Date: Fri, 12 Jun 2020 16:38:44 -0700	[thread overview]
Message-ID: <6059723.tB9ojmTFGE@tyche> (raw)
In-Reply-To: <CALbNGRSJb8fUA23=C+ecLN5-VpXb=sh2=cBCy8nR1_2shuBS4Q@mail.gmail.com>

On Tuesday, June 9, 2020 6:21:50 AM PDT Andreas Müller wrote:
> On Tue, Jun 9, 2020 at 3:06 PM Christian Eggers <ceggers@arri.de> wrote:
> > When using doxygen together with the "dot" tool (graphviz package), a
> > ttf font package is additionally required.
> > 
> > Probably this change could also be moved to ttf.inc.
> 
> Extend an allarch recipe to native - sounds odd to me...
> 

bbclassextend will convert the dependencies to be PN-<bbclassextend> and thats 
where this will help. But ideally I think I agree, it would be better to sort 
out dependencies such that native/nativesdk can depend on PN for allarch ones.

> Andreas





  reply	other threads:[~2020-06-13  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09  6:32 [meta-oe][PATCH 0/4] Extend graphviz and mscgen for nativesdk Christian Eggers
2020-06-09  6:32 ` [meta-oe][PATCH 1/4] graphviz: Extend " Christian Eggers
2020-06-09  6:32 ` [meta-oe][PATCH 2/4] ttf-dejavu: Extend for native and nativesdk Christian Eggers
2020-06-09 13:21   ` [oe] " Andreas Müller
2020-06-12 23:38     ` Khem Raj [this message]
2020-06-15  9:55     ` Christian Eggers
2020-06-09  6:32 ` [meta-oe][PATCH 3/4] gd: " Christian Eggers
2020-06-09  6:32 ` [meta-oe][PATCH 4/4] mscgen: " Christian Eggers

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=6059723.tB9ojmTFGE@tyche \
    --to=raj.khem@gmail.com \
    --cc=ceggers@arri.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=schnitzeltony@gmail.com \
    /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.