Am 08.04.19 um 08:55 schrieb richard.pur...@linuxfoundation.org:
On Mon, 2019-04-08 at 07:43 +0200, Stefan Herbrechtsmeier wrote:
Am 07.04.2019 23:35 schrieb richard.pur...@linuxfoundation.org:
You're saying A runtime depends on B and B runtime depends on A.
Yes, only the run time depends on
On Mon, 2019-04-08 at 07:43 +0200, Stefan Herbrechtsmeier wrote:
> Am 07.04.2019 23:35 schrieb richard.pur...@linuxfoundation.org:
> > You're saying A runtime depends on B and B runtime depends on A.
>
> Yes, only the run time depends on each other. This means the
> dependency doesn't exist
Hi,Am 07.04.2019 23:35 schrieb richard.pur...@linuxfoundation.org:On Sun, 2019-04-07 at 21:18 +0200, Stefan Herbrechtsmeier wrote:
> I'm working towards an integrated Node.js support without npm and
> have a problem with a circular dependency of do_populate_sysroot for
> the native build.
>
On Sun, 2019-04-07 at 21:18 +0200, Stefan Herbrechtsmeier wrote:
> I'm working towards an integrated Node.js support without npm and
> have a problem with a circular dependency of do_populate_sysroot for
> the native build.
>
> I have two recipes a.bb and b.bb which have no DEPENDS but a
>
Hi,
I'm working towards an integrated Node.js support without npm and have a
problem with a circular dependency of do_populate_sysroot for the native
build.
I have two recipes a.bb and b.bb which have no DEPENDS but a
RDEPENDS_${PN} between each other. This is no problem for a cross build
