All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@googlemail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Does recipe specific sysrooot (or whatelse in current oe) break native dependencies?
Date: Mon, 13 Feb 2017 19:17:14 +0100	[thread overview]
Message-ID: <CALbNGRSg9p-MPjjmR4g5VDgfRTWONyuF5_s+t2G=o2wLxsVgXQ@mail.gmail.com> (raw)
In-Reply-To: <1487009117.27753.14.camel@linuxfoundation.org>

On Mon, Feb 13, 2017 at 7:05 PM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> To be clear, you can't depend on the build dependencies of some other
> recipe to be available to your recipe just because you DEPEND on it.
>
Yes I expected that my fault. Together with my hack on sysroot
alignments I think this is the end of kf5-kde in meta-qt5-extra.

Andreas


  reply	other threads:[~2017-02-13 18:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  0:26 Does recipe specific sysrooot (or whatelse in current oe) break native dependencies? Andreas Müller
2017-02-13 13:47 ` Andreas Müller
2017-02-13 14:36   ` Martin Jansa
2017-02-13 15:15     ` Andreas Müller
2017-02-13 15:24     ` Patrick Ohly
2017-02-13 15:32       ` Martin Jansa
2017-02-13 15:37         ` Patrick Ohly
2017-02-13 15:52           ` Max Krummenacher
2017-02-13 15:45       ` Andreas Müller
2017-02-13 18:05         ` Richard Purdie
2017-02-13 18:17           ` Andreas Müller [this message]
2017-03-05  0:55           ` Andreas Müller
2017-02-13 17:03       ` Patrick Ohly
2017-02-13 17:06         ` Patrick Ohly
2017-02-14 10:26         ` Patrick Ohly
2017-02-19 22:26           ` Richard Purdie
2017-02-20 14:14             ` Patrick Ohly

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='CALbNGRSg9p-MPjjmR4g5VDgfRTWONyuF5_s+t2G=o2wLxsVgXQ@mail.gmail.com' \
    --to=schnitzeltony@googlemail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.