From 12ed05f89323fc27ad4a8ae24d9cdf371165beee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Thu, 7 May 2020 06:00:05 +0000 Subject: [PATCH] --print-cmd-oneline: document its existence in the usual locations --- README.adoc | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.adoc b/README.adoc index bc5db46..76a86f0 100644 --- a/README.adoc +++ b/README.adoc @@ -567,6 +567,8 @@ So observe that the command contains: * `+`: sign to differentiate it from program stdout, much like bash `-x` output. This is not a valid part of the generated Bash command however. * the actual command nicely, indented and with arguments broken one per line, but with continuing backslashes so you can just copy paste into a terminal ++ +For setups that don't support the newline e.g. <>, you can turn them off with `--print-cmd-oneline` * `;`: both a valid part of the Bash command, and a visual mark the end of the command For the specific case of running emulators such as QEMU, the last command is also automatically placed in a file for your convenience and later inspection: @@ -13244,7 +13246,13 @@ I recommend the following settings, tested in Eclipse 2019.09, Ubuntu 18.04: *** ./src/ in the source tree *** the ISA specific build directory which contains some self-generated stuff, e.g.: out/gem5/default/build/ARM -To run and GDB step debug the executable, just copy the full command line from the output `./run`, and configure it into Eclipse. +To run and GDB step debug the executable, just copy the <> from your run command (Eclipse does not like newlines for the arguments), e.g.: + +.... +./run --emulator gem5 --print-cmd-oneline +.... + +and configure it into Eclipse as usual. ==== gem5 Python C++ interaction