Update Document and README.

This commit is contained in:
Gregory Nutt 2017-07-08 10:34:06 -06:00
parent bea75baaab
commit ec01bc411c
2 changed files with 31 additions and 1 deletions

View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
<p>Last Updated: June 5, 2017</p>
<p>Last Updated: July 8, 2017</p>
</td>
</tr>
</table>
@ -796,6 +796,14 @@
</p>
</td>
</tr>
<tr>
<td><br></td>
<td>
<p>
<li>IP Forwarding.</li>
</p>
</td>
</tr>
<tr>
<td><br></td>
<td>

View File

@ -20,6 +20,7 @@ README
- Make Sure that You on on the Right Platform
- Comparing Two Configurations
- Making defconfig Files
- Configuring with "Compressed" defconfig Files
- Incompatibilities with Older Configurations
- NuttX Configuration Tool under DOS
o Toolchains
@ -896,6 +897,27 @@ Making defconfig Files
If the default settings change, and they often do, then the original
.config may not be reproducible.
Configuring with "Compressed" defconfig Files
---------------------------------------------
As described in the previous section, "Making defconfig Files," defconfig
files may be "compressed" using 'make savedeconfig'. This compressed
defconfig files are will may not be fully usable and may not build the
target binaries that you want because the compression process removed all
of the default settings from the defconfig file. To restore the default
settings, you should run the following after configuring:
make olddefconfig
That will restore the the missing defaulted value.
Using this command after configuring is generally a good practice anyway:
Even if the defconfig files are not "compressed" in this fashion, there
the defconfig file may be old and the only way to assure that the
installed .config is via 'make oldconfig' or 'make olddefconfig'. See the
paragraph above entitled ""Refreshing Configurations" for additional
information.
Incompatibilities with Older Configurations
-------------------------------------------