diff options
Diffstat (limited to 'config/global/extract.in')
| -rw-r--r-- | config/global/extract.in | 67 |
1 files changed, 24 insertions, 43 deletions
diff --git a/config/global/extract.in b/config/global/extract.in index b754775..4e62480 100644 --- a/config/global/extract.in +++ b/config/global/extract.in @@ -40,60 +40,42 @@ config ONLY_EXTRACT Useful to look at the code before doing the build itself. choice - prompt "Patches origin" - bool + bool "Patches origin" default PATCH_BUNDLED config PATCH_BUNDLED - bool - prompt "Bundled only" + bool "Bundled only" help Only apply patches bundled with crosstool-NG. config PATCH_LOCAL - bool - prompt "Local only" + bool "Local only" select PATCH_USE_LOCAL + depends on EXPERIMENTAL help - Only apply your local patches. + Only apply your local patches. Many components require patching + to build or work properly; please review the bundled patches and + copy them into your local directory if needed. config PATCH_BUNDLED_LOCAL - bool - prompt "Bundled, then local" + bool "Bundled, then local" select PATCH_USE_LOCAL help - Apply the patches bundled with crosstool-NG, - then apply your local patches. + Apply the patches bundled with crosstool-NG, then apply your local + patches. config PATCH_LOCAL_BUNDLED - bool - prompt "Local, then bundled" - select PATCH_USE_LOCAL - help - Apply your local patches, then apply the patches - bundled with crosstool-NG. - -config PATCH_BUNDLED_FALLBACK_LOCAL - bool - prompt "Bundled only, local if no bundled" - select PATCH_USE_LOCAL - select PATCH_SINGLE - help - Apply the patches bundled with crosstool-NG; - if there's no bundled patches, apply your local patches. - -config PATCH_LOCAL_FALLBACK_BUNDLED - bool - prompt "Local only, bundled if no local" + bool "Local, then bundled" select PATCH_USE_LOCAL - select PATCH_SINGLE + depends on EXPERIMENTAL help - Only apply your local patches; - if there's no local patches, apply patches bundled with crosstool-NG. + Apply your local patches, then apply the patches bundled with + crosstool-NG. Note that the bundled patches cannot be guaranteed + to apply on top of your local patches. config PATCH_NONE - bool - prompt "None" + bool "None" + depends on EXPERIMENTAL help Don't use any patch at all. @@ -110,23 +92,22 @@ config PATCH_ORDER string default "bundled" if PATCH_BUNDLED default "local" if PATCH_LOCAL - default "bundled,local" if PATCH_BUNDLED_LOCAL || PATCH_BUNDLED_FALLBACK_LOCAL - default "local,bundled" if PATCH_LOCAL_BUNDLED || PATCH_LOCAL_FALLBACK_BUNDLED + default "bundled,local" if PATCH_BUNDLED_LOCAL + default "local,bundled" if PATCH_LOCAL_BUNDLED default "none" if PATCH_NONE -config PATCH_SINGLE - bool - config PATCH_USE_LOCAL bool config LOCAL_PATCH_DIR string - prompt "| Local patch directory" + prompt "Local patch directory" default "" depends on PATCH_USE_LOCAL help Enter the custom patch directory here. - Note that you must ensure that the directory containing your custom - patches is arranged the same way the official directory is. + Note that you must ensure that tree layout of the directory containing + your custom patches match the bundled patches one. For example, if you + have custom GCC patches for <gcc-version>, place them under + $LOCAL_PATCH_DIR/gcc/<gcc-version>. |