I'm personally not fully convinced that this solves a real problem. As you pointed out, the build system does support external modules. Those do require a one-liner Makefile, but they don't need to list all the source by hand. This is less clutter when subfolders contain more than one C file. (But if a subfolder only contains one C file, creating the folder doesn't really help organizing the code, does it?)

More generally: The buildsystem is a pain in the ass to maintain as it is and few maintainers like to actually maintain it, most maintainers/developers much rather maintain/write C code than Makefiles. I'm personally reluctant on adding features that makes niche use cases a tiny bit more convenient. And again: I personally don't think that this indeed is an improvement over using external modules, anyway.

@mguetschow so far two maintainer have voted against this and there has been little interest. Do you want convert it into a draft and discuss / find a common ground?

@maribu only for applications, this feature can be beneficial. It allows for easy organization of folders and subfolders without having to create a module each time. It's also better for people discovering RIOT, as it seems easier to create one file and add SRC in it than to create a Makefile for each folder in an application.

I've come across the need for subfolder SRC for external packages as well, whose folder structure is not under RIOT's control.

We actually had a side-discussion with @plmorange over at mguetschow#1. They proposed a test for the BLOB in subfolder case and I was wondering if the application showcasing the subfolder functionality should actually rather go into tests/build_system instead of examples. WDYT?

Hmm, given how often this question popped up recently, I'd personally favor the example to increase visibility. But I think both are fine.

@plmorange I've now reworded the documentation to mainly link to the example. Also I found that there was already a test for testing blob files in subdirectories with tests/build_system/blob (this PR does not add support for it, it just followed the example of BLOB to pass down source files to recursive make invocations).

@maribu After checking the CI generated documentation, this should be ready for merge.

Murdock results

✔️ PASSED

518f75f docs: link to subfolders example in documentation

Artifacts

• Documentation preview

Thank you all!