Config.in

menu "Branding"

config NETBOX_PLAT
	string "Single word lower-case identifier for the platform"
	default "basis"   if BR2_arm926t
	default "coronet" if BR2_powerpc
	default "dagger"  if BR2_arm
	default "envoy"   if BR2_aarch64
	default "zero"    if BR2_x86_64
	default BR2_ARCH

config NETBOX_VENDOR_ID
	string "Single word lower-case identifier for the operating system"
	default "netbox"
	help
	  A lower-case string (no spaces or other characters outside of
          0–9, a–z, '.', '_' and '-') identifying the operating system,
          excluding any version information and suitable for processing
          by scripts or usage in generated filenames.

	  Used for identifying the OS, e.g. as ID in /etc/os-release and
	  in the generated image name: ID-TYPE-PLAT.img

config NETBOX_VENDOR_NAME
	string "String identifier for the operating system"
	default "NetBox"
	help
	  Used for identifying the OS, e.g. as NAME in /etc/os-release

config NETBOX_VENDOR_DESC
	string "Pretty operating system name, format for presentation to user"
	default "NetBox - The Networking Toolbox"
	help
	  Used for identifying the OS, e.g. as PRETTY_NAME in /etc/os-release

config NETBOX_VENDOR_HOME
	string "Internet URL for the homepage of the operating system"
	default "https://github.com/westermo/netbox/"
	help
	  Used for identifying the OS, e.g. as HOME_URL in /etc/os-release

config NETBOX_VENDOR_VERSION
	string "Version of operating system, may be a script with ``"
	default "`$BR2_EXTERNAL_NETBOX_PATH/utils/mkversion $BR2_EXTERNAL_NETBOX_PATH`"
	help
	   A lower-case string (no spaces or other characters outside of
           0–9, a–z, '.', '_' and '-') identifying the operating system
           version, excluding any OS name information or release code
           name, and suitable for processing by scripts or usage in
           generated filenames.

	   Used for VERSION and VERSION_ID in /etc/os-release

endmenu

choice
	bool "Type"
	default NETBOX_TYPE_APP
	help
	  Select the NetBox type:

	    o Application        Basic root filesystem, no kernel
	    o Operating System   Like app + kernel

config NETBOX_TYPE_APP
	bool "Application (LXC)"
	help
	  Application build for the chosen CPU platform.  This only
	  creates a root filesystem, no kernel is built.

	  This is typically suitable for container images (LXC), but can
	  also be useful for systems where a pre-built kernel exists
	  already.

	  Selecting this pre-selects the app profile option (below),
	  this is only a recommendation.

config NETBOX_TYPE_OS
	bool "Operating System (kernel + userland)"
	help
	  Complete operating system, including kernel and userland,
	  for the chosen CPU platform.

	  This is the same as the application build, but includes a
	  kernel, and optionally a (second) stage bootloader.

	  Selecting this pre-selects the OS profile option (below),
	  this is only a recommendation.

endchoice

config NETBOX_TYPE
	string
	default "app" if NETBOX_TYPE_APP
	default "os"  if NETBOX_TYPE_OS

choice
	bool "Profile"
	default NETBOX_PROFILE_APP if NETBOX_TYPE_APP
	default NETBOX_PROFILE_OS  if NETBOX_TYPE_OS
	help
	  NetBox is built around BusyBox and Finit.  Comprising the very
	  core of the exprience of this embedded system.  On top of that
	  two main profiles are available; slimmed down applications or
	  full-blown operating systems.

	    o Applicaiton        Finit + Dropbear SSH + tcpdump
	    o Operating System   Finit + lots of tools & daemons
	    o Custom             Finit

	  See each profile for details.

config NETBOX_PROFILE_CUSTOM
	bool "Custom (minimal)"
	select BR2_PACKAGE_FINIT
	help
	  The custom profile allows more fine grained control over what
	  packages are included.  However, NetBox always has Finit as
	  its preferred init.  If you want something else, you should
	  probably skip NetBox and use buildroot directly.

config NETBOX_PROFILE_APP
	bool "Appplication (basic)"
	help
	  The application profile includes a set of basic packages
	  that usually are essential to a basic contatainer app:

	    o Dropbear SSH (server + client)
	    o tcpdump

	  SSH in to your container from remote, and support to debug
	  network connections in case SSH connection fails.

	  If you want to create a really small app and do not need these
	  tools, use the custom profile or use buildroot directly.

config NETBOX_PROFILE_OS
	bool "Operating System (full)"
	help
	  The operating system profile comes with a lot more features
	  compared to the other profiles.  The intention is to provide
	  common network services and also tools for debugging network
	  devices on all the different layers in the stack of a switch
	  or router product.

	  This profile will likely expand and change a lot over time.
	  Use the custom profile to get more fine grained control.

endchoice

config NETBOX_PROFILE
	string
	default "app"     if NETBOX_PROFILE_APP
	default "os"      if NETBOX_PROFILE_OS
	default "custom"  if NETBOX_PROFILE_CUSTOM

menu "Developer"

config NETBOX_IMAGE_FIT
	bool "Build FIT image"
	depends on NETBOX_TYPE_OS
	select BR2_PACKAGE_HOST_UBOOT_TOOLS
	select BR2_PACKAGE_HOST_UBOOT_TOOLS_FIT_SUPPORT
	select BR2_PACKAGE_HOST_UBOOT_TOOLS_FIT_SIGNATURE_SUPPORT
	help
	  Build an FIT image with all device trees in boot/, creating a
	  configuration for each, the default kernel and the SquashFS as
	  a ramdisk.

	  This is useful for testing NetBox on systems which do not have
	  a bootloader capable of loading standard images, e.g. U-Boot
	  on various evaluation/development boards.

endmenu

menu "Packages"

source "$BR2_EXTERNAL_NETBOX_PATH/package/Config.in"

endmenu