Loading toolchain/Config.in +3 −9 Original line number Diff line number Diff line Loading @@ -16,16 +16,10 @@ config BR2_TOOLCHAIN_EXTERNAL endchoice source "toolchain/Config.in.1" source "toolchain/toolchain-buildroot/Config.in" source "toolchain/toolchain-external/Config.in" # we want gdb config in the middle of both source and external # toolchains, but mconf won't let us source the same file twice, # so put it here instead source "toolchain/gdb/Config.in" comment "Common Toolchain Options" source "toolchain/Config.in.2" source "toolchain/toolchain-common.in" source "toolchain/toolchain-buildroot/Config.in.2" source "toolchain/toolchain-external/Config.in.2" endmenu toolchain/Config.in.1→toolchain/toolchain-buildroot/Config.in +1 −1 Original line number Diff line number Diff line # # Config entries for internal toolchain backend if BR2_TOOLCHAIN_BUILDROOT source "toolchain/kernel-headers/Config.in" Loading toolchain/toolchain-buildroot/Config.in.2 0 → 100644 +37 −0 Original line number Diff line number Diff line # Buildroot backend specific options if BR2_TOOLCHAIN_BUILDROOT source "toolchain/elf2flt/Config.in" source "toolchain/mklibs/Config.in" source "toolchain/sstrip/Config.in" config BR2_ENABLE_MULTILIB bool "Enable multilib support?" help Build libraries to support different ABIs. config BR2_VFP_FLOAT bool "Use ARM Vector Floating Point unit" depends on !BR2_SOFT_FLOAT depends on BR2_arm || BR2_armeb help Setting this option will enable the "-mfpu=vfp" option. If your ARM CPU has a Vector Floating Point Unit (VFP) and the toolchain supports the option, then the code can be optimized. Most people will answer N. config BR2_CROSS_TOOLCHAIN_TARGET_UTILS bool "Include target utils in cross toolchain" default y help When using buildroot to build a deployable cross toolchain, it is handy to include certain target apps with that toolchain as a convenience. Examples include ldd, gdbserver, and strace. Answer Y if you want these apps (if built) copied into the cross toolchain dir under <arch>-linux-uclibc/target_utils/. endif toolchain/Config.in.2→toolchain/toolchain-common.in +9 −37 Original line number Diff line number Diff line # # Generic toolchain options # we want gdb config in the middle of both source and external # toolchains, but mconf won't let us source the same file twice, # so put it here instead source "toolchain/gdb/Config.in" comment "Common Toolchain Options" config BR2_LARGEFILE bool "Enable large file (files > 2 GB) support?" depends on !BR2_cris Loading Loading @@ -162,39 +170,3 @@ config BR2_TARGET_OPTIMIZATION help Optimizations to use when building for the target host. NOTE: gcc optimization level is defined in build options. if BR2_TOOLCHAIN_BUILDROOT source "toolchain/elf2flt/Config.in" source "toolchain/mklibs/Config.in" source "toolchain/sstrip/Config.in" config BR2_ENABLE_MULTILIB bool "Enable multilib support?" help Build libraries to support different ABIs. config BR2_VFP_FLOAT bool "Use ARM Vector Floating Point unit" depends on !BR2_SOFT_FLOAT depends on BR2_arm || BR2_armeb help Setting this option will enable the "-mfpu=vfp" option. If your ARM CPU has a Vector Floating Point Unit (VFP) and the toolchain supports the option, then the code can be optimized. Most people will answer N. config BR2_CROSS_TOOLCHAIN_TARGET_UTILS bool "Include target utils in cross toolchain" default y help When using buildroot to build a deployable cross toolchain, it is handy to include certain target apps with that toolchain as a convenience. Examples include ldd, gdbserver, and strace. Answer Y if you want these apps (if built) copied into the cross toolchain dir under <arch>-linux-uclibc/target_utils/. endif Loading
toolchain/Config.in +3 −9 Original line number Diff line number Diff line Loading @@ -16,16 +16,10 @@ config BR2_TOOLCHAIN_EXTERNAL endchoice source "toolchain/Config.in.1" source "toolchain/toolchain-buildroot/Config.in" source "toolchain/toolchain-external/Config.in" # we want gdb config in the middle of both source and external # toolchains, but mconf won't let us source the same file twice, # so put it here instead source "toolchain/gdb/Config.in" comment "Common Toolchain Options" source "toolchain/Config.in.2" source "toolchain/toolchain-common.in" source "toolchain/toolchain-buildroot/Config.in.2" source "toolchain/toolchain-external/Config.in.2" endmenu
toolchain/Config.in.1→toolchain/toolchain-buildroot/Config.in +1 −1 Original line number Diff line number Diff line # # Config entries for internal toolchain backend if BR2_TOOLCHAIN_BUILDROOT source "toolchain/kernel-headers/Config.in" Loading
toolchain/toolchain-buildroot/Config.in.2 0 → 100644 +37 −0 Original line number Diff line number Diff line # Buildroot backend specific options if BR2_TOOLCHAIN_BUILDROOT source "toolchain/elf2flt/Config.in" source "toolchain/mklibs/Config.in" source "toolchain/sstrip/Config.in" config BR2_ENABLE_MULTILIB bool "Enable multilib support?" help Build libraries to support different ABIs. config BR2_VFP_FLOAT bool "Use ARM Vector Floating Point unit" depends on !BR2_SOFT_FLOAT depends on BR2_arm || BR2_armeb help Setting this option will enable the "-mfpu=vfp" option. If your ARM CPU has a Vector Floating Point Unit (VFP) and the toolchain supports the option, then the code can be optimized. Most people will answer N. config BR2_CROSS_TOOLCHAIN_TARGET_UTILS bool "Include target utils in cross toolchain" default y help When using buildroot to build a deployable cross toolchain, it is handy to include certain target apps with that toolchain as a convenience. Examples include ldd, gdbserver, and strace. Answer Y if you want these apps (if built) copied into the cross toolchain dir under <arch>-linux-uclibc/target_utils/. endif
toolchain/Config.in.2→toolchain/toolchain-common.in +9 −37 Original line number Diff line number Diff line # # Generic toolchain options # we want gdb config in the middle of both source and external # toolchains, but mconf won't let us source the same file twice, # so put it here instead source "toolchain/gdb/Config.in" comment "Common Toolchain Options" config BR2_LARGEFILE bool "Enable large file (files > 2 GB) support?" depends on !BR2_cris Loading Loading @@ -162,39 +170,3 @@ config BR2_TARGET_OPTIMIZATION help Optimizations to use when building for the target host. NOTE: gcc optimization level is defined in build options. if BR2_TOOLCHAIN_BUILDROOT source "toolchain/elf2flt/Config.in" source "toolchain/mklibs/Config.in" source "toolchain/sstrip/Config.in" config BR2_ENABLE_MULTILIB bool "Enable multilib support?" help Build libraries to support different ABIs. config BR2_VFP_FLOAT bool "Use ARM Vector Floating Point unit" depends on !BR2_SOFT_FLOAT depends on BR2_arm || BR2_armeb help Setting this option will enable the "-mfpu=vfp" option. If your ARM CPU has a Vector Floating Point Unit (VFP) and the toolchain supports the option, then the code can be optimized. Most people will answer N. config BR2_CROSS_TOOLCHAIN_TARGET_UTILS bool "Include target utils in cross toolchain" default y help When using buildroot to build a deployable cross toolchain, it is handy to include certain target apps with that toolchain as a convenience. Examples include ldd, gdbserver, and strace. Answer Y if you want these apps (if built) copied into the cross toolchain dir under <arch>-linux-uclibc/target_utils/. endif