Introduce a string define for the currently running OS, or execution
environment.
Originally, with old make build system, CONFIG_RTE_EXEC_ENV used to hold
this name string, but the variable seems to have been missed in the
meson build system, until commit cadb255e25d6 ("eal: add OS defines for
C conditional checks") which introduced the RTE_EXEC_ENV for a different
purpose. Now we can fix the docs with the new name reference.
Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
---
config/meson.build | 1 +
doc/guides/contributing/design.rst | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/config/meson.build b/config/meson.build
index f31fef216c..40f33816aa 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -20,6 +20,7 @@ foreach env, id:exec_envs
dpdk_conf.set10('RTE_EXEC_ENV_IS_' + env.to_upper(), (exec_env == env))
endforeach
dpdk_conf.set('RTE_EXEC_ENV', exec_envs[exec_env])
+dpdk_conf.set_quoted('RTE_EXEC_ENV_NAME', exec_env)
dpdk_conf.set('RTE_EXEC_ENV_' + exec_env.to_upper(), 1)
# MS linker requires special treatment.
diff --git a/doc/guides/contributing/design.rst
b/doc/guides/contributing/design.rst
index b724177ba1..5517613424 100644
--- a/doc/guides/contributing/design.rst
+++ b/doc/guides/contributing/design.rst
@@ -50,7 +50,7 @@ Per Execution Environment Sources
The following macro options can be used:
-* ``RTE_EXEC_ENV`` is a string that contains the name of the executive
environment.
+* ``RTE_EXEC_ENV_NAME`` is a string that contains the name of the executive
environment.
* ``RTE_EXEC_ENV_FREEBSD``, ``RTE_EXEC_ENV_LINUX`` or ``RTE_EXEC_ENV_WINDOWS``
are defined only if we are building for this execution environment.
Mbuf features
--
2.48.1
