On Wed, 2017-01-04 at 11:01 +0100, Patrick Ohly wrote: > On Wed, 2016-12-28 at 13:38 -0800, Ricardo Neri wrote: > > > do_install_class-target() { > > > - OVMF_DIR_SUFFIX="X64" > > > - if [ "${TARGET_ARCH}" != "x86_64" ] ; then > > > - OVMF_DIR_SUFFIX="Ia32" # Note the different capitalization > > > - fi > > > + # Traditional location. > > > install -d ${D}${datadir}/ovmf > > > + install -m 0755 ${WORKDIR}/ovmf/OVMF.fd ${D}${datadir}/ovmf/bios.bin > > > > Now that I think about it. Installing here does not sever any purpose. > > Thus, I think this can be removed by perhaps doing do_install[noexec] = > > "1" > > I was trying not to break traditional usage patterns. If we keep the > "bios" runqemu parameters, then we should also keep the bios.bin file.
I think OVMF is not a traditional recipe. There are two use cases to ponder. 1) a Yocto Project disk image wants to include OVMF along with qemu to run a VM from the YP image. 2) we want to run a YP image in a host system. I am not sure if someone is interested in 1) and I think your use case and LUV's is 2). I think that putting things in the deploy directory makes more sense because, as you said, these images will be written to. I reckon the the "bios" parameters in runqemu should look there. This is not a must for this patchset but something nice to have. Thanks and BR, Ricardo -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core