There are plugins part of collections that fail on target postinst so
manifest.ttl is not created (cross and on-target failed - there is nothing left
we can do).
That causes warnings: an lv2 path without manifest: tse tse.
Shut these up by deleting whole path on target - right - binaries without
manifest.ttk are useless blobs.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
distrho-ports ttl generation with qemu has alway been pain: For unknown reasons
some plugins caues qemu to run infinite. Up to now we could ignore particular
plugins by adding them to LV2_PLUGIN_BLACKLIST_QEMU} but since the affected
plugins change from time to time maintaining this turned into pain. So handle
infinit qemu runs as error. To achive we:
* add qemu-with-timeout-native which injects coreutils' 'timeout' into command
line by creatin wrappers for all qemu-* available
* rework qemu-ext-musicians.bbclass (was renamed to avoid conflicts with
meta-qt5-extra's qemu-ext)
* rework lv2-turtle-helper.bbclass and adjust logs
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
QEMU ttl-generation has been far from reliable for many reasons.
This class decides per lv2-plugin which way to go:
If qemu survives we are done - if not: try first boot.
Should have done done this much earlier because it is a major enhancement:
* It reduces 1st boot delay - only those plugins which failed at qemu are
handled at 1st boot - not all in affected recipe.
* Up to now it was maintainer's business to decide which way to go. Have seen
it more than once: Aargh QEMU creation failes -> move to 1st boot - or: Hey
QEMU has seen enhancements - is 1st boot still necessary: Try to remember how
to move (back) to qemu - aargh fails still...
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
