From e10e4d19e3c02a9d251499172a65c77c59e15a67 Mon Sep 17 00:00:00 2001 From: Luca Ceresoli Date: Mon, 18 Sep 2017 11:34:18 +0200 Subject: [PATCH] docs/manual: fix typo Signed-off-by: Luca Ceresoli Signed-off-by: Peter Korsgaard --- docs/manual/using-buildroot-development.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/manual/using-buildroot-development.txt b/docs/manual/using-buildroot-development.txt index e167849cdc..1071de5132 100644 --- a/docs/manual/using-buildroot-development.txt +++ b/docs/manual/using-buildroot-development.txt @@ -50,11 +50,11 @@ BUSYBOX_OVERRIDE_SRCDIR = /home/bob/busybox/ When Buildroot finds that for a given package, an +_OVERRIDE_SRCDIR+ has been defined, it will no longer attempt to download, extract and patch the package. Instead, it will directly use -the source code available in in the specified directory and +make -clean+ will not touch this directory. This allows to point Buildroot -to your own directories, that can be managed by Git, Subversion, or -any other version control system. To achieve this, Buildroot will use -_rsync_ to copy the source code of the component from the specified +the source code available in the specified directory and +make clean+ +will not touch this directory. This allows to point Buildroot to your +own directories, that can be managed by Git, Subversion, or any other +version control system. To achieve this, Buildroot will use _rsync_ to +copy the source code of the component from the specified +_OVERRIDE_SRCDIR+ to +output/build/-custom/+. This mechanism is best used in conjunction with the +make -- 2.30.2