refactor: Improve makefile build commands #19498
Merged
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.
This does a couple things:
LTS_CPU=1
e.g.make build-release LTS_CPU=1
to build a lts-cpu variant.make build ARGS="--no-default-features"
.debug
nodebug-release
release
debug-release
dist-release
Almost all the time you want
debug
, which is justmake build
. If you are investigating performance, you wantmake build-release
.The remaining profiles are more niche. Use
dist-release
to exactly match the optimization we use when distributing, which is not necessary most of the time. Thenodebug
/debug
variants ofrelease
exist because I found it adds significant (30-60 sec) compile time between them (all fresh compiles):Use
nodebug
if you are iterating on something performance-sensitive but you've already done profiling so you know what to improve without needing further profiling. Usedebug
when hunting down a bug with a debugger that only occurs in release mode.