diff options
Diffstat (limited to 'config/global')
| -rw-r--r-- | config/global/build-behave.in | 34 | ||||
| -rw-r--r-- | config/global/ct-behave.in | 1 | ||||
| -rw-r--r-- | config/global/download.in | 50 | ||||
| -rw-r--r-- | config/global/extract.in | 67 | ||||
| -rw-r--r-- | config/global/paths.in | 40 |
5 files changed, 123 insertions, 69 deletions
diff --git a/config/global/build-behave.in b/config/global/build-behave.in index 9ad5438..4af2f26 100644 --- a/config/global/build-behave.in +++ b/config/global/build-behave.in @@ -2,12 +2,9 @@ comment "Build behavior" -comment "Build options hiden" - depends on BACKEND - config PARALLEL_JOBS int - prompt "Number of parallel jobs" if ! BACKEND + prompt "Number of parallel jobs" default 0 help Number of jobs make will be allowed to run concurently. @@ -16,11 +13,12 @@ config PARALLEL_JOBS Enter 1 to have only one job at a time. - Enter 0 to set automatically based on how many processors the host has. + Enter 0 to set automatically based on how many processors the build + machine has. config LOAD string - prompt "Maximum allowed load" if ! BACKEND + prompt "Maximum allowed load" default "" help Specifies that no new jobs should be started if there are others jobs @@ -33,7 +31,7 @@ config LOAD config USE_PIPES bool - prompt "Use -pipe" if ! BACKEND + prompt "Use -pipe" default y help Use gcc's option -pipe to use pipes rather than temp files when building @@ -48,7 +46,17 @@ config EXTRA_CFLAGS_FOR_BUILD May be used to change the default features of the build compiler such as turning off the stack protector or fortify. - + +config EXTRA_CXXFLAGS_FOR_BUILD + string + prompt "Extra build compiler flags" + default "" + help + Extra flags to pass only to the build C++ compiler. + + May be used to change the default features of the C++ build + compiler such as specifying the C++ standard to use. + config EXTRA_LDFLAGS_FOR_BUILD string prompt "Extra build linker flags" @@ -83,7 +91,6 @@ choice bool prompt "Shell to use as CONFIG_SHELL" default CONFIG_SHELL_BASH - depends on ! BACKEND config CONFIG_SHELL_SH bool @@ -141,13 +148,10 @@ config CONFIG_SHELL_CUSTOM endchoice -# Do not put this into the choice above, because the choice -# is not available in BACKEND-mode, while we do want this to -# be set even in BACKEND-mode. config CONFIG_SHELL_CUSTOM_PATH string - prompt "Path to custom shell" if ! BACKEND - depends on CONFIG_SHELL_CUSTOM || BACKEND + prompt "Path to custom shell" + depends on CONFIG_SHELL_CUSTOM default "/bin/sh" # Ditto. @@ -157,4 +161,4 @@ config CONFIG_SHELL default "/bin/sh" if CONFIG_SHELL_SH default "/bin/ash" if CONFIG_SHELL_ASH default "${bash}" if CONFIG_SHELL_BASH - default CONFIG_SHELL_CUSTOM_PATH if CONFIG_SHELL_CUSTOM || BACKEND + default CONFIG_SHELL_CUSTOM_PATH if CONFIG_SHELL_CUSTOM diff --git a/config/global/ct-behave.in b/config/global/ct-behave.in index a57c798..42171e4 100644 --- a/config/global/ct-behave.in +++ b/config/global/ct-behave.in @@ -63,7 +63,6 @@ config ALLOW_BUILD_AS_ROOT_SURE config DEBUG_CT bool prompt "Debug crosstool-NG" - depends on ! BACKEND help Say 'y' here to get some options regarding debugging crosstool-NG. diff --git a/config/global/download.in b/config/global/download.in index fc79400..57f42e6 100644 --- a/config/global/download.in +++ b/config/global/download.in @@ -132,4 +132,54 @@ config MIRROR_BASE_URL endif # USE_MIRROR +config VERIFY_DOWNLOAD_DIGEST + bool "Verify download digests (checksums)" + default y + depends on CONFIGURE_has_sha512sum || CONFIGURE_has_sha256sum || CONFIGURE_has_sha1sum || CONFIGURE_has_md5sum + +if VERIFY_DOWNLOAD_DIGEST + +choice + prompt "Digest algorithm" + +config VERIFY_DOWNLOAD_DIGEST_SHA512 + bool "SHA-512" + depends on CONFIGURE_has_sha512sum + +config VERIFY_DOWNLOAD_DIGEST_SHA256 + depends on CONFIGURE_has_sha256sum + bool "SHA-256" + +config VERIFY_DOWNLOAD_DIGEST_SHA1 + depends on CONFIGURE_has_sha1sum + bool "SHA-1" + +config VERIFY_DOWNLOAD_DIGEST_MD5 + depends on CONFIGURE_has_md5sum + bool "MD5" + +endchoice + +config VERIFY_DOWNLOAD_DIGEST_ALG + string + default "md5" if VERIFY_DOWNLOAD_DIGEST_MD5 + default "sha1" if VERIFY_DOWNLOAD_DIGEST_SHA1 + default "sha256" if VERIFY_DOWNLOAD_DIGEST_SHA256 + default "sha512" if VERIFY_DOWNLOAD_DIGEST_SHA512 + +endif # VERIFY_DOWNLOAD_DIGEST + +config VERIFY_DOWNLOAD_SIGNATURE + bool "Verify detached signatures" + help + Verify the signatures for the downloads where available. + This requires the public keys for all the packages used in the build + to be imported into a keyring on the build machine. + + Note that the validation will succeed so long as the signature + is known and valid, even if the signature is not trusted! GnuPG + issues a warning in this case, but ultimately reports that validation + succeeded. Check the log file if this is a concern; crosstool-NG + may add an option to verify this more paranoidally later. + endif # ! FORBID_DOWNLOAD 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>. diff --git a/config/global/paths.in b/config/global/paths.in index 5313d0d..82ee4b3 100644 --- a/config/global/paths.in +++ b/config/global/paths.in @@ -4,7 +4,7 @@ comment "Paths" config LOCAL_TARBALLS_DIR string - prompt "Local tarballs directory" if ! BACKEND + prompt "Local tarballs directory" default "${HOME}/src" help If you have previously downloaded the tarballs, enter the PATH where @@ -12,16 +12,27 @@ config LOCAL_TARBALLS_DIR config SAVE_TARBALLS bool - prompt "Save new tarballs" if ! BACKEND - depends on LOCAL_TARBALLS_DIR != "" || BACKEND + prompt "Save new tarballs" + depends on LOCAL_TARBALLS_DIR != "" default y help If you say 'y' here, new downloaded tarballs will be saved in the directory you entered above. +config TARBALLS_BUILDROOT_LAYOUT + bool "Prefer buildroot-style layout of the downloads" + help + Buildroot switched the layout of its downloads directory to place + files for each package into a subdirectory named after that package. + Enable this option to have crosstool-NG create similar layout. + If this option is set and the required archive is located in + the directory with a legacy, flat layout, the archive will be moved + into a subdirectory. If this is option is not set, subdirectories + will neither be checked nor used to store the downloads. + config WORK_DIR string - prompt "Working directory" if ! BACKEND + prompt "Working directory" default "${CT_TOP_DIR}/.build" help Set this to the directory where all build actions will be done. @@ -42,11 +53,15 @@ config WORK_DIR config BUILD_TOP_DIR string - default "${CT_WORK_DIR}/${CT_HOST:+HOST-${CT_HOST}/}${CT_TARGET}" + default "${CT_WORK_DIR:-${CT_TOP_DIR}/.build}/${CT_HOST:+HOST-${CT_HOST}/}${CT_TARGET}" + +config BUILD_DIR + string + default "${CT_BUILD_TOP_DIR}/build" config PREFIX_DIR string - prompt "Prefix directory" if ! BACKEND + prompt "Prefix directory" default "${CT_PREFIX:-${HOME}/x-tools}/${CT_HOST:+HOST-${CT_HOST}/}${CT_TARGET}" help This is the path the toolchain will run from. @@ -55,7 +70,6 @@ config RM_RF_PREFIX_DIR bool prompt "| Remove the prefix dir prior to building" default y - depends on !BACKEND help If you say 'y' here, then PREFIX_DIR (above) will be eradicated prior to the toolchain is built. @@ -69,9 +83,6 @@ config RM_RF_PREFIX_DIR it into a directory with pre-install, unrelated programs, it would be damageable to remove that directory. In this case, you may want to say 'n' here. - - Note that when acting as a backend, this option is not available, and - is forced to 'n'. config REMOVE_DOCS bool @@ -89,6 +100,15 @@ config BUILD_MANUALS Build the PDF and HTML manuals for the main components such as binutils, GCC, GDB, and the C library. +config INSTALL_LICENSES + bool "Install licenses" + default y + help + Collect the license files for all the components that went into + producing this toolchain (including the crosstool-NG itself) + and place them in /share/licenses directory within the prefix + directory. + config PREFIX_DIR_RO bool prompt "Render the toolchain read-only" |