Config.in.2 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194
  1. #
  2. config BR2_LARGEFILE
  3. bool "Enable large file (files > 2 GB) support?"
  4. depends on !BR2_cris
  5. help
  6. If you are building your own toolchain and you want to
  7. support files larger than 2GB then enable this option.
  8. If you have an external binary toolchain that has been
  9. built with large file support (files > 2GB) then enable
  10. this option.
  11. config BR2_INET_IPV6
  12. bool "Enable IPv6"
  13. help
  14. If you are building your own toolchain and you want to
  15. enable IPV6 support then enable this option.
  16. If you have an external binary toolchain that has been
  17. built with IPV6 support then enable this option.
  18. config BR2_INET_RPC
  19. bool "Enable RPC"
  20. help
  21. Enable RPC. RPC support is needed for nfs.
  22. If you are building your own toolchain and you want to
  23. enable RPC support then enable this option.
  24. If you have an external binary toolchain that has been
  25. built with RPC support then enable this option.
  26. config BR2_ENABLE_LOCALE
  27. bool "Enable toolchain locale/i18n support?"
  28. select BR2_USE_WCHAR
  29. help
  30. If you are building your own toolchain and you want to
  31. enable locale/i18n support then enable this option.
  32. If you have an external binary toolchain that has been
  33. built with locale/i18n support then enable this option.
  34. config BR2_ENABLE_LOCALE_PREGENERATED
  35. bool "Use pregenerated locale data?"
  36. depends on BR2_ENABLE_LOCALE && BR2_TOOLCHAIN_BUILDROOT && BROKEN # tarball missing
  37. help
  38. Instead of generating the locale data locally you can optionally
  39. download a pregenerated set of locales.
  40. Say N here unless your buildhost lacks locale support and you
  41. desparately want to use internationalization on your target.
  42. config BR2_ENABLE_LOCALE_PURGE
  43. bool "Purge unwanted locales"
  44. help
  45. Explicitly specify what locales to install on target. If N
  46. then all locales supported by packages are installed.
  47. config BR2_ENABLE_LOCALE_WHITELIST
  48. string "Locales to keep"
  49. default "C en_US de fr"
  50. depends on BR2_ENABLE_LOCALE_PURGE
  51. help
  52. Whitespace seperated list of locales to allow on target.
  53. Locales not listed here will be removed from the target.
  54. See 'locale -a' on your host for a list of locales available
  55. on your build host, or have a look in /usr/share/locale in
  56. the target file system for available locales.
  57. Notice that listing a locale here doesn't guarantee that it
  58. will be available on the target - That purely depends on the
  59. support for that locale in the selected packages.
  60. config BR2_USE_WCHAR
  61. bool "Enable WCHAR support"
  62. help
  63. If you are building your own toolchain and you want to
  64. enable WCHAR support then enable this option.
  65. If you have an external binary toolchain that has been built
  66. with WCHAR support then enable this option.
  67. config BR2_PREFER_SOFT_FLOAT
  68. bool
  69. default y if BR2_arm || BR2_armeb || BR2_avr32 || BR2_mips || BR2_mipsel || BR2_nios2
  70. config BR2_SOFT_FLOAT
  71. bool "Use software floating point by default"
  72. depends on BR2_arm || BR2_armeb || BR2_avr32 || BR2_mips || BR2_mipsel || BR2_powerpc || BR2_nios2
  73. default $(BR2_PREFER_SOFT_FLOAT)
  74. help
  75. If your target CPU does not have a Floating Point Unit (FPU) or a
  76. kernel FPU emulator, but you still wish to support floating point
  77. functions, then everything will need to be compiled with soft
  78. floating point support (-msoft-float).
  79. config BR2_USE_SSP
  80. bool "Enable stack protection support"
  81. help
  82. Enable stack smashing protection support using GCCs
  83. -fstack-protector[-all] option.
  84. See http://www.linuxfromscratch.org/hints/downloads/files/ssp.txt
  85. for details.
  86. choice
  87. prompt "Thread library implementation"
  88. default BR2_PTHREADS_OLD
  89. help
  90. If you are building your own toolchain then select the type of
  91. libpthreads you want to use.
  92. Not all thread variants work with all versions of uClibc,
  93. the "linuxthreads (stable/old)" may be a working fallback
  94. if you need threading at all.
  95. If you have an external binary toolchain then select the type
  96. of libpthreads it was built with.
  97. config BR2_PTHREADS_NONE
  98. bool "none"
  99. config BR2_PTHREADS
  100. bool "linuxthreads"
  101. config BR2_PTHREADS_OLD
  102. bool "linuxthreads (stable/old)"
  103. config BR2_PTHREADS_NATIVE
  104. bool "Native POSIX Threading (NPTL)"
  105. endchoice
  106. config BR2_PROGRAM_INVOCATION
  107. bool "Enable 'program invocation name'"
  108. help
  109. Support for the GNU-specific program_invocation_name and
  110. program_invocation_short_name strings. Some GNU packages
  111. (like tar and coreutils) utilize these for extra useful
  112. output, but in general are not required.
  113. If you have an external binary toolchain that has been built
  114. with program invocation support then enable this option.
  115. config BR2_GCC_CROSS_CXX
  116. bool
  117. help
  118. If you are building your own toolchain and want to build
  119. a C++ cross-compiler this needs to be enabled.
  120. If you have an external binary toolchain that has a C++ compiler
  121. and you want to use it then you need to enable this option.
  122. config BR2_INSTALL_LIBSTDCPP
  123. bool "Build/install c++ compiler and libstdc++?"
  124. select BR2_LARGEFILE if (!BR2_GCC_SUPPORTS_SYSROOT && BR2_TOOLCHAIN_BUILDROOT)
  125. select BR2_GCC_CROSS_CXX
  126. help
  127. If you are building your own toolchain and want to build and install
  128. the C++ compiler and library then you need to enable this option.
  129. If you have an external toolchain that has been built with C++
  130. support and you want to use the compiler / library then you need
  131. to select this option.
  132. config BR2_TARGET_OPTIMIZATION
  133. string "Target Optimizations"
  134. default "-Os -pipe"
  135. help
  136. Optimizations to use when building for the target host.
  137. if BR2_TOOLCHAIN_BUILDROOT
  138. source "toolchain/elf2flt/Config.in"
  139. source "toolchain/mklibs/Config.in"
  140. source "toolchain/sstrip/Config.in"
  141. config BR2_ENABLE_MULTILIB
  142. bool "Enable multilib support?"
  143. help
  144. Build libraries to support different ABIs.
  145. config BR2_VFP_FLOAT
  146. bool "Use ARM Vector Floating Point unit"
  147. depends on !BR2_SOFT_FLOAT
  148. depends on BR2_arm || BR2_armeb
  149. help
  150. Setting this option will enable the "-mfpu=vfp" option.
  151. If your ARM CPU has a Vector Floating Point Unit (VFP)
  152. and the toolchain supports the option, then the
  153. code can be optimized.
  154. Most people will answer N.
  155. config BR2_CROSS_TOOLCHAIN_TARGET_UTILS
  156. bool "Include target utils in cross toolchain"
  157. default y
  158. help
  159. When using buildroot to build a deployable cross toolchain,
  160. it is handy to include certain target apps with that toolchain
  161. as a convenience.
  162. Examples include ldd, gdbserver, and strace.
  163. Answer Y if you want these apps (if built) copied into the
  164. cross toolchain dir under <arch>-linux-uclibc/target_utils/.
  165. endif