Re: More bletiny

2016-10-28 Thread Adam
The best way I've found to get an exhaustive list of syscfg definitions (and their values) that apply to your project config is to just go look at the generated syscfg.h file in: bin/targets/{your-target}/generated/include/syscfg/syscfg.h That shows you all the #defines prepended with

Re: More bletiny

2016-10-28 Thread Christopher Collins
On Fri, Oct 28, 2016 at 10:12:26AM -0700, aditi hilbert wrote: > I thought you are compiling all the config options by package > irrespective of what is used in any particular target. > > Documenting how to do a newt target config eliminates the > need to statically document settings. So that is

Re: More bletiny

2016-10-28 Thread aditi hilbert
I thought you are compiling all the config options by package irrespective of what is used in any particular target. Documenting how to do a newt target config eliminates the need to statically document settings. So that is better. thanks, aditi > On Oct 28, 2016, at 9:58 AM, David G.

Re: More bletiny

2016-10-28 Thread aditi hilbert
Hi David, I agree documenting sys configuration settings/values will be immensely useful. The manual way is to walk the repo. I mean: For stats: incubator-mynewt-core/sys/stats/syscfg.yml For shell: incubator-mynewt-core/sys/shell/syscfg.yml For full console:

Re: More bletiny

2016-10-28 Thread David G. Simmons
Thanks Chris, this is super helpful. Is there a definitive list somewhere of all the possible settings/values for the syscfg.yml file that are accepted? Since I'm documenting everything I come across, this seems like a good thing to document. :-) dg > On Oct 27, 2016, at 6:50 PM, Christopher