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 <target> eliminates the need to statically document settings. So that is better. thanks, aditi > On Oct 28, 2016, at 9:58 AM, David G. Simmons <[email protected]> wrote: > > I actually found the exhaustive list by running newt target config myble > which lists ALL the system configuration options by package, etc. and shows > which ones are overridden in the current application. > > I've documented this on the Vocabulary page. > > dg > >> On Oct 28, 2016, at 12:40 PM, aditi hilbert <[email protected]> wrote: >> >> 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: >> incubator-mynewt-core/sys/console/full/syscfg.yml >> >> For BLE host: >> incubator-mynewt-core/net/nimble/host/syscfg.yml >> >> For BLE controller: >> incubator-mynewt-core/net/nimble/controller/syscfg.yml >> >> … and so on. >> >> Then, the application's syscfg.yml can override any default settings as >> required by the use case. We see that, say, in the syscfg.yml for the >> example app bletiny: >> incubator-mynewt-core/apps/bletiny/syscfg.yml >> >> thanks, >> aditi >> >> >> >>> On Oct 28, 2016, at 8:31 AM, David G. Simmons <[email protected]> wrote: >>> >>> 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 Collins <[email protected]> >>>> wrote: >>>> >>>> Hi David, >>>> >>>> On Thu, Oct 27, 2016 at 06:03:22PM -0400, David G. Simmons wrote: >>>>> There must be more to it than this ... >>>>> >>>>> # Package: apps/bletiny >>>>> >>>>> syscfg.vals: >>>>> SHELL_TASK: 1 >>>>> STATS_NAMES: 1 >>>>> >>>>> I can confirm that changing SHELL_TASK to 0 does indeed disable the >>>>> shell, but STATS_NAME does not seem to enable stats. >>>> >>>> That syscfg.yml file looks good to me. However, I think you may need to >>>> enable some additional settings. The STATS_NAMES setting causes name >>>> strings to be included in the build, but the stats won't necessarily be >>>> accessible. >>>> >>>> A good way to see the available settings is to use the "newt target >>>> configure <target-name>" command. When I use this command on a target >>>> of mine, I see the following settings defined by the sys/stats package: >>>> >>>> [ccollins@pseudoephedrine:~/repos/mynewt/core]$ newt target config >>>> bleprph-nrf52dk >>>> # [...] >>>> >>>> * PACKAGE: sys/stats >>>> * Setting: STATS_CLI >>>> * Description: Expose the "stat" shell command. >>>> * Value: 0 >>>> * Setting: STATS_NAMES >>>> * Description: Include and report the textual name of each >>>> statistic. >>>> * Value: 0 >>>> * Setting: STATS_NEWTMGR >>>> * Description: Expose the "stat" newtmgr command. >>>> * Value: 0 >>>> >>>> (Before someone calls me out, yes, the descriptions were all "TBD" until >>>> about five seconds ago! :) >>>> >>>> I think you probably want one or both of STATS_CLI / STATS_NEWTMGR. >>>> >>>> Sorry for the confusion. The default behavior of some packages has >>>> changed, and we haven't done a very good job of explaining it on the dev >>>> list. >>>> >>>> Chris >>> >>> -- >>> David G. Simmons >>> (919) 534-5099 >>> Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • >>> Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter >>> <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> >>> /** Message digitally signed for security and authenticity. >>> * If you cannot read the PGP.sig attachment, please go to >>> * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! >>> * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> >>> **/ >>> ♺ This email uses 100% recycled electrons. Don't blow it by printing! >>> >>> There are only 2 hard things in computer science: Cache invalidation, >>> naming things, and off-by-one errors. >>> >>> >> > > -- > David G. Simmons > (919) 534-5099 > Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • > Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter > <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> > /** Message digitally signed for security and authenticity. > * If you cannot read the PGP.sig attachment, please go to > * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! > * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> > **/ > ♺ This email uses 100% recycled electrons. Don't blow it by printing! > > There are only 2 hard things in computer science: Cache invalidation, naming > things, and off-by-one errors. > >
