From 17e8021a430494380dac57acedd1a9c0d3bb7764 Mon Sep 17 00:00:00 2001
From: Imbus <>
Date: Tue, 2 Sep 2025 04:49:54 +0200
Subject: [PATCH] Readme, note about dependencies

---
 README.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/README.md b/README.md
index 8d95e18..c7f3879 100644
--- a/README.md
+++ b/README.md
@@ -26,6 +26,14 @@ On a linux machine, make sure that you have `make` and `curl` in path. The rest
 of the tooling (gcc, qemu) will be handled by the build system. For extra convenience,
 you could also use `bear` for generating "compile_commands.json". This is useful for helping
 clangd pick up the correct paths, and will result in better in-editor diagnostics and warnings.
+For development, `clang-format` and `find` will also be useful.  
+  
+In short, for debian/redhat:
+```sh
+sudo apt install bear make curl clang-format find
+sudo dnf install bear make curl clang-format find
+```
+Im sure its the same on alpine/arch and friends. You're a linux user, put on those big boy pants and figure it out.
 
 ```sh
 make get_toolchain # Dont worry, is will land locally inside project directory