In this video, I talk about how I'm going to organize the files of the project and I present the following structure:

build/
docs/
src/
    app/
    common/
    drivers/
    test/
    main.c
tools/
.clang-format
.gitignore
LICENSE
Makefile
README.md

Is this the best project structure? Well, take a look at the video for my opinion :)

0:00 What's the best structure?
1:33 Ex 1: The Pitchfork Layout
2:13 Ex 2: Canonical Project Structure
2:45 My project structure
7:35 Naming conventions
7:57 Last words

🌍 Links mentioned
The Pitchfork Layout - https://api.csswg.org/bikeshed/?force=1&url=https://raw.githubusercontent.com/vector-of-bool/pitchfork/develop/data/spec.bs
Canonical Project Structure - https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1204r0.html
https://cliutils.gitlab.io/modern-cmake/chapters/basics/structure.html
https://github.com/embeddedartistry/project-skeleton

⌨️ My development environment
https://www.artfulbytes.com/devenv

🌍 Links
GitHub - https://github.com/artfulbytes
Website - https://www.artfulbytes.com

👨‍💻 About me
Hi and welcome. I'm Niklas, an embedded systems engineer from Sweden. On this channel, I make practical videos about embedded systems or, in general terms, about building and programming hardware.

Artful Bytes

Explores best practices for organizing C/C++ embedded systems projects, covering directory structures like the Pitchfork layout and canonical project structure. Demonstrates a practical folder organization with separate directories for source code (app, drivers, common), external dependencies, documentation, tools, and build artifacts. Emphasizes that there's no perfect structure and it depends on project specifics and personal preference, especially for smaller projects with around 20 files.

The BEST Project Structure for C/C++/MCU | Embedded System Project Series #7