code stringlengths 0 21.5M | repo_name stringlengths 4 92 | path stringlengths 1 189 | language stringlengths 0 26 | license stringclasses 11
values | size int64 0 21.5M |
|---|---|---|---|---|---|
# Architecture
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_EABIHF=y
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
# System configuration
BR2_TARGET_GENERIC_HOSTNAME="a20-olinuxino"
BR2_TARGET_GENERIC_ISSUE="Welcome to OLinuXino!"
BR2_TARGET_GENERIC_GETTY=y
BR2_TARGET_GENERIC_GETTY_POR... | shibajee/buildroot | configs/olimex_a20_olinuxino_lime_defconfig | none | mit | 1,339 |
# Architecture
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_EABIHF=y
# Linux headers same as kernel, a 3.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_4=y
# System configuration
BR2_TARGET_GENERIC_HOSTNAME="a20-olinuxino"
BR2_TARGET_GENERIC_ISSUE="Welcome to OLinuXino!"
BR2_TARGET_GENERIC_GETTY=y
BR2_TARGET_GENERIC_GETTY_POR... | shibajee/buildroot | configs/olimex_a20_olinuxino_lime_mali_defconfig | none | mit | 1,493 |
# Architecture
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_FPU_NEON_VFPV4=y
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
# System configuration
BR2_TARGET_GENERIC_HOSTNAME="a20-olinuxino"
BR2_TARGET_GENERIC_ISSUE="Welcome to OLinuXino!"
BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
BR2_SYSTE... | shibajee/buildroot | configs/olimex_a20_olinuxino_micro_defconfig | none | mit | 1,284 |
# Architecture
BR2_arm=y
BR2_arm926t=y
# System
BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
# For automatic firmware loading
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
# Kernel
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_18=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.18.2"
... | shibajee/buildroot | configs/olimex_imx233_olinuxino_defconfig | none | mit | 1,349 |
# Architecture
BR2_arm=y
BR2_arm926t=y
# system
BR2_TARGET_GENERIC_HOSTNAME="openblocks-a6"
BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
# filesystem
BR2_TARGET_ROOTFS_JFFS2=y
BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K=y
# Linux headers same as kernel, a 3.18 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_18=y
# kernel
BR2_LI... | shibajee/buildroot | configs/openblocks_a6_defconfig | none | mit | 587 |
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_FPU_VFPV4=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_6=y
BR2_TARGET_GENERIC_HOSTNAME="OrangePi_PC"
BR2_TARGET_GENERIC_ISSUE="Welcome to Buildroot for the Orange Pi PC"
BR2_ROOTFS_POST_BUILD_SCRIPT="board/orangepi/orangepipc/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/orangepi/ora... | shibajee/buildroot | configs/orangepipc_defconfig | none | mit | 1,080 |
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_5=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyO2"
BR2_SYSTEM_DHCP="eth0"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/pandaboard/post-image.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM... | shibajee/buildroot | configs/pandaboard_defconfig | none | mit | 1,000 |
# Architecture
BR2_x86_64=y
# Toolchain, required for eudev (to autoload drivers)
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
# System
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
# Required tools to create bootable media
BR2_PACKAGE_HOST_GENIMAGE=y
# Bootloader
BR2_TARGET_GRUB2=y
# Filesyst... | shibajee/buildroot | configs/pc_x86_64_bios_defconfig | none | mit | 1,857 |
# Architecture
BR2_x86_64=y
# Toolchain, required for eudev (to autoload drivers)
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
# System
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
# Required tools to create bootable media
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HO... | shibajee/buildroot | configs/pc_x86_64_efi_defconfig | none | mit | 1,943 |
# Architecture
BR2_aarch64=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
# Filesystem
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ROOTFS_INITRAMFS=y
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUS... | shibajee/buildroot | configs/qemu_aarch64_virt_defconfig | none | mit | 494 |
# Architecture
BR2_arm=y
BR2_arm926t=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNE... | shibajee/buildroot | configs/qemu_arm_versatile_defconfig | none | mit | 579 |
# Architecture
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_ARM_FPU_VFPV3D16=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LIN... | shibajee/buildroot | configs/qemu_arm_vexpress_defconfig | none | mit | 572 |
# Architecture
BR2_m68k=y
BR2_m68k_cf5208=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_INITRAMFS=y
# BR2_TARGET_ROOTFS_TAR is not set
BR2_GLOBAL_PATCH_DIR="board/qemu/m68k-mcf5208/patches"
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINU... | shibajee/buildroot | configs/qemu_m68k_mcf5208_defconfig | none | mit | 761 |
# Architecture
BR2_m68k=y
BR2_m68k_68040=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_... | shibajee/buildroot | configs/qemu_m68k_q800_defconfig | none | mit | 574 |
# Architecture
BR2_microblaze=y
BR2_microblazebe=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttyUL0"
# Filesystem
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ROOTFS_INITRAMFS=y
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y... | shibajee/buildroot | configs/qemu_microblazebe_mmu_defconfig | none | mit | 624 |
# Architecture
BR2_microblaze=y
BR2_microblazeel=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttyUL0"
# Filesystem
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ROOTFS_INITRAMFS=y
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y... | shibajee/buildroot | configs/qemu_microblazeel_mmu_defconfig | none | mit | 624 |
# Architecture
BR2_mips=y
BR2_mips_32r2=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_C... | shibajee/buildroot | configs/qemu_mips32r2_malta_defconfig | none | mit | 578 |
# Architecture
BR2_mipsel=y
BR2_mips_32r2=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL... | shibajee/buildroot | configs/qemu_mips32r2el_malta_defconfig | none | mit | 582 |
# Architecture
BR2_mips=y
BR2_mips_32r6=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_C... | shibajee/buildroot | configs/qemu_mips32r6_malta_defconfig | none | mit | 687 |
# Architecture
BR2_mipsel=y
BR2_mips_32r6=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL... | shibajee/buildroot | configs/qemu_mips32r6el_malta_defconfig | none | mit | 693 |
# Architecture
BR2_mips64=y
BR2_MIPS_NABI64=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERN... | shibajee/buildroot | configs/qemu_mips64_malta_defconfig | none | mit | 580 |
# Architecture
BR2_mips64el=y
BR2_MIPS_NABI64=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KE... | shibajee/buildroot | configs/qemu_mips64el_malta_defconfig | none | mit | 584 |
# Architecture
BR2_mips64=y
BR2_mips_64r6=y
BR2_MIPS_NABI64=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=... | shibajee/buildroot | configs/qemu_mips64r6_malta_defconfig | none | mit | 707 |
# Architecture
BR2_mips64el=y
BR2_mips_64r6=y
BR2_MIPS_NABI64=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSIO... | shibajee/buildroot | configs/qemu_mips64r6el_malta_defconfig | none | mit | 711 |
# Architecture
BR2_powerpc64=y
BR2_powerpc_power7=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="hvc0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_L... | shibajee/buildroot | configs/qemu_ppc64_pseries_defconfig | none | mit | 457 |
# Architecture
BR2_powerpc=y
BR2_powerpc_750=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KER... | shibajee/buildroot | configs/qemu_ppc_g3beige_defconfig | none | mit | 580 |
# Architecture
BR2_powerpc=y
BR2_powerpc_8548=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ROOTFS_INITRAMFS=y
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LIN... | shibajee/buildroot | configs/qemu_ppc_mpc8544ds_defconfig | none | mit | 588 |
# Architecture
BR2_powerpc=y
BR2_powerpc_440=y
# Filesystem
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ROOTFS_INITRAMFS=y
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Use soft float
BR2_SOFT_FLOAT=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LI... | shibajee/buildroot | configs/qemu_ppc_virtex_ml507_defconfig | none | mit | 587 |
# Architecture
BR2_sh=y
BR2_sh4=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttySC1"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Linux kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNE... | shibajee/buildroot | configs/qemu_sh4_r2d_defconfig | none | mit | 520 |
# Architecture
BR2_sh=y
BR2_sh4eb=y
# System
BR2_TARGET_GENERIC_GETTY_PORT="ttySC1"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Linux kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR... | shibajee/buildroot | configs/qemu_sh4eb_r2d_defconfig | none | mit | 501 |
# Architecture
BR2_sparc64=y
BR2_sparc_v9=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Linux kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_... | shibajee/buildroot | configs/qemu_sparc64_sun4u_defconfig | none | mit | 471 |
# Architecture
BR2_sparc=y
BR2_sparc_v8=y
# System
BR2_SYSTEM_DHCP="eth0"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Linux kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KE... | shibajee/buildroot | configs/qemu_sparc_ss10_defconfig | none | mit | 466 |
# Architecture
BR2_x86_64=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSI... | shibajee/buildroot | configs/qemu_x86_64_defconfig | none | mit | 479 |
# Architecture
BR2_i386=y
BR2_x86_pentiumpro=y
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_7=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_... | shibajee/buildroot | configs/qemu_x86_defconfig | none | mit | 495 |
# Architecture
BR2_xtensa=y
BR2_XTENSA_CUSTOM=y
BR2_XTENSA_CUSTOM_NAME="dc233c"
BR2_XTENSA_CORE_NAME="lx60"
BR2_XTENSA_OVERLAY_DIR="board/qemu/xtensa-lx60"
# Patches
BR2_GLOBAL_PATCH_DIR="board/qemu/xtensa-lx60"
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
# Filesystem
# BR2_TARGET_ROOTFS_TA... | shibajee/buildroot | configs/qemu_xtensa_lx60_defconfig | none | mit | 798 |
# Architecture
BR2_xtensa=y
BR2_XTENSA_CUSTOM=y
BR2_XTENSA_CUSTOM_NAME="dc233c"
BR2_XTENSA_CORE_NAME="lx60"
BR2_XTENSA_OVERLAY_DIR="board/qemu/xtensa-lx60"
# Toolchain
BR2_PACKAGE_HOST_ELF2FLT=y
# BR2_USE_MMU is not set
# Patches
BR2_GLOBAL_PATCH_DIR="board/qemu/xtensa-lx60"
# System
BR2_SYSTEM_DHCP="eth0"
BR2_TARGE... | shibajee/buildroot | configs/qemu_xtensa_lx60_nommu_defconfig | none | mit | 869 |
BR2_arm=y
BR2_cortex_a9=y
# Linux headers same as kernel, a 3.14 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_14=y
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc1"
# Notice you need a recent version of u-boot (with DT support) to be able
# to boot this kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_... | shibajee/buildroot | configs/qmx6_defconfig | none | mit | 1,217 |
BR2_arm=y
BR2_arm1176jzf_s=y
BR2_ARM_EABIHF=y
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
BR2_LINUX_KERNEL_CUSTOM_REP... | shibajee/buildroot | configs/raspberrypi0_defconfig | none | mit | 1,066 |
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_EABIHF=y
BR2_ARM_FPU_NEON_VFPV4=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_SYSTEM_DHCP="eth0"
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/rasp... | shibajee/buildroot | configs/raspberrypi2_defconfig | none | mit | 1,028 |
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_EABIHF=y
BR2_ARM_FPU_NEON_VFPV4=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_SYSTEM_DHCP="eth0"
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/rasp... | shibajee/buildroot | configs/raspberrypi3_defconfig | none | mit | 1,028 |
BR2_arm=y
BR2_arm1176jzf_s=y
BR2_ARM_EABIHF=y
BR2_SYSTEM_DHCP="eth0"
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
BR2... | shibajee/buildroot | configs/raspberrypi_defconfig | none | mit | 1,070 |
# architecture
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
# system
BR2_TARGET_GENERIC_GETTY=y
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc1"
# rootfs
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_2r1=y
BR2_ROOTFS_OVERLAY="board/embest/riotboard/rootfs_overlay"
# bootloader
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_CUSTOM_V... | shibajee/buildroot | configs/riotboard_defconfig | none | mit | 873 |
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_GLOBAL_PATCH_DIR="board/roseapplepi/patches"
# Linux headers same as kernel, a 3.10 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_10=y
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/roseapplepi/post-image.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT... | shibajee/buildroot | configs/roseapplepi_defconfig | none | mit | 1,353 |
BR2_microblaze=y
BR2_microblazeel=y
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyUL0"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ROOTFS_INITRAMFS=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE=... | shibajee/buildroot | configs/s6lx9_microboard_defconfig | none | mit | 560 |
# Architecture
BR2_arm=y
BR2_arm926t=y
# system
BR2_TARGET_GENERIC_GETTY=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
BR2_SYSTEM_DHCP="eth0"
# filesystem
BR2_TARGET_ROOTFS_JFFS2=y
BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K=y
# Linux headers same as kernel, a 4.6 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_6=y
# bootloade... | shibajee/buildroot | configs/sheevaplug_defconfig | none | mit | 854 |
BR2_aarch64=y
# Linux headers same as kernel, a 3.18 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_18=y
BR2_TARGET_GENERIC_HOSTNAME="vdk-buildroot"
BR2_TARGET_GENERIC_ISSUE="Welcome to SNPS VDK by Buildroot"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://git.linaro.org/kerne... | shibajee/buildroot | configs/snps_aarch64_vdk_defconfig | none | mit | 623 |
# Architecture
BR2_arcle=y
# System
BR2_TARGET_GENERIC_HOSTNAME="axs101"
BR2_TARGET_GENERIC_ISSUE="Welcome to the ARC Software Development Platform"
BR2_TARGET_ROOTFS_INITRAMFS=y
BR2_SYSTEM_DHCP="eth0"
BR2_ROOTFS_OVERLAY="board/synopsys/axs10x/fs-overlay"
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_... | shibajee/buildroot | configs/snps_axs101_defconfig | none | mit | 716 |
# Architecture
BR2_arcle=y
BR2_archs38=y
# System
BR2_TARGET_GENERIC_HOSTNAME="axs103"
BR2_TARGET_GENERIC_ISSUE="Welcome to the ARC Software Development Platform"
BR2_TARGET_ROOTFS_INITRAMFS=y
BR2_SYSTEM_DHCP="eth0"
BR2_ROOTFS_OVERLAY="board/synopsys/axs10x/fs-overlay"
# Linux headers same as kernel, a 4.7 series
BR2... | shibajee/buildroot | configs/snps_axs103_defconfig | none | mit | 734 |
# Architecture
BR2_arcle=y
BR2_archs38=y
# System
BR2_TARGET_GENERIC_HOSTNAME="hs38_vdk"
BR2_TARGET_GENERIC_ISSUE="Welcome to the HS38 VDK Software Development Platform"
BR2_ROOTFS_OVERLAY="board/synopsys/axs10x/fs-overlay"
BR2_TARGET_ROOTFS_EXT2=y
# Linux headers same as kernel, a 4.7 series
BR2_PACKAGE_HOST_LINUX_H... | shibajee/buildroot | configs/snps_hs38_smp_vdk_defconfig | none | mit | 516 |
BR2_arm=y
BR2_cortex_m4=y
BR2_GLOBAL_PATCH_DIR="board/stmicroelectronics/stm32f429-disco/patches"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_5=y
BR2_ROOTFS_POST_BUILD_SCRIPT="board/stmicroelectronics/stm32-post-build.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.5"
BR2_L... | shibajee/buildroot | configs/stm32f429_disco_defconfig | none | mit | 703 |
BR2_arm=y
BR2_cortex_m4=y
BR2_GLOBAL_PATCH_DIR="board/stmicroelectronics/stm32f469-disco/patches"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_5=y
BR2_ROOTFS_POST_BUILD_SCRIPT="board/stmicroelectronics/stm32-post-build.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.5"
BR2_L... | shibajee/buildroot | configs/stm32f469_disco_defconfig | none | mit | 797 |
# Architecture
BR2_arm=y
BR2_arm926t=y
# Linux headers same as kernel, a 3.9 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_9=y
# Watchdog is armed by the first stage bootloader
BR2_PACKAGE_BUSYBOX_WATCHDOG=y
# Filesystem
BR2_TARGET_ROOTFS_UBIFS=y
BR2_TARGET_ROOTFS_UBI=y
# Bootloader
BR2_TARGET_BAREBOX=y
BR2_TARGET... | shibajee/buildroot | configs/telit_evk_pro3_defconfig | none | mit | 810 |
BR2_arm=y
BR2_cortex_a9=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_14=y
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/toradex/apalis-imx6/post-image.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.toradex.com/linux-toradex.git"
BR2_LINUX_KERN... | shibajee/buildroot | configs/toradex_apalis_imx6_defconfig | none | mit | 1,065 |
BR2_arm=y
BR2_cortex_a8=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_6=y
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/technologic/ts4800/post-image.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.6.3"
BR2_LINUX_KERNEL_DEFCONFIG="imx_v6_v7"
BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="bo... | shibajee/buildroot | configs/ts4800_defconfig | none | mit | 770 |
# architecture
BR2_i386=y
BR2_x86_i586=y
# Linux headers same as kernel, a 3.17 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_17=y
# system
BR2_TARGET_GENERIC_GETTY_PORT="ttyS1"
BR2_ROOTFS_OVERLAY="board/technologic/ts5x00/fs-overlay"
# kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CU... | shibajee/buildroot | configs/ts5x00_defconfig | none | mit | 624 |
# Architceture
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
# Linux headers same as kernel, a 3.0 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_0=y
# System
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc1"
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/UDOObo... | shibajee/buildroot | configs/udoo_quad_defconfig | none | mit | 1,053 |
# Architecture
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
# Linux headers same as kernel, a 3.10 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_10=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/viaembedded/vab820-kernel-bsp.git"
BR2_LINUX_KERNEL_CU... | shibajee/buildroot | configs/via_imx6_vab820_defconfig | none | mit | 1,043 |
BR2_arm=y
BR2_cortex_a9=y
# Linux headers same as kernel, a 3.14 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_14=y
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/wandboard/post-image.sh"
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_UBOOT=y
BR2... | shibajee/buildroot | configs/wandboard_defconfig | none | mit | 1,110 |
# architecture
BR2_arm=y
BR2_cortex_a9=y
# Linux headers same as kernel, a 4.4 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
# system
BR2_TARGET_GENERIC_HOSTNAME="warpboard"
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
# rootfs overlay
BR2_ROOTFS_OVERLAY="board/freescale/warpboard/rootfs_overlay"
# kernel
BR2_LINUX... | shibajee/buildroot | configs/warpboard_defconfig | none | mit | 1,346 |
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/Xilinx/linux-xlnx.git"
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xilinx-v2016.2"
BR2_LINUX_... | shibajee/buildroot | configs/zynq_microzed_defconfig | none | mit | 973 |
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/Xilinx/linux-xlnx.git"
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xilin... | shibajee/buildroot | configs/zynq_zc706_defconfig | none | mit | 993 |
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/Xilinx/linux-xlnx.git"
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xilinx-v2016.2"
BR2_LINUX_... | shibajee/buildroot | configs/zynq_zed_defconfig | none | mit | 968 |
# Refer to following asciidoc documentation:
# http://www.methods.co.nz/asciidoc/userguide.html
# In particular sections "Macros" and "Attribute References"
#
# For hyperlinks, show 'link text [URL]' (if link text provided) or 'URL'
[http-inlinemacro]
{0=}{0? [}{name}:{target}{0?]}
[https-inlinemacro]
{0=}{... | shibajee/buildroot | docs/conf/asciidoc-text.conf | INI | mit | 687 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[adding-board-support]]
== Adding support for a particular board
Buildroot contains basic configurations for several publicly available
hardware boards, so that users of such a board can easily build a system
that is known to work. You are welcome to add support for ... | shibajee/buildroot | docs/manual/adding-board-support.txt | Text | mit | 1,898 |
// -*- mode:doc; -*-
// vim: syntax=asciidoc
=== Infrastructure for asciidoc documents
[[asciidoc-documents-tutorial]]
The Buildroot manual, which you are currently reading, is entirely written
using the http://asciidoc.org/[AsciiDoc] mark-up syntax. The manual is then
rendered to many formats:
* html
* split-html
... | shibajee/buildroot | docs/manual/adding-packages-asciidoc.txt | Text | mit | 4,283 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for autotools-based packages
[[autotools-package-tutorial]]
==== +autotools-package+ tutorial
First, let's see how to write a +.mk+ file for an autotools-based
package, with an example :
------------------------
01: ##############################... | shibajee/buildroot | docs/manual/adding-packages-autotools.txt | Text | mit | 7,503 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for CMake-based packages
[[cmake-package-tutorial]]
==== +cmake-package+ tutorial
First, let's see how to write a +.mk+ file for a CMake-based package,
with an example :
------------------------
01: ###############################################... | shibajee/buildroot | docs/manual/adding-packages-cmake.txt | Text | mit | 6,547 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Conclusion
As you can see, adding a software package to Buildroot is simply a
matter of writing a Makefile using an existing example and modifying it
according to the compilation process required by the package.
If you package software that might be useful for ot... | shibajee/buildroot | docs/manual/adding-packages-conclusion.txt | Text | mit | 425 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Package directory
First of all, create a directory under the +package+ directory for
your software, for example +libfoo+.
Some packages have been grouped by topic in a sub-directory:
+x11r7+, +efl+ and +matchbox+. If your package fits in
one of these categories, ... | shibajee/buildroot | docs/manual/adding-packages-directory.txt | Text | mit | 19,752 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for packages with specific build systems
By 'packages with specific build systems' we mean all the packages
whose build system is not one of the standard ones, such as
'autotools' or 'CMake'. This typically includes packages whose build
system is ba... | shibajee/buildroot | docs/manual/adding-packages-generic.txt | Text | mit | 25,391 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Gettext integration and interaction with packages
Many packages that support internationalization use the gettext
library. Dependencies for this library are fairly complicated and
therefore, deserve some explanation.
The 'uClibc' C library doesn't implement gette... | shibajee/buildroot | docs/manual/adding-packages-gettext.txt | Text | mit | 2,221 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[hooks]]
=== Hooks available in the various build steps
The generic infrastructure (and as a result also the derived autotools
and cmake infrastructures) allow packages to specify hooks.
These define further actions to perform after existing steps.
Most hooks aren't ... | shibajee/buildroot | docs/manual/adding-packages-hooks.txt | Text | mit | 2,927 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for packages using kconfig for configuration files
A popular way for a software package to handle user-specified
configuration is +kconfig+. Among others, it is used by the Linux
kernel, Busybox, and Buildroot itself. The presence of a .config file
... | shibajee/buildroot | docs/manual/adding-packages-kconfig.txt | Text | mit | 3,346 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for packages building kernel modules
Buildroot offers a helper infrastructure to make it easy to write packages that
build and install Linux kernel modules. Some packages only contain a kernel
module, other packages contain programs and libraries in... | shibajee/buildroot | docs/manual/adding-packages-kernel-module.txt | Text | mit | 5,097 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[linux-kernel-specific-infra]]
=== Infrastructure specific to the Linux kernel package
The Linux kernel package can use some specific infrastructures based on package
hooks for building Linux kernel tools or/and building Linux kernel extensions.
[[linux-kernel-tools... | shibajee/buildroot | docs/manual/adding-packages-linux-kernel-spec-infra.txt | Text | mit | 5,614 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for LuaRocks-based packages
[[luarocks-package-tutorial]]
==== +luarocks-package+ tutorial
First, let's see how to write a +.mk+ file for a LuaRocks-based package,
with an example :
------------------------
01: ###################################... | shibajee/buildroot | docs/manual/adding-packages-luarocks.txt | Text | mit | 3,408 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for Perl/CPAN packages
[[perl-package-tutorial]]
==== +perl-package+ tutorial
First, let's see how to write a +.mk+ file for a Perl/CPAN package,
with an example :
------------------------
01: #####################################################... | shibajee/buildroot | docs/manual/adding-packages-perl.txt | Text | mit | 4,678 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for Python packages
This infrastructure applies to Python packages that use the standard
Python setuptools mechanism as their build system, generally
recognizable by the usage of a +setup.py+ script.
[[python-package-tutorial]]
==== +python-packag... | shibajee/buildroot | docs/manual/adding-packages-python.txt | Text | mit | 10,099 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for rebar-based packages
[[rebar-package-tutorial]]
==== +rebar-package+ tutorial
First, let's see how to write a +.mk+ file for a rebar-based package,
with an example :
------------------------------
01: #########################################... | shibajee/buildroot | docs/manual/adding-packages-rebar.txt | Text | mit | 3,974 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Tips and tricks
[[package-name-variable-relation]]
==== Package name, config entry name and makefile variable relationship
In Buildroot, there is some relationship between:
* the _package name_, which is the package directory name (and the
name of the +*.mk+ f... | shibajee/buildroot | docs/manual/adding-packages-tips.txt | Text | mit | 2,784 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Infrastructure for virtual packages
[[virtual-package-tutorial]]
In Buildroot, a virtual package is a package whose functionalities are
provided by one or more packages, referred to as 'providers'. The virtual
package management is an extensible mechanism allowin... | shibajee/buildroot | docs/manual/adding-packages-virtual.txt | Text | mit | 4,832 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[adding-packages]]
== Adding new packages to Buildroot
This section covers how new packages (userspace libraries or
applications) can be integrated into Buildroot. It also shows how
existing packages are integrated, which is needed for fixing issues or
tuning their c... | shibajee/buildroot | docs/manual/adding-packages.txt | Text | mit | 1,032 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Advanced usage
include::using-buildroot-toolchain.txt[]
include::using-buildroot-debugger.txt[]
include::ccache-support.txt[]
include::download-location.txt[]
include::package-make-target.txt[]
include::using-buildroot-development.txt[]
| shibajee/buildroot | docs/manual/advanced.txt | Text | mit | 298 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
include::makedev-syntax.txt[]
include::makeusers-syntax.txt[]
// Automatically generated lists:
[[package-list]]
== List of target packages available in Buildroot
include::package-list.txt[]
[[virtual-package-list]]
== List of virtual packages
These are the virtu... | shibajee/buildroot | docs/manual/appendix.txt | Text | mit | 1,183 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
== Beyond Buildroot
=== Boot the generated images
==== NFS boot
To achieve NFS-boot, enable _tar root filesystem_ in the _Filesystem
images_ menu.
After a complete build, just run the following commands to setup the
NFS-root directory:
-------------------
sudo tar... | shibajee/buildroot | docs/manual/beyond-buildroot.txt | Text | mit | 1,914 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[ccache]]
==== Using +ccache+ in Buildroot
http://ccache.samba.org[ccache] is a compiler cache. It stores the
object files resulting from each compilation process, and is able to
skip future compilation of the same source file (with same compiler
and same arguments) ... | shibajee/buildroot | docs/manual/ccache-support.txt | Text | mit | 2,323 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
== General Buildroot usage
include::make-tips.txt[]
include::rebuilding-packages.txt[]
=== Offline builds
If you intend to do an offline build and just want to download
all sources that you previously selected in the configurator
('menuconfig', 'nconfig', 'xconfig'... | shibajee/buildroot | docs/manual/common-usage.txt | Text | mit | 12,018 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
== Configuration of other components
Before attempting to modify any of the components below, make sure you
have already configured Buildroot itself, and have enabled the
corresponding package.
BusyBox::
+
If you already have a BusyBox configuration file, you can dir... | shibajee/buildroot | docs/manual/configure-other-components.txt | Text | mit | 2,189 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[configure]]
== Buildroot configuration
All the configuration options in +make *config+ have a help text
providing details about the option.
The +make *config+ commands also offer a search tool. Read the help
message in the different frontend menus to know how to us... | shibajee/buildroot | docs/manual/configure.txt | Text | mit | 19,496 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
== Contributing to Buildroot
There are many ways in which you can contribute to Buildroot: analyzing
and fixing bugs, analyzing and fixing package build failures detected by
the autobuilders, testing and reviewing patches sent by other
developers, working on the items... | shibajee/buildroot | docs/manual/contribute.txt | Text | mit | 19,266 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[customize-store-buildroot-config]]
=== Storing the Buildroot configuration
The Buildroot configuration can be stored using the command
+make savedefconfig+.
This strips the Buildroot configuration down by removing configuration
options that are at their default va... | shibajee/buildroot | docs/manual/customize-configuration.txt | Text | mit | 2,965 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[customize-device-permission]]
==== Setting file permissions and ownership and adding custom devices nodes
Sometimes it is needed to set specific permissions or ownership on files
or device nodes. For example, certain files may need to be owned by
root. Since the pos... | shibajee/buildroot | docs/manual/customize-device-permission-tables.txt | Text | mit | 1,368 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[customize-dir-structure]]
=== Recommended directory structure
When customizing Buildroot for your project, you will be creating one or
more project-specific files that need to be stored somewhere. While most
of these files could be placed in _any_ location as their ... | shibajee/buildroot | docs/manual/customize-directory-structure.txt | Text | mit | 3,589 |
// -*- mode:doc -*- ;
// vim: set syntax=asciidoc:
[[outside-br-custom]]
=== Keeping customizations outside of Buildroot
As already briefly mentioned in xref:customize-dir-structure[], you can
place project-specific customizations in two locations:
* directly within the Buildroot tree, typically maintaining them us... | shibajee/buildroot | docs/manual/customize-outside-br.txt | Text | mit | 4,139 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[customize-packages]]
=== Adding project-specific packages
In general, any new package should be added directly in the +package+
directory and submitted to the Buildroot upstream project. How to add
packages to Buildroot in general is explained in full detail in
xref... | shibajee/buildroot | docs/manual/customize-packages.txt | Text | mit | 2,816 |
// -*- mode:doc -*- ;
// vim: set syntax=asciidoc:
[[customize-patches]]
=== Adding project-specific patches
It is sometimes useful to apply 'extra' patches to packages - on top of
those provided in Buildroot. This might be used to support custom
features in a project, for example, or when working on a new
architectu... | shibajee/buildroot | docs/manual/customize-patches.txt | Text | mit | 2,299 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Customization _after_ the images have been created
While post-build scripts (xref:rootfs-custom[]) are run _before_
building the filesystem image, kernel and bootloader, *post-image
scripts* can be used to perform some specific actions _after_ all images
have been... | shibajee/buildroot | docs/manual/customize-post-image.txt | Text | mit | 1,815 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
=== Quick guide to storing your project-specific customizations
Earlier in this chapter, the different methods for making
project-specific customizations have been described. This section will
now summarize all this by providing step-by-step instructions to storing yo... | shibajee/buildroot | docs/manual/customize-quick-guide.txt | Text | mit | 3,377 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[rootfs-custom]]
=== Customizing the generated target filesystem
Besides changing the configuration through +make *config+,
there are a few other ways to customize the resulting target filesystem.
The two recommended methods, which can co-exist, are root filesystem
... | shibajee/buildroot | docs/manual/customize-rootfs.txt | Text | mit | 6,422 |
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[customize-users]]
=== Adding custom user accounts
Sometimes it is needed to add specific users in the target system.
To cover this requirement, Buildroot provides support for so-called
_users tables_. To use this feature, set config option
+BR2_ROOTFS_USERS_TABLES+ ... | shibajee/buildroot | docs/manual/customize-users-tables.txt | Text | mit | 752 |