Saahil Shaw commented on a discussion on cpukit/include/rtems/shellconfig.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1563#note_162112 > extern rtems_shell_cmd_t rtems_shell_MALLOC_INFO_Command; > extern rtems_shell_cmd_t rtems_shell_RTRACE_Command; > extern rtems_shell_cmd_t rtems_shell_PRIO_Command; > -#if RTEMS_NETWORKING > - extern rtems_shell_cmd_t rtems_shell_IFCONFIG_Command; > - extern rtems_shell_cmd_t rtems_shell_ROUTE_Command; > - extern rtems_shell_cmd_t rtems_shell_NETSTATS_Command; > - extern rtems_shell_cmd_t rtems_shell_PING_Command; > -#endif I looked into rtems-libbsd and rtems-lwip to see how they handle shell command declaration. ### rtems-libbsd: 1) It has its own dedicated header in \<include/rtems/netcmds-config.h\> . This header exports all the necessary shell command declarations. 2) Applications and testsuites include both netcmds-config.h and the core RTEMS shellconfig,h to construct the shell command table. ### rtems-lwip: 1) I didn't find any shell commands with rtems_shell_cmd_t. I believe it doesn't provide built-in shell commands and hence doesn't has needs/uses a shellconfig header. I will move all the shell command declarations within a header in rtems-net-legacy. (likely rtems_bsdnet.h) and once its done, removing all the declarations and mentions of RTEMS_NETWORKING from core RTEMS repo will cause no issues. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1563#note_162112 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-7ljbhubbibvpztm9i5f3av2p2-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
