Skip to contentSkip to conversation

No recipe for recipes-tweaks/qt5/qtbase_5.2.1.bbappend

DISCUSSION Steffen Sledz 2 participants 2 messages Jun 6, 2014

lore
Share & tools
lore
#0 lore raw

We're currently switching to th daisy branches.

According to [1] meta-angstrom depends on openembedded-core, meta-oe, and meta-systemd layers.

The angstrom-v2014.06-yocto1.6 branch of meta-angstrom contains recipes-tweaks/qt5/qtbase_5.2.1.bbappend. But there's no qtbase recipe in the required layers. So we get

---------------> snip <-------------------
ERROR: No recipes available for:
/pm/sledz/hipos-dfe/meta-angstrom/recipes-tweaks/qt5/qtbase_5.2.1.bbappend
ERROR: Command execution failed: Exited with 1
---------------> snip <-------------------

A bug in the daisy branch of meta-angstrom? An incomplete dependency list in [1]?

[1] <http://layers.openembedded.org/layerindex/branch/master/layer/meta-angstrom/>

Regards,
Steffen

Signature · 7 lines
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
#1 lore raw
Quoted 6 lines · Steffen Sledz

We're currently switching to th daisy branches.

According to [1] meta-angstrom depends on openembedded-core, meta-oe, and meta-systemd layers.

The angstrom-v2014.06-yocto1.6 branch of meta-angstrom contains recipes-tweaks/qt5/qtbase_5.2.1.bbappend. But there's no qtbase recipe in the required layers. So we get

Quoted 9 lines

---------------> snip <-------------------
ERROR: No recipes available for:
/pm/sledz/hipos-dfe/meta-angstrom/recipes-tweaks/qt5/qtbase_5.2.1.bbappend
ERROR: Command execution failed: Exited with 1
---------------> snip <-------------------

A bug in the daisy branch of meta-angstrom?
An incomplete dependency list in [1]?

Likely you need to add meta-qt5, but this is up to the maintainer of meta-angstrom, since it's a manual process currently. It should be in meta-angstrom's documentation and setup info.

Sau!

Quoted 5 lines

[1] <http://layers.openembedded.org/layerindex/branch/master/layer/meta-angstrom/>

Regards,
Steffen