feat: add optional BUILD_DIR Makefile variable to place build outputs in a separate directory#115
Merged
cnlohr merged 2 commits intocnlohr:masterfrom Nov 15, 2025
Merged
Conversation
Owner
|
Looks good. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce an optional variable so build artifacts can be placed in a dedicated directory
This pull request updates the
Makefileto add support for specifying an output build directory via the newBUILD_DIRvariable. All build artifacts, including binaries, APKs, and intermediate files, are now placed in the specifiedBUILD_DIR. This improves build organization and makes it easier to manage output files.What this PR does