From 3a8f2fcff5e828dfb4eb93932a25375dae8a1d4c 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?= <ciro.santilli@gmail.com>
Date: Mon, 30 Dec 2019 00:00:01 +0000
Subject: [PATCH] build: custom build directory with symlink technique

---
 README.adoc | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/README.adoc b/README.adoc
index 2d5920e..bcb9f16 100644
--- a/README.adoc
+++ b/README.adoc
@@ -20403,6 +20403,17 @@ Verify with:
 ls "$(./getvar buildroot_build_build_dir)"
 ....
 
+=== Custom build directory
+
+For now there is no way to change the build directory from `out/` (resp. `out.docker` for <<docker>.) to something else.
+
+However, if you just want to place the build storage in your hard drive and the source in your SSD, which is a good configuration if you are doing lots of builds, just create a symlink as:
+
+....
+mkdir -p /mnt/hd/linux-kernel-module-cheat-out
+ln -s out /mnt/hd/linux-kernel-module-cheat-out
+....
+
 === ccache
 
 https://en.wikipedia.org/wiki/Ccache[ccache] <<benchmark-builds,might>> save you a lot of re-build when you decide to <<clean-the-build>> or create a new <<build-variants,build variant>>.