package/b*/Config.in: fix ordering of statements
The check-package script when ran gives warnings on ordering issues on all of these Config files. This patch cleans up all warnings related to the ordering in the Config files for packages starting with the letter b in the package directory. The appropriate ordering is: type, default, depends on, select, help See http://nightly.buildroot.org/#_config_files for more information. Signed-off-by: Adam Duskett <Adamduskett@outlook.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
parent
7b493e411f
commit
48bd50287f
|
@ -32,8 +32,8 @@ if BR2_PACKAGE_BANDWIDTHD
|
|||
|
||||
config BR2_PACKAGE_BANDWIDTHD_POSTGRESQL
|
||||
bool "enable postgresql log target support"
|
||||
select BR2_PACKAGE_POSTGRESQL
|
||||
depends on !BR2_STATIC_LIBS
|
||||
select BR2_PACKAGE_POSTGRESQL
|
||||
help
|
||||
Enable support for logging the bandwidthd data to a remote
|
||||
(or local) postgresql server. This data can then be viewed
|
||||
|
|
|
@ -1,10 +1,10 @@
|
|||
config BR2_PACKAGE_BASH
|
||||
bool "bash"
|
||||
select BR2_PACKAGE_NCURSES
|
||||
select BR2_PACKAGE_READLINE
|
||||
# uses fork()
|
||||
depends on BR2_USE_MMU
|
||||
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
|
||||
select BR2_PACKAGE_NCURSES
|
||||
select BR2_PACKAGE_READLINE
|
||||
help
|
||||
The standard GNU Bourne again shell.
|
||||
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
config BR2_PACKAGE_BINUTILS
|
||||
bool "binutils"
|
||||
select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALE
|
||||
depends on !BR2_nios2
|
||||
depends on BR2_USE_WCHAR
|
||||
select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALE
|
||||
help
|
||||
Install binutils on the target
|
||||
|
||||
|
|
|
@ -2,8 +2,8 @@ comment "Binutils Options"
|
|||
|
||||
choice
|
||||
prompt "Binutils Version"
|
||||
depends on !BR2_arc
|
||||
default BR2_BINUTILS_VERSION_2_27_X
|
||||
depends on !BR2_arc
|
||||
help
|
||||
Select the version of binutils you wish to use.
|
||||
|
||||
|
|
|
@ -29,8 +29,8 @@ if BR2_PACKAGE_BLUEZ5_UTILS
|
|||
|
||||
config BR2_PACKAGE_BLUEZ5_UTILS_OBEX
|
||||
bool "build OBEX support"
|
||||
select BR2_PACKAGE_LIBICAL
|
||||
depends on BR2_INSTALL_LIBSTDCPP
|
||||
select BR2_PACKAGE_LIBICAL
|
||||
help
|
||||
Enable the OBEX support in Bluez 5.x.
|
||||
|
||||
|
|
|
@ -115,9 +115,9 @@ config BR2_PACKAGE_BOOST_MATH
|
|||
bool "boost-math"
|
||||
|
||||
config BR2_PACKAGE_BOOST_METAPARSE
|
||||
bool "boost-metaparse"
|
||||
depends on BR2_USE_MMU # boost-test
|
||||
select BR2_PACKAGE_BOOST_TEST
|
||||
bool "boost-metaparse"
|
||||
|
||||
config BR2_PACKAGE_BOOST_MPI
|
||||
bool "boost-mpi"
|
||||
|
@ -126,8 +126,8 @@ config BR2_PACKAGE_BOOST_PROGRAM_OPTIONS
|
|||
bool "boost-program_options"
|
||||
|
||||
config BR2_PACKAGE_BOOST_PYTHON
|
||||
depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3
|
||||
bool "boost-python"
|
||||
depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3
|
||||
|
||||
config BR2_PACKAGE_BOOST_RANDOM
|
||||
bool "boost-random"
|
||||
|
|
|
@ -1,11 +1,11 @@
|
|||
config BR2_PACKAGE_BUSTLE
|
||||
bool "bustle"
|
||||
select BR2_PACKAGE_LIBPCAP
|
||||
select BR2_PACKAGE_LIBGLIB2
|
||||
depends on BR2_USE_WCHAR # libglib2
|
||||
depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2
|
||||
depends on BR2_USE_MMU # libglib2
|
||||
depends on BR2_PACKAGE_DBUS # runtime
|
||||
select BR2_PACKAGE_LIBPCAP
|
||||
select BR2_PACKAGE_LIBGLIB2
|
||||
help
|
||||
Bustle is a better dbus-monitor! It records and draws
|
||||
sequence diagrams of D-Bus activity, showing signal
|
||||
|
|
|
@ -35,12 +35,12 @@ config BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
|
|||
by busybox.
|
||||
|
||||
config BR2_PACKAGE_BUSYBOX_SELINUX
|
||||
select BR2_PACKAGE_LIBSELINUX
|
||||
bool "Enable SELinux support"
|
||||
depends on BR2_TOOLCHAIN_HAS_THREADS
|
||||
depends on !BR2_STATIC_LIBS
|
||||
depends on BR2_TOOLCHAIN_USES_GLIBC
|
||||
depends on !BR2_arc
|
||||
bool "Enable SELinux support"
|
||||
select BR2_PACKAGE_LIBSELINUX
|
||||
help
|
||||
Enable SELinux support in BusyBox. Please note that
|
||||
depending on your BusyBox configuration and the SELinux
|
||||
|
|
Loading…
Reference in a new issue