On 11/06/13 06:08, Jordan Justen wrote: > If the user has set the QEMU_COMMAND environment variable, > then use it when running QEMU. This can be useful for running > OVMF with development builds of QEMU. > > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Jordan Justen <[email protected]> > --- > OvmfPkg/build.sh | 14 ++++++++++++-- > 1 file changed, 12 insertions(+), 2 deletions(-) > > diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh > index d35d2e0..f3eb97c 100755 > --- a/OvmfPkg/build.sh > +++ b/OvmfPkg/build.sh > @@ -143,7 +143,12 @@ done > case $PROCESSOR in > IA32) > Processor=Ia32 > - if [ -x `which qemu-system-i386` ]; then > + if [ -n "$QEMU_COMMAND" ]; then > + # > + # The user set the QEMU_COMMAND variable. We'll use it to run QEMU. > + # > + : > + elif [ -x `which qemu-system-i386` ]; then > QEMU_COMMAND=qemu-system-i386 > elif [ -x `which qemu-system-x86_64` ]; then > QEMU_COMMAND=qemu-system-x86_64 > @@ -156,7 +161,12 @@ case $PROCESSOR in > ;; > X64) > Processor=X64 > - QEMU_COMMAND=qemu-system-x86_64 > + if [ -z "$QEMU_COMMAND" ]; then > + # > + # The user didn't set the QEMU_COMMAND variable. > + # > + QEMU_COMMAND=qemu-system-x86_64 > + fi > ;; > *) > echo Unsupported processor architecture: $PROCESSOR >
Reviewed-by: Laszlo Ersek <[email protected]> ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
