yann@693: # Options specific to extracting packages
yann@693: 
yann@693: comment "Extracting"
yann@693: 
yann@693: config FORCE_EXTRACT
yann@693:     bool
yann@693:     prompt "Force extractions"
yann@693:     help
antony@2564:       Force extraction of already extracted tarballs.
yann@693:       
antony@2564:       Useful if you suspect a previous extract did not complete (eg. broken
yann@693:       tarball), or you added a new set of patches for this component.
yann@693: 
yann@693: config OVERIDE_CONFIG_GUESS_SUB
yann@693:     bool
yann@693:     prompt "Override config.{guess,sub}"
yann@693:     default y
yann@693:     help
yann@693:       Override tools' versions of config.guess and config.sub with the ones
yann@693:       from crosstool-NG. This means that all instances of config.guess and
yann@693:       config.sub in gcc, binutils, glibc, etc... will be replaced.
yann@693: 
yann@693:       Most of the time, the versions of those scripts found in packages are old
yann@693:       versions, thus lacking some target definitions. This is the case for
yann@693:       uClibc-based tuples in old versions of gcc and gdb, for example.
yann@693: 
yann@693:       Also, doing so will guarantee that all components have the same tuples
yann@693:       definitions for your target, and not diverging ones.
yann@693: 
yann@693:       You can update the ones provided with crosstool-NG by first running:
yann@693:         ct-ng updatetools
yann@693:       in the directory where you want to run crosstool-NG prior to the build.
yann@693: 
yann@693: config ONLY_EXTRACT
yann@693:     bool
yann@693:     prompt "Stop after extracting tarballs"
yann@693:     help
yann@693:       Exit after unpacking and patching tarballs.
yann@693:       
antony@2564:       Useful to look at the code before doing the build itself.
yann@1510: 
yann@1510: choice
yann@1510:     prompt "Patches origin"
yann@1510:     bool
yann@1510:     default PATCH_BUNDLED
yann@1510: 
yann@1510: config PATCH_BUNDLED
yann@1510:     bool
yann@1510:     prompt "Bundled only"
yann@1510:     help
yann@1510:       Only apply patches bundled with crosstool-NG.
yann@1510: 
yann@1510: config PATCH_LOCAL
yann@1510:     bool
yann@1510:     prompt "Local only"
yann@1510:     select PATCH_USE_LOCAL
yann@1510:     help
yann@1510:       Only apply your local patches.
yann@1510: 
yann@1510: config PATCH_BUNDLED_LOCAL
yann@1510:     bool
yann@1510:     prompt "Bundled, then local"
yann@1510:     select PATCH_USE_LOCAL
yann@1510:     help
yann@1510:       Apply the patches bundled with crosstool-NG,
yann@1510:       then apply your local patches.
yann@1510: 
yann@1510: config PATCH_LOCAL_BUNDLED
yann@1510:     bool
yann@1510:     prompt "Local, then bundled"
yann@1510:     select PATCH_USE_LOCAL
yann@1510:     help
yann@1510:       Apply your local patches, then apply the patches
yann@1510:       bundled with crosstool-NG.
yann@1510: 
yann@1510: config PATCH_BUNDLED_FALLBACK_LOCAL
yann@1510:     bool
yann@1510:     prompt "Bundled only, local if no bundled"
yann@1510:     select PATCH_USE_LOCAL
yann@1510:     select PATCH_SINGLE
yann@1510:     help
yann@1510:       Apply the patches bundled with crosstool-NG;
yann@1510:       if there's no bundled patches, apply your local patches.
yann@1510: 
yann@1510: config PATCH_LOCAL_FALLBACK_BUNDLED
yann@1510:     bool
yann@1510:     prompt "Local only, bundled if no local"
yann@1510:     select PATCH_USE_LOCAL
yann@1510:     select PATCH_SINGLE
yann@1510:     help
yann@1510:       Only apply your local patches;
yann@1510:       if there's no local patches, apply patches bundled with crosstool-NG.
yann@1510: 
yann@1630: config PATCH_NONE
yann@1630:     bool
yann@1630:     prompt "None"
yann@1630:     help
yann@1630:       Don't use any patch at all.
yann@1630:       
antony@2564:       Please be careful if you select this. Most components do require
yann@1630:       patches to properly build. It can happen, however, that support for
yann@1630:       your architecture is clean enough that you can build a toolchain
yann@1630:       with no patch. But most probably, this is *not* the case.
yann@1630:       
yann@1630:       Be safe, use (the bundeld) patches.
yann@1630: 
yann@1510: endchoice
yann@1510: 
yann@1510: config PATCH_ORDER
yann@1510:     string
yann@1510:     default "bundled"           if PATCH_BUNDLED
yann@1510:     default "local"             if PATCH_LOCAL
yann@2225:     default "bundled,local"     if PATCH_BUNDLED_LOCAL || PATCH_BUNDLED_FALLBACK_LOCAL
yann@2225:     default "local,bundled"     if PATCH_LOCAL_BUNDLED || PATCH_LOCAL_FALLBACK_BUNDLED
yann@1630:     default "none"              if PATCH_NONE
yann@1510: 
yann@1510: config PATCH_SINGLE
yann@1510:     bool
yann@1510: 
yann@1510: config PATCH_USE_LOCAL
yann@1510:     bool
yann@1510: 
yann@1510: config LOCAL_PATCH_DIR
yann@1510:     string
yann@1510:     prompt "|  Local patch directory"
yann@1510:     default ""
yann@1510:     depends on PATCH_USE_LOCAL
yann@1510:     help
yann@1510:       Enter the custom patch directory here.
yann@1510:       
antony@2564:       Note that you must ensure that the directory containing your custom
yann@1510:       patches is arranged the same way the official directory is.