patacongo commented on issue #9428: URL: https://github.com/apache/nuttx/issues/9428#issuecomment-1574119233
> @btashton AFAIK when you just create a new board (adding it to those 3 positions at Kconfig) you yet still need to have a boardname/configs/nsh/defconfig adapted to this new board. I think it is a dilemma: we cannot edit the defconfig, but we need a defconfig to use with ./tools/configure.sh to this new board. @patacongo am I missing something on this process? I am not aware of many specific problems with this. The procedure outlined by @TimJTi generally works. I am aware of a couple of things: - You can't switch between a POSIX build and a Windows build or vice versa. The path styles are too different. - If the average user edits the defconfig file by hand, it will probably break. - If you reconfigure the architecture, MCU, or board, then the symbolic links that are in place will be wrong. You need to exit the configuration, `make clean_context`, then `make menuconfig` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
