[V1,2/4] doc/dts_gsg: removed makefile from user guide document

Message ID 20211117085444.2254-2-junx.dong@intel.com (mailing list archive)
State Superseded
Headers
Series [V1,1/4] executions/execution*: removed makefile from configure file |

Commit Message

Jun Dong Nov. 17, 2021, 8:54 a.m. UTC
  Signed-off-by: DongJunX <junx.dong@intel.com>
---
 doc/dts_gsg/usr_guide/usage.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
  

Comments

Owen Hilyard Jan. 12, 2022, 3:16 p.m. UTC | #1
>
> +* build_type: the tool for building DPDK, it can be meson.
>

Since there is only one valid option for this, it might make sense to
either remove it or change it to:

* build_type: [IGNORED] Selects which build tool to use. Currently always
uses meson.
  

Patch

diff --git a/doc/dts_gsg/usr_guide/usage.rst b/doc/dts_gsg/usr_guide/usage.rst
index ef729a9e..7f0b5e0f 100644
--- a/doc/dts_gsg/usr_guide/usage.rst
+++ b/doc/dts_gsg/usr_guide/usage.rst
@@ -24,7 +24,7 @@  First of all, you must configure execution.cfg as below:
 
 * crbs: IP address of the DUT. The detail information is defined in file conf/crbs.cfg.
 * drivername: the driver devices used by DPDK bound to.
-* build_type: the tool for building DPDK, it can be meson and makefile. DPDK 20.11+ only uses meson and ninja.
+* build_type: the tool for building DPDK, it can be meson.
 * rx_mode: vector instructions used in tests, it can be novector/sse/avx2/avx512. it is optional, if not set, dpdk uses avx2 by default.
 * test_suites: test suites and cases that to be executed. use ``:`` to separate suite and it's cases and use ``\`` to separate different cases.
 * targets: DPDK targets to be tested.