[OE-core] should one be free to invoke "runqemu" outside the context of a build?

[Robert P. J. Day]

  goofing around with "runqemu" and noticed this in the usage:

   echo "Examples:"
    echo "  $MYNAME qemuarm"
    echo "  $MYNAME qemux86-64 core-image-sato ext3"

if i try that last example the way i've set up a toolchain and am
trying to run the pre-built yocto qemu images, i get:

$ runqemu qemuarm core-image-minimal ext3
Assuming core-image-minimal really means
/opt/poky/1.3/deploy/images/core-image-minimal-qemuarm.ext3

Continuing with the following parameters:
KERNEL: [/opt/poky/1.3/deploy/images/zImage-qemuarm.bin]
ROOTFS: [/opt/poky/1.3/deploy/images/core-image-minimal-qemuarm.ext3]
FSTYPE: [ext3]
Setting up tap interface under sudo
[sudo] password for rpjday:
Acquiring lockfile for tap0...
Error: Kernel image file
/opt/poky/1.3/deploy/images/zImage-qemuarm.bin doesn't exist
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'
$

  obviously, the simple argument "ext3" is expanded into something
involving pathname components "deploy/images", which means that
particular sample usage makes sense *only* in the context of a current
build directory.

  but (as i've done), what if one simply wants to download the
pre-built images and see what they're like to run?  in a case like
that, that sample usage clearly isn't going to work.

  it might be useful to change the usage info to make that clear.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================