Deprecate the misnamed YOTTA_CFG_MTRACE_TMP_LINE_LENGTH flag. #43
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.
Configuring the tmp line length value through config.json in yotta requires defining a separate "mtrace" group, because the name of the flag doesn't follow the 'YOTTA_CFG_MBED_TRACE_' pattern.
This allows configuring the tmp line length in the same group mbed-trace is enabled in.
(The name of the flag seems to be a relic of the time the name of the library was still being decided.
For some reason it wasn't changed with the other ones when 'mbed-trace' was decided on.)