string
option env="HOSTARCH"
+config BR2_EXTERNAL
+ string
+ option env="BR2_EXTERNAL"
+
+# Hidden config symbols for packages to check system gcc version
+config BR2_HOST_GCC_VERSION
+ string
+ option env="HOST_GCC_VERSION"
+
+config BR2_HOST_GCC_AT_LEAST_4_7
+ bool
+ default y if BR2_HOST_GCC_VERSION = "4 7"
+
+config BR2_HOST_GCC_AT_LEAST_4_8
+ bool
+ default y if BR2_HOST_GCC_VERSION = "4 8"
+ select BR2_HOST_GCC_AT_LEAST_4_7
+
+config BR2_HOST_GCC_AT_LEAST_4_9
+ bool
+ default y if BR2_HOST_GCC_VERSION = "4 9"
+ select BR2_HOST_GCC_AT_LEAST_4_8
+
+config BR2_HOST_GCC_AT_LEAST_5
+ bool
+ default y if BR2_HOST_GCC_VERSION = "5"
+ select BR2_HOST_GCC_AT_LEAST_4_9
+
+# Hidden boolean selected by packages in need of Java in order to build
+# (example: xbmc)
+config BR2_NEEDS_HOST_JAVA
+ bool
+
+# Hidden boolean selected by packages in need of javac in order to build
+# (example: classpath)
+config BR2_NEEDS_HOST_JAVAC
+ bool
+
+# Hidden boolean selected by packages in need of jar in order to build
+# (example: classpath)
+config BR2_NEEDS_HOST_JAR
+ bool
+
# Hidden boolean selected by pre-built packages for x86, when they
# need to run on x86-64 machines (example: pre-built external
# toolchains, binary tools like SAM-BA, etc.).
config BR2_HOSTARCH_NEEDS_IA32_LIBS
bool
+# Hidden boolean selected by packages that need to build 32 bits
+# binaries with the host compiler, even on 64 bits build machines (e.g
+# bootloaders).
+config BR2_HOSTARCH_NEEDS_IA32_COMPILER
+ bool
+
source "arch/Config.in"
menu "Build options"
default "$(TOPDIR)/dl"
help
Directory to store all the source files that we need to fetch.
- If the Linux shell environment has defined the BUILDROOT_DL_DIR
+ If the Linux shell environment has defined the BR2_DL_DIR
environment variable, then this overrides this configuration item.
The default is $(TOPDIR)/dl
Primary site to download from. If this option is set then buildroot
will try to download package source first from this site and try the
default if the file is not found.
- Valid URIs are URIs recognized by $(WGET) and scp URIs of the form
- scp://[user@]host:path.
- NOTE: This works for all packages using the central package
- infrastructure (generic, autotools, cmake, ...)
+ Valid URIs are:
+ - URIs recognized by $(WGET)
+ - local URIs of the form file://absolutepath
+ - scp URIs of the form scp://[user@]host:path.
config BR2_PRIMARY_SITE_ONLY
bool "Only allow downloads from primary download site"
config BR2_BACKUP_SITE
string "Backup download site"
- default "http://sources.buildroot.net/"
+ default "http://sources.buildroot.net"
help
Backup site to download from. If this option is set then buildroot
will fall back to download package sources from here if the
config BR2_KERNEL_MIRROR
string "Kernel.org mirror"
- default "http://www.kernel.org/pub/"
+ default "https://www.kernel.org/pub"
help
kernel.org is mirrored on a number of servers around the world.
The following allows you to select your preferred mirror.
http://ftp.gnu.org/pub/gnu
http://mirror.aarnet.edu.au/pub/gnu
-config BR2_DEBIAN_MIRROR
- string "Debian Software mirror"
- default "http://ftp.debian.org"
+config BR2_LUAROCKS_MIRROR
+ string "LuaRocks mirror"
+ default "http://rocks.moonscript.org"
help
- Debian has multiple software mirrors scattered around the world.
- The following allows you to select your preferred mirror.
+ LuaRocks repository.
+
+ See http://luarocks.org
+
+config BR2_CPAN_MIRROR
+ string "CPAN mirror (Perl packages)"
+ default "http://cpan.metacpan.org"
+ help
+ CPAN (Comprehensive Perl Archive Network) is a repository
+ of Perl packages. It has multiple software mirrors scattered
+ around the world. This option allows you to select a mirror.
- Usually, just add your country code like XX here:
- http://ftp.XX.debian.org
+ The list of mirrors is available at:
+ http://search.cpan.org/mirror
endif
help
This option will enable the use of ccache, a compiler
cache. It will cache the result of previous builds to speed
- up future builds. The cache is stored in
+ up future builds. By default, the cache is stored in
$HOME/.buildroot-ccache.
Note that Buildroot does not try to invalidate the cache
ccache cache by removing the $HOME/.buildroot-ccache
directory.
+if BR2_CCACHE
+
config BR2_CCACHE_DIR
string "Compiler cache location"
- depends on BR2_CCACHE
default "$(HOME)/.buildroot-ccache"
help
Where ccache should store cached files.
+config BR2_CCACHE_INITIAL_SETUP
+ string "Compiler cache initial setup"
+ help
+ Initial ccache settings to apply, such as --max-files or --max-size.
+
+ For example, if your project is known to require more space than the
+ default max cache size, then you might want to increase the cache size
+ to a suitable amount using the -M (--max-size) option.
+
+ The string you specify here is passed verbatim to ccache. Refer to
+ ccache documentation for more details.
+
+ These initial settings are applied after ccache has been compiled.
+
+config BR2_CCACHE_USE_BASEDIR
+ bool "Use relative paths"
+ default y
+ help
+ Allow ccache to convert absolute paths within the output
+ directory into relative paths.
+
+ During the build, many -I include directives are given with
+ an absolute path. These absolute paths end up in the hashes
+ that are computed by ccache. Therefore, when you build from a
+ different directory, the hash will be different and the
+ cached object will not be used.
+
+ To improve cache performance, set this option to y. This
+ allows ccache to rewrite absolute paths within the output
+ directory into relative paths. Note that only paths within
+ the output directory will be rewritten; therefore, if you
+ change BR2_HOST_DIR to point outside the output directory and
+ subsequently move it to a different location, this will lead
+ to cache misses.
+
+ This option has as a result that the debug information in the
+ object files also has only relative paths. Therefore, make
+ sure you cd to the build directory before starting gdb. See
+ the section "COMPILING IN DIFFERENT DIRECTORIES" in the
+ ccache manual for more information.
+
+endif
+
config BR2_DEPRECATED
- bool "Show packages that are deprecated or obsolete"
+ bool "Show options and packages that are deprecated or obsolete"
help
- This option hides outdated/obsolete versions of packages.
+ This option shows outdated/obsolete versions of packages and
+ options that are otherwise hidden.
+
+if BR2_DEPRECATED
+
+config BR2_DEPRECATED_SINCE_2015_05
+ bool
+ default y
+
+config BR2_DEPRECATED_SINCE_2015_08
+ bool
+ default y
+
+config BR2_DEPRECATED_SINCE_2015_11
+ bool
+ default y
+
+config BR2_DEPRECATED_SINCE_2016_02
+ bool
+ default y
+
+endif
config BR2_ENABLE_DEBUG
bool "build packages with debugging symbols"
symbols on the target are needed for native debugging, but
not when remote debugging is used.
-config BR2_STRIP_sstrip
- bool "sstrip"
- select BR2_PACKAGE_SSTRIP_HOST
- depends on !BR2_PACKAGE_HOST_ELF2FLT
- help
- Binaries and libraries in the target filesystem will be
- stripped using the 'sstrip' command, which strips a little
- bit more than the traditional 'strip' command. This allows to
- save space, mainly by removing debugging symbols. Debugging
- symbols on the target are needed for native debugging, but
- not when remote debugging is used.
-
config BR2_STRIP_none
bool "none"
help
endchoice
-config BR2_ENABLE_SSP
+config BR2_GOOGLE_BREAKPAD_ENABLE
+ bool "Enable google-breakpad support"
+ select BR2_PACKAGE_GOOGLE_BREAKPAD
+ depends on BR2_INSTALL_LIBSTDCPP
+ depends on BR2_TOOLCHAIN_USES_GLIBC
+ depends on BR2_PACKAGE_GOOGLE_BREAKPAD_ARCH_SUPPORTS
+ help
+ This option will enable the use of google breakpad, a
+ library and tool suite that allows you to distribute an
+ application to users with compiler-provided debugging
+ information removed, record crashes in compact "minidump"
+ files, send them back to your server and produce C and C++
+ stack traces from these minidumps. Breakpad can also write
+ minidumps on request for programs that have not crashed.
+
+if BR2_GOOGLE_BREAKPAD_ENABLE
+
+config BR2_GOOGLE_BREAKPAD_INCLUDE_FILES
+ string "List of executables and libraries to extract symbols from"
+ default ""
+ help
+ You may specify a space-separated list of binaries and
+ libraries with full paths relative to $(TARGET_DIR) of which
+ debug symbols will be dumped for further use with google
+ breakpad.
+
+ A directory structure that can be used by minidump-stackwalk
+ will be created at:
+
+ $(STAGING_DIR)/usr/share/google-breakpad-symbols
+
+endif
+
+choice
bool "build code with Stack Smashing Protection"
+ default BR2_SSP_ALL if BR2_ENABLE_SSP # legacy
depends on BR2_TOOLCHAIN_HAS_SSP
help
- Enable stack smashing protection support using GCCs
- -fstack-protector-all option.
+ Enable stack smashing protection support using GCC's
+ -fstack-protector option family.
See http://www.linuxfromscratch.org/hints/downloads/files/ssp.txt
for details.
support. This is always the case for glibc and eglibc
toolchain, but is optional in uClibc toolchains.
-comment "enabling Stack Smashing Protection requires support in the toolchain"
+config BR2_SSP_NONE
+ bool "None"
+ help
+ Disable stack-smashing protection.
+
+config BR2_SSP_REGULAR
+ bool "-fstack-protector"
+ help
+ Emit extra code to check for buffer overflows, such as stack
+ smashing attacks. This is done by adding a guard variable to
+ functions with vulnerable objects. This includes functions
+ that call alloca, and functions with buffers larger than 8
+ bytes. The guards are initialized when a function is entered
+ and then checked when the function exits. If a guard check
+ fails, an error message is printed and the program exits.
+
+config BR2_SSP_STRONG
+ bool "-fstack-protector-strong"
+ depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
+ help
+ Like -fstack-protector but includes additional functions to be
+ protected - those that have local array definitions, or have
+ references to local frame addresses.
+
+comment "Stack Smashing Protection strong needs a toolchain w/ gcc >= 4.9"
+ depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
+
+config BR2_SSP_ALL
+ bool "-fstack-protector-all"
+ help
+ Like -fstack-protector except that all functions are
+ protected. This option might have a significant performance
+ impact on the compiled binaries.
+
+endchoice
+
+comment "Stack Smashing Protection needs a toolchain w/ SSP"
depends on !BR2_TOOLCHAIN_HAS_SSP
-config BR2_PREFER_STATIC_LIB
- bool "prefer static libraries"
+choice
+ bool "libraries"
+ default BR2_SHARED_LIBS if BR2_BINFMT_SUPPORTS_SHARED
+ default BR2_STATIC_LIBS if !BR2_BINFMT_SUPPORTS_SHARED
help
- Where possible, build and use static libraries for the target.
- This potentially increases your code size and should only be
- used if you know what you do.
+ Select the type of libraries you want to use on the target.
+
The default is to build dynamic libraries and use those on
- the target filesystem.
+ the target filesystem, except when the architecture and/or
+ the selected binary format does not support shared
+ libraries.
- WARNING: This is highly experimental at the moment.
+config BR2_STATIC_LIBS
+ bool "static only"
+ help
+ Build and use only static libraries. No shared libraries
+ will be instaled on the target. This potentially increases
+ your code size and should only be used if you know what you
+ are doing. Note that some packages may not be available when
+ this option is enabled, due to their need for dynamic
+ library support.
+
+config BR2_SHARED_LIBS
+ bool "shared only"
+ depends on BR2_BINFMT_SUPPORTS_SHARED
+ help
+ Build and use only shared libraries. This is the recommended
+ solution as it saves space and build time.
-config BR2_HAVE_DOCUMENTATION
- bool "documentation on the target"
- # We no longer want to support a toolchain on the target
- depends on BR2_DEPRECATED
+config BR2_SHARED_STATIC_LIBS
+ bool "both static and shared"
+ depends on BR2_BINFMT_SUPPORTS_SHARED
help
- Install the documentation, including manual pages and info
- pages, on the target.
- If you say n here, your target will not contain any
- documentation.
+ Build both shared and static libraries, but link executables
+ dynamically. While building both shared and static libraries
+ take more time and more disk space, having static libraries
+ may be useful to link some of the applications statically.
+
+endchoice
+
config BR2_PACKAGE_OVERRIDE_FILE
string "location of a package override file"
- default "$(TOPDIR)/local.mk"
+ default "$(CONFIG_DIR)/local.mk"
help
A package override file is a short makefile that contains
variable definitions of the form <pkg>_OVERRIDE_SRCDIR,
Buildroot documentation for more details on this feature.
config BR2_GLOBAL_PATCH_DIR
- string "global patch directory"
+ string "global patch directories"
help
- You may specify a directory containing global package patches.
- For a specific version <packageversion> of a specific package
- <packagename>, patches are applied as follows.
+ You may specify a space separated list of one or more directories
+ containing global package patches. For a specific version
+ <packageversion> of a specific package <packagename>, patches are
+ applied as follows:
- First, the default Buildroot patch set for the package is applied.
+ First, the default Buildroot patch set for the package is applied
+ from the package's directory in Buildroot.
- If the directory $(BR2_GLOBAL_PATCH_DIR)/<packagename>/<packageversion>
- exists, then all *.patch files in the directory will be applied.
+ Then for every directory - <global-patch-dir> - that exists in
+ BR2_GLOBAL_PATCH_DIR, if the directory
+ <global-patch-dir>/<packagename>/<packageversion>/ exists, then all
+ *.patch files in this directory will be applied.
- Otherwise, if the directory
$(BR2_GLOBAL_PATCH_DIR)/<packagename> exists,
+ Otherwise, if the directory
<global-patch-dir>/<packagename> exists,
then all *.patch files in the directory will be applied.
+menu "Advanced"
+
+config BR2_COMPILER_PARANOID_UNSAFE_PATH
+ bool "paranoid check of library/header paths"
+ help
+ By default, when this option is disabled, when the Buildroot
+ cross-compiler will encounter an unsafe library or header
+ path (such as /usr/include, or /usr/lib), the compiler will
+ display a warning.
+
+ By enabling this option, this warning is turned into an
+ error, which will completely abort the build when such
+ unsafe paths are encountered.
+
+ Note that this mechanism is available for both the internal
+ toolchain (through gcc and binutils patches) and external
+ toolchain backends (through the external toolchain wrapper).
+
+endmenu
+
endmenu
source "toolchain/Config.in"
source "package/Config.in.host"
source "Config.in.legacy"
+
+menu "User-provided options"
+ depends on BR2_EXTERNAL != "support/dummy-external"
+
+source "$BR2_EXTERNAL/Config.in"
+
+endmenu
projects / coffee / buildroot.git / blobdiff