d748cb6118
This makes it possible to tell at a glance which variables are internal to the script and which ones are parameters to it, which is very helpful. This convention is pretty common. See e.g. Google's shell style guide at https://google.github.io/styleguide/shell.xml#Naming_Conventions, and https://github.com/icy/bash-coding-style#naming-and-styles. It's older than those though. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.txt | ||
| check_net_options.sh | ||
| prj.conf | ||
| testcase.yaml | ||
README.txt
This test tries to enable all possible networking related config options and build a sample application. The application is not supposed to be run as typically the generated configuration is not usable. The check_net_options.sh script can be used in Linux host to generate a list of missing network related kconfig options from prj.conf file. TODO: * separate conflicting configuration options and create new test cases for them