From 98708821be1ad4c75e07a3ab6e799b80a31ed7c7 Mon Sep 17 00:00:00 2001
From: Extremesecrecy <10959169+extremesecrecy@users.noreply.github.com>
Date: Thu, 24 Jul 2025 10:09:09 -0700
Subject: [PATCH] Housekeeping BuildSystem update

Documented how to build only the command-line tool by running cmake --build build --target pipedalconfig in the build instructions
---
 docs/TheBuildSystem.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/TheBuildSystem.md b/docs/TheBuildSystem.md
index 9b16433..9971286 100644
--- a/docs/TheBuildSystem.md
+++ b/docs/TheBuildSystem.md
@@ -20,10 +20,17 @@ the following shell scripts have been provided in the root of the project.
 
     ./mk.sh   # Build all targets (release build)
     
-    sudo ./install.sh   # Deploy all targets 
+    sudo ./install.sh   # Deploy all targets
     
     sudo ./makePackage.sh    # Build a .deb file for distribution.
     
+	If you only need the `pipedalconfig` command line tool and want to skip the
+	web client build, you can build it directly using:
+
+	```bash
+	cmake --build build --target pipedalconfig
+	```	
+	
 If you are using a development environment other than Visual Studio Code, it should be fairly straightforward to figure out how
 to incorporate the PiPedal build procedure into your IDE workflow by using the contents of the build shell scripts as a model.