As per request below, I’m happy to add a paragraph or two regarding this, but I 
am not sure where it should go?

 

It could be a section in “guides” or I could add it to the FAQ. What is 
preferred, assuming the Documentation folder in the repo is actually the right 
place for this of course?

 

Related to this, what is the significance of the cwiki 
(https://cwiki.apache.org/confluence/display/NUTTX) as that has a lot more 
information in it compared to the Nuttx distro’s Documentation folder, but is 
outdated and perhaps not maintained I think? The cwiki has information on 
custom app directory usage that could either be a source of info for a more 
complete “custom environment” guide or is the actually the intended place for 
the custom boards info I’ve been asked to add?

 

TIA,

 

TimH

 

 

From: hartmannathan <notificati...@github.com> 
Sent: 22 September 2022 15:00



@TimJTi <https://github.com/TimJTi>  :

Bear in mind that a distclean will wipe .config so any settings of paths etc. 
there become irrelevant…that’s what “did me in”!

I don't think we have good documentation on how to do custom-out-of-tree 
boards. Since you're working with an out-of-tree board, would you be willing to 
write something helpful for including in Documentation? It wouldn't have to be 
super long and detailed, just how to invoke the configure.sh script, which 
Kconfig options to set, and gotchas to avoid like distclean wiping the .config!

—
Reply to this email directly, view it on GitHub 
<https://github.com/apache/incubator-nuttx/pull/7103#issuecomment-1255066777> , 
or unsubscribe 
<https://github.com/notifications/unsubscribe-auth/ANQZJKNGKLF5PVP4I7SQESTV7RQ45ANCNFSM6AAAAAAQNUBOU4>
 .
You are receiving this because you were mentioned.  
<https://github.com/notifications/beacon/ANQZJKI4BDY4LRTNDNARIJDV7RQ45A5CNFSM6AAAAAAQNUBOU6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSKZ3GJS.gif>
 Message ID: <apache/incubator-nuttx/pull/7103/c1255066...@github.com 
<mailto:apache/incubator-nuttx/pull/7103/c1255066...@github.com> >

Reply via email to