docs/ct-ng.1.in
changeset 3034 11c23aa9c9f9
parent 2621 00853d565edf
child 3224 4e9c41579ebd
     1.1 --- a/docs/ct-ng.1.in	Wed Aug 17 23:05:01 2011 +0200
     1.2 +++ b/docs/ct-ng.1.in	Wed Aug 15 22:06:22 2012 +0200
     1.3 @@ -60,6 +60,47 @@
     1.4  with the target tuple they represent.
     1.5  ."
     1.6  .TP
     1.7 +.B defconfig
     1.8 +Save the current configuration to a mini-defconfig file, that contains only
     1.9 +the strictly required symbols to reproduce the configuraiton. defconfig files
    1.10 +are much smaller than a complete .config, so it is easy to send by mail. As
    1.11 +only non-default symbols are present in a defconfig, it easy to spot the
    1.12 +meaningfull values. Also, it is easy to use defconfig files with newer
    1.13 +versions of
    1.14 +.BR crosstool-NG .
    1.15 +By default the mini-defconfig is saved to a file named
    1.16 +.IR defconfig ,
    1.17 +unless the variable
    1.18 +.B $DEFCONFIG
    1.19 +is set, in which case the mini-defconfig will be saved to the file referenced
    1.20 +by
    1.21 +.BR $DEFCONFIG .
    1.22 +
    1.23 +Note: only the
    1.24 +.I .config
    1.25 +file for
    1.26 +.B crosstool-NG
    1.27 +is saved. Config files for the components are
    1.28 +.B not
    1.29 +saved. Use
    1.30 +.B saveconfig
    1.31 +for that
    1.32 +."
    1.33 +.TP
    1.34 +.B olddefconfig
    1.35 +Configure
    1.36 +.B crosstool-NG
    1.37 +using a mini-defconfig file (previously saved with
    1.38 +.B defconfig
    1.39 +or manually edited). The default mini-defconfig is rad from the file
    1.40 +.IR defconfig ,
    1.41 +unless the vraiable
    1.42 +.B $DEFCONFIG
    1.43 +is set, inwhich case the mini-defconfig will be read from the file referenced
    1.44 +by
    1.45 +.B $DEFCONFIG
    1.46 +."
    1.47 +.TP
    1.48  .B build
    1.49  Builds the configured toolchain.
    1.50  ."