-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build-system: Allow out of tree BUILD_DIR #19600
Conversation
- Replace all users of `$(RIOTBASE)/build` with the already present `$(BUILD_DIR)` variable - Replace all users of `$(BUILD_DIR)/pkg` with the already present `$(PKGDIRBASE)` variable - Create a `CACHEDIR.TAG` file in the `$(BUILD_DIR)`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, works as advertised.
Note there's a typo (BUILDDIR instead of BUILD_DIR) in the PR description; not sure whether these are still committed in full text.
To those unfamiliar with the build system it may be surprising that BUILD_DIR is only used for pkg clones (while the actual building still happens in bin/
as usual); that behavior is not changed here.
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Thx :) |
Contribution description
$(RIOTBASE)/build
with the already present$(BUILD_DIR)
variable$(BUILD_DIR)/pkg
with the already present$(PKGDIRBASE)
variableCACHEDIR.TAG
file in the$(BUILD_DIR)
Testing procedure
BUILD_DIR=~/.cache/RIOT make -C tests/pkg/foobar
should work and foobar should be checked out into~/.cache/RIOT
rather than into the$(RIOTBASE)/build
CACHEDIR.TAG
file should be created in that directoryIssues/PRs references
None