nuttx/nuttx-mirror
1
2
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2025-01-13 10:58:49 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README.txt files

Browse source
This commit is contained in:
Gregory Nutt 2016-03-10 17:24:48 -06:00
parent 0929c8b1d7
commit f16f470881
2 changed files with 38 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.txt
View file

@ -476,6 +476,16 @@ Refreshing Configurations
be? Enter ? in response to the 'make oldconfig' prompt and it will show be? Enter ? in response to the 'make oldconfig' prompt and it will show
you the help text that goes with the option. you the help text that goes with the option.
If you don't want to make any decisions are are willing to just accep the
recommended default value for each new configuration item, an even easier
way is:
make oldefconfig
The olddefconfig target will simply bring you configuration up to date with
the current Kconfig files, setting any new options to the default value.
No questions asked.
NuttX Configuration Tool NuttX Configuration Tool
------------------------ ------------------------

32
tools/README.txt
View file

@ -575,7 +575,26 @@ refresh.sh
new dependencies are added. So an old configuration file may new dependencies are added. So an old configuration file may
not be usable anymore until it is refreshed. not be usable anymore until it is refreshed.
The steps to refresh the file are: Help is also available:
$ tools/refresh.sh --help
tools/refresh.sh is a tool for refreshing board configurations
USAGE: tools/refresh.sh [--debug|--help] <board>/<config>
Where:
--debug
Enable script debug
--silent
Update board configuration without interaction
--help
Show this help message and exit
<board>
The board directory under nuttx/configs
<config>
The board configuration directory under nuttx/configs/<board>
The steps to refresh the file taken by refresh.sh are:
1. Make tools/cmpconfig if it is not already built. 1. Make tools/cmpconfig if it is not already built.
2. Copy the the defconfig file to the top-level NuttX 2. Copy the the defconfig file to the top-level NuttX
@ -584,6 +603,10 @@ refresh.sh
3. Execute 'make oldconfig' to update the configuration. 3. Execute 'make oldconfig' to update the configuration.
'make oldconfig' will prompt you for each change in the 'make oldconfig' will prompt you for each change in the
configuration that requires that you make some decision. configuration that requires that you make some decision.
With the --silent option, the script will use 'make
oldefconfig' instead and you won't have to answer any
questions; the refresh will simply accept the default
value for any new configuration settings.
4. Then it runs tools/cmpconfig to show the real differences 4. Then it runs tools/cmpconfig to show the real differences
between the configuration files. Configuration files are between the configuration files. Configuration files are
complex and things can move around so a simple 'diff' between complex and things can move around so a simple 'diff' between
@ -597,9 +620,10 @@ refresh.sh
installed. installed.
5. Finally, the refreshed defconfig file is copied back in 5. Finally, the refreshed defconfig file is copied back in
place where it can be committed with the next set of place where it can be committed with the next set of
difference to the command line. refresh.sh will prompt difference to the command line. If you select the --silent
you first to avoid overwriting the defconfig file with option, this file copy will occur autiomatically. Otherwise,
changes that you do not want. refresh.sh will prompt you first to avoid overwriting the
defconfig file with changes that you may not want.
testbuild.sh testbuild.sh
------------ ------------