aboutsummaryrefslogtreecommitdiff
path: root/doc/build
diff options
context:
space:
mode:
authorTom Rini2022-11-19 18:45:43 -0500
committerTom Rini2022-12-05 16:11:50 -0500
commitd948c8988c212bc8fe94db556b7ef265d2e96452 (patch)
treed4f2e93ee6b6eeb9b5a7c3cf772a9f2407b25b97 /doc/build
parent17f13e7119cc628bc26edf12252794770247df63 (diff)
sandbox: Rework how SDL is enabled / disabled
Given that we can use Kconfig logic directly to see if we have a program available on the host or not, change from passing NO_SDL to instead controlling CONFIG_SANDBOX_SDL in Kconfig directly. Introduce CONFIG_HOST_HAS_SDL as the way to test for sdl2-config and default CONFIG_SANDBOX_SDL on if we have that, or not. Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/build')
-rw-r--r--doc/build/tools.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/tools.rst b/doc/build/tools.rst
index c06f9152741..ec017229258 100644
--- a/doc/build/tools.rst
+++ b/doc/build/tools.rst
@@ -44,4 +44,4 @@ applications using a linux toolchain (gcc, bash, etc), targeting respectively
Launch the MSYS2 shell of the MSYS2 environment, and do the following::
$ make tools-only_defconfig
- $ make tools-only NO_SDL=1
+ $ make tools-only