Skip to content

doc/guides/finding_modules: make inclusion clearer#22485

Open
AnnsAnns wants to merge 1 commit into
RIOT-OS:masterfrom
AnnsAnns:make_placement_clear
Open

doc/guides/finding_modules: make inclusion clearer#22485
AnnsAnns wants to merge 1 commit into
RIOT-OS:masterfrom
AnnsAnns:make_placement_clear

Conversation

@AnnsAnns

Copy link
Copy Markdown
Member

Contribution description

After somebody new to RIOT tried to include a package following the tutorial, they assumed that it can be anywhere within the Makefile (which, to be fair, the guide also never make clear before). Naturally the build system gets really confused because the package will never be resolved. This should hopefully stop that from happening in the future (if people read the guide :P)

Testing procedure

read text

Issues/PRs references

Declaration of AI-Tools / LLMs usage:

AI-Tools / LLMs that were used are:

  • none

@AnnsAnns
AnnsAnns requested review from aabadie and jia200x as code owners July 19, 2026 11:15
@github-actions github-actions Bot added the Area: doc Area: Documentation label Jul 19, 2026
@AnnsAnns AnnsAnns added CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs AI: None Stated AI was not (stated to be) used in this PR/Issue labels Jul 19, 2026
@riot-ci

riot-ci commented Jul 19, 2026

Copy link
Copy Markdown

Murdock results

✔️ PASSED

78e2a8b doc/guides/finding_modules: make inclusion clearer

Success Failures Total Runtime
1 0 1 01m:17s

Artifacts

@crasbe crasbe added the Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation label Jul 19, 2026
Comment on lines +93 to +95
Make sure to always include stuff before `include $(RIOTBASE)/Makefile.include` in your `Makefile`.
This is important because the `Makefile.include` file will do a lot of build system setup
and doing it after that will not work as expected and cause confusing errors.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Make sure to always include stuff before `include $(RIOTBASE)/Makefile.include` in your `Makefile`.
This is important because the `Makefile.include` file will do a lot of build system setup
and doing it after that will not work as expected and cause confusing errors.
Make sure that `include $(RIOTBASE)/Makefile.include` is the very last line in your `Makefile`.
This is important because the `Makefile.include` file is responsible for setting up the
build process and kicks off the dependency resolution. Everything included and defined
after this line will not be considered by this process and therefore will either
not work at all, not work as expected and/or cause confusing errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI: None Stated AI was not (stated to be) used in this PR/Issue Area: doc Area: Documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants