-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
MCUMGR_LOG build error #15713
Comments
That file doesn't seem to have ever existed. It might be that this has never been correctly tested. @ccollins476ad can you shed some light? |
Relabeled as enhancement since this has never been actually supported. Contributors welcome to address this. |
It appears that when this was originally contributed in apache/mynewt-mcumgr@96dc9d8 it referenced a managed log infrastructure that was not part of the contribution. I can find no history of it ever being in Zephyr, nor elsewhere. The dependency reference was removed from Zephyr in 4db7cce leaving the mistaken impression that It would probably be good to remove the entire cmd/log_mgmt/port/zephyr hierarchy and everything referencing it from upstream mcumgr, and from Zephyr itself. It's continued presence (and marking as "currently disabled" in the Zephyr documentation without explanation) will confuse and waste the time of users interested in getting log information off a device. |
log related commands have never been supported by mcumgr on Zephyr. This commit removes configuration options that might have been misleading for developers. Fixes zephyrproject-rtos#15713 Signed-off-by: Dominik Ermel <[email protected]>
Describe the bug
when I config CONFIG_MCUMGR_CMD_LOG_MGMT=y, mcumgr log will build error:
error 1: create makefile fail:
I fix it by modify zephyr/ext/lib/mgmt/mcumgr/cmd/log_mgmt/CMakeLists.txt
then disapper
error 2 can't find file:
I search zephyr path & west path, can't find mdlog, but it be used by zephyr_log_mgmt.c.
It's a bug? or I config have some error?
Please give me some suggest, thanks!
The text was updated successfully, but these errors were encountered: