summaryrefslogtreecommitdiff
path: root/meta/recipes-qt/qt4
diff options
context:
space:
mode:
authorLaurentiu Palcu <laurentiu.palcu@intel.com>2013-05-14 14:23:29 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-05-16 00:09:41 +0300
commit0f6c0ed7888603c8d026a671f2acb1515ce799bf (patch)
tree7ec4ac551680f4450b25e82f87c7025c07d7e519 /meta/recipes-qt/qt4
parent18d3e5eb9102a984d00837f8fec16fda522c511a (diff)
downloadopenembedded-core-0f6c0ed7888603c8d026a671f2acb1515ce799bf.tar.gz
openembedded-core-0f6c0ed7888603c8d026a671f2acb1515ce799bf.tar.bz2
openembedded-core-0f6c0ed7888603c8d026a671f2acb1515ce799bf.zip
systemd: make udev-hwdb postinstall run on host
Run udevadm inside qemu in order to create the HW database index on host. The alternative would be to build a native version of udevadm which would imply several things: split out systemd recipe, create a common inc file and create a new recipe for udevadm native. However, this latter solution might also add up to the build time (the native recipe would need to run configure, make udevadm, install), besides the time spent in the actual postinstall... So, having the postinstall run through qemu is a good trade-off. [YOCTO #4341] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/recipes-qt/qt4')
0 files changed, 0 insertions, 0 deletions