w8jcik edited a comment on issue #2206: URL: https://github.com/apache/incubator-nuttx/issues/2206#issuecomment-721264846
@Ouss4 regarding the issue of mine: > Please, make sure you are setting the paths correctly: "No directory at /home/user/dev/project/base/nuttx//src" I didn't put quotes over path in `defconfig`, apparently they are required by Kconfig. But then it was stopping on this: ``` make[1]: Entering directory '/home/user/dev/project/base/nuttx/arch/arm/src' make[2]: Entering directory '/home/user/dev/project/board/src' make[2]: *** No rule to make target 'libboard.a'. Stop. make[2]: Leaving directory '/home/user/dev/project/board/src' make[1]: *** [Makefile:168: board/libboard.a] Error 2 make[1]: Leaving directory '/home/user/dev/project/base/nuttx/arch/arm/src' make: *** [tools/Makefile.unix:425: nuttx] Error 2 ``` > I also notice that you copied a board that uses the `custom` and `drivers` directories. You need those too. You mean `common` right? Yes this was missing, thank you a lot for help :D `common` is not optional, `Makefile` needs to be there for build system to work. It is far from obvious. @v01d Regarding documentation and improvement. I think describing how to do it by copying an existing board is already great. Example don't need to be generic. Also I think this is typical workflow, you start with some similar development kit and change it in few places. I can describe what I did to make a custom copy, based on this particular board and you might review it. > we could make a "make-custom.sh" This is what web frameworks do, they have scripts to generate code based on templates. I think it would be perfectly fine to have such script which takes any board code, performs simple refactoring to avoid name collisions and gives you something which already runs. I will prepare it. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
