From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Knight <james.d.knight@live.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 3/3] board/qemu/start-qemu.sh.in: support launching with host system's qemu
Date: Mon, 10 Apr 2023 23:15:24 +0200 [thread overview]
Message-ID: <20230410211524.GQ2819@scaer> (raw)
In-Reply-To: <SN4P221MB06829533040263705CA5B624A0969@SN4P221MB0682.NAMP221.PROD.OUTLOOK.COM>
James, All,
On 2023-04-07 01:21 -0400, James Knight spake thusly:
> Provides the ability to use a host system's QEMU. While a Buildroot
> generated QEMU should work for most cases, a developer may wish to use
> the system's QEMU for options which may not have been configured in the
> Buildroot's QEMU build (e.g. configuring a different display mode).
>
> Signed-off-by: James Knight <james.d.knight@live.com>
> ---
> Changes v1 -> v2:
> - From the original patch, this third patch now only contains changes
> related to permitting a system QEMU usage.
> - Change from `--host` to `--use-system-qemu` (suggested by Romain).
> ---
> board/qemu/start-qemu.sh.in | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/board/qemu/start-qemu.sh.in b/board/qemu/start-qemu.sh.in
> index dd387507f8867778ec73f49d769679dcd0956fd4..51f15b3ecdfdc8151caeae90582ad1142d122e69 100644
> --- a/board/qemu/start-qemu.sh.in
> +++ b/board/qemu/start-qemu.sh.in
> @@ -4,9 +4,11 @@ BINARIES_DIR="${0%/*}/"
> cd ${BINARIES_DIR}
>
> mode_serial=0
> +mode_sys_qemu=0
> while [ "$1" ]; do
> case "$1" in
> --serial-only|serial-only) mode_serial=1; shift;;
> + --use-system-qemu) mode_sys_qemu=1; shift;;
I also swotched to false/true here...
> --) shift; break;;
> *) echo "unknown option: $1" 1>&2; exit 1;;
> esac
> @@ -22,6 +24,9 @@ if [ "$*" ]; then
> echo "(warning) unsupported options: $*"
> fi
>
> -export PATH="${HOST_DIR}/bin:${PATH}"
> +if [ $mode_sys_qemu -ne 1 ]; then
... and here.
Applied to master, thanks.
Regards,
Yann E. MORIN.
> + export PATH="${HOST_DIR}/bin:${PATH}"
> +fi
> +
> exec VAR_QEMU_CMD_LINE ${EXTRA_ARGS} "$@"
> )
> --
> 2.39.1.windows.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-04-10 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230407052108.1696-1-james.d.knight@live.com>
2023-04-07 5:21 ` [Buildroot] [PATCH v2 2/3] board/qemu/start-qemu.sh.in: rework argument handling James Knight
2023-04-10 21:14 ` Yann E. MORIN
2023-04-07 5:21 ` [Buildroot] [PATCH v2 3/3] board/qemu/start-qemu.sh.in: support launching with host system's qemu James Knight
2023-04-10 21:15 ` Yann E. MORIN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230410211524.GQ2819@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=james.d.knight@live.com \
--cc=romain.naour@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox