toolchain/Config.in

   1 #
   2 config NATIVE_TOOLCHAIN
   3         bool
   4         prompt "Use host's toolchain" if DEVEL && BROKEN
   5         default n
   6         help
   7                 If enabled, OpenWrt will compile using your existing toolchain instead of compiling one
   8
   9 menuconfig TOOLCHAINOPTS
  10         bool "Toolchain Options" if DEVEL
  11         depends !NATIVE_TOOLCHAIN
  12
  13 menuconfig EXTRA_TARGET_ARCH
  14         bool
  15         prompt "Enable an extra toolchain target architecture" if TOOLCHAINOPTS
  16         default n
  17         help
  18           Some builds may require a 'biarch' toolchain. This option
  19           allows you to specify an additional target arch.
  20
  21           Most people will answer N here.
  22
  23         config EXTRA_TARGET_ARCH_NAME
  24                 string
  25                 prompt "Extra architecture name" if EXTRA_TARGET_ARCH
  26                 help
  27                   Specify the cpu name (eg powerpc64 or x86_64) of the
  28                   additional target architecture.
  29
  30         config EXTRA_TARGET_ARCH_OPTS
  31                 string
  32                 prompt "Extra architecture compiler options" if EXTRA_TARGET_ARCH
  33                 help
  34                   If you're specifying an addition target architecture,
  35                   you'll probably need to also provide options to make
  36                   the compiler use this alternate arch.
  37
  38                   For example, if you're building a compiler that can build
  39                   both powerpc and powerpc64 binaries, you'll need to
  40                   specify -m64 here.
  41
  42 source "toolchain/binutils/Config.in"
  43 source "toolchain/gcc/Config.in"
  44 source "toolchain/uClibc/Config.in"
  45
  46 config GDB
  47         bool
  48         prompt "Build gdb" if TOOLCHAINOPTS
  49         default n
  50         help
  51                 Enable if you want to build the gdb
  52
  53 config LARGEFILE
  54         bool
  55         prompt "Enable large file (files > 2 GB) support?" if TOOLCHAINOPTS
  56         default y
  57         help
  58                 Enable large file (files > 2 GB) support
  59
  60 config SHADOW_PASSWORDS
  61         bool
  62         prompt "Enable shadow password support?" if TOOLCHAINOPTS
  63         default y
  64         help
  65                 Enable shadow password support.
  66
  67 config SOFT_FLOAT
  68         bool
  69         prompt "Use software floating point by default" if TOOLCHAINOPTS
  70         default y
  71         depends on (arm || armeb || powerpc) && !HAS_FPU
  72         help
  73           If your target CPU does not have a Floating Point Unit (FPU) or a
  74           kernel FPU emulator, but you still wish to support floating point
  75           functions, then everything will need to be compiled with soft floating
  76           point support (-msoft-float).
  77
  78           Most people will answer N.
  79
  80 config TARGET_OPTIMIZATION
  81         string
  82         prompt "Target Optimizations" if TOOLCHAINOPTS
  83         default "-O2 -pipe -march=i686 -funit-at-a-time" if TARGET_x86_mediacenter
  84         default "-O2 -pipe -march=i486 -funit-at-a-time" if TARGET_x86
  85         default "-Os -pipe -march=i486 -funit-at-a-time" if TARGET_rdc
  86         default "-Os -pipe -mips32 -mtune=mips32 -funit-at-a-time" if mipsel || mips
  87         default "-Os -pipe -march=armv5te -mtune=xscale -funit-at-a-time" if TARGET_ixp4xx || TARGET_iop32x || TARGET_pxa || TARGET_orion
  88         default "-Os -pipe -march=armv4t -mtune=arm9tdmi -funit-at-a-time" if TARGET_storm
  89         default "-Os -pipe -funit-at-a-time"
  90         help
  91           Optimizations to use when building for the target host.
  92
  93 source "toolchain/gcc/Config.version"
  94 source "toolchain/uClibc/Config.version"