code
string
repo_name
string
path
string
language
string
license
string
size
int64
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[customize]] == Project-specific customization Typical actions you may need to perform for a given project are: * configuring Buildroot (including build options and toolchain, bootloader, kernel, package and filesystem image type selection) * configuring other components, like the Linux kernel and BusyBox * customizing the generated target filesystem ** adding or overwriting files on the target filesystem (using +BR2_ROOTFS_OVERLAY+) ** modifying or deleting files on the target filesystem (using +BR2_ROOTFS_POST_BUILD_SCRIPT+) ** running arbitrary commands prior to generating the filesystem image (using +BR2_ROOTFS_POST_BUILD_SCRIPT+) ** setting file permissions and ownership (using +BR2_ROOTFS_DEVICE_TABLE+) ** adding custom devices nodes (using +BR2_ROOTFS_STATIC_DEVICE_TABLE+) * adding custom user accounts (using +BR2_ROOTFS_USERS_TABLES+) * running arbitrary commands after generating the filesystem image (using +BR2_ROOTFS_POST_IMAGE_SCRIPT+) * adding project-specific patches to some packages (using +BR2_GLOBAL_PATCH_DIR+) * adding project-specific packages An important note regarding such 'project-specific' customizations: please carefully consider which changes are indeed project-specific and which changes are also useful to developers outside your project. The Buildroot community highly recommends and encourages the upstreaming of improvements, packages and board support to the official Buildroot project. Of course, it is sometimes not possible or desirable to upstream because the changes are highly specific or proprietary. This chapter describes how to make such project-specific customizations in Buildroot and how to store them in a way that you can build the same image in a reproducible way, even after running 'make clean'. By following the recommended strategy, you can even use the same Buildroot tree to build multiple distinct projects! include::customize-directory-structure.txt[] include::customize-outside-br.txt[] include::customize-configuration.txt[] include::customize-rootfs.txt[] include::customize-users-tables.txt[] include::customize-post-image.txt[] include::customize-patches.txt[] include::customize-packages.txt[] include::customize-quick-guide.txt[]
shibajee/buildroot
docs/manual/customize.txt
Text
mit
2,316
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[debugging-buildroot]] == Debugging Buildroot It is possible to instrument the steps +Buildroot+ does when building packages. Define the variable +BR2_INSTRUMENTATION_SCRIPTS+ to contain the path of one or more scripts (or other executables), in a space-separated list, you want called before and after each step. The scripts are called in sequence, with three parameters: - +start+ or +end+ to denote the start (resp. the end) of a step; - the name of the step about to be started, or which just ended; - the name of the package. For example : ---- make BR2_INSTRUMENTATION_SCRIPTS="/path/to/my/script1 /path/to/my/script2" ---- The list of steps is: - +extract+ - +patch+ - +configure+ - +build+ - +install-host+, when a host-package is installed in +$(HOST_DIR)+ - +install-target+, when a target-package is installed in +$(TARGET_DIR)+ - +install-staging+, when a target-package is installed in +$(STAGING_DIR)+ - +install-image+, when a target-package installs files in +$(BINARIES_DIR)+ The script has access to the following variables: - +BR2_CONFIG+: the path to the Buildroot .config file - +HOST_DIR+, +STAGING_DIR+, +TARGET_DIR+: see xref:generic-package-reference[] - +BUILD_DIR+: the directory where packages are extracted and built - +BINARIES_DIR+: the place where all binary files (aka images) are stored - +BASE_DIR+: the base output directory
shibajee/buildroot
docs/manual/debugging-buildroot.txt
Text
mit
1,462
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[download-infra]] == Download infrastructure TODO
shibajee/buildroot
docs/manual/download-infra.txt
Text
mit
104
// -*- mode:doc; -*- // vim: set syntax=asciidoc: ==== Location of downloaded packages The various tarballs that are downloaded by Buildroot are all stored in +BR2_DL_DIR+, which by default is the +dl+ directory. If you want to keep a complete version of Buildroot which is known to be working with the associated tarballs, you can make a copy of this directory. This will allow you to regenerate the toolchain and the target filesystem with exactly the same versions. If you maintain several Buildroot trees, it might be better to have a shared download location. This can be achieved by pointing the +BR2_DL_DIR+ environment variable to a directory. If this is set, then the value of +BR2_DL_DIR+ in the Buildroot configuration is overridden. The following line should be added to +<~/.bashrc>+. ----------------- export BR2_DL_DIR=<shared download location> ----------------- The download location can also be set in the +.config+ file, with the +BR2_DL_DIR+ option. Unlike most options in the .config file, this value is overridden by the +BR2_DL_DIR+ environment variable.
shibajee/buildroot
docs/manual/download-location.txt
Text
mit
1,084
// -*- mode:doc; -*- // vim: set syntax=asciidoc: === Integration with Eclipse While a part of the embedded Linux developers like classical text editors like Vim or Emacs, and command-line based interfaces, a number of other embedded Linux developers like richer graphical interfaces to do their development work. Eclipse being one of the most popular Integrated Development Environment, Buildroot integrates with Eclipse in order to ease the development work of Eclipse users. Our integration with Eclipse simplifies the compilation, remote execution and remote debugging of applications and libraries that are built on top of a Buildroot system. It does not integrate the Buildroot configuration and build processes themselves with Eclipse. Therefore, the typical usage model of our Eclipse integration would be: * Configure your Buildroot system with +make menuconfig+, +make xconfig+ or any other configuration interface provided with Buildroot. * Build your Buildroot system by running +make+. * Start Eclipse to develop, execute and debug your own custom applications and libraries, that will rely on the libraries built and installed by Buildroot. The Buildroot Eclipse integration installation process and usage is described in detail at https://github.com/mbats/eclipse-buildroot-bundle/wiki.
shibajee/buildroot
docs/manual/eclipse-integration.txt
Text
mit
1,315
// -*- mode:doc; -*- // vim: set syntax=asciidoc: == Frequently Asked Questions & Troubleshooting [[faq-boot-hang-after-starting]] === The boot hangs after 'Starting network...' If the boot process seems to hang after the following messages (messages not necessarily exactly similar, depending on the list of packages selected): ------------------------ Freeing init memory: 3972K Initializing random number generator... done. Starting network... Starting dropbear sshd: generating rsa key... generating dsa key... OK ------------------------ then it means that your system is running, but didn't start a shell on the serial console. In order to have the system start a shell on your serial console, you have to go into the Buildroot configuration, in +System configuration+, modify +Run a getty (login prompt) after boot+ and set the appropriate port and baud rate in the +getty options+ submenu. This will automatically tune the +/etc/inittab+ file of the generated system so that a shell starts on the correct serial port. [[faq-no-compiler-on-target]] === Why is there no compiler on the target? It has been decided that support for the _native compiler on the target_ would be stopped from the Buildroot-2012.11 release because: * this feature was neither maintained nor tested, and often broken; * this feature was only available for Buildroot toolchains; * Buildroot mostly targets _small_ or _very small_ target hardware with limited resource onboard (CPU, ram, mass-storage), for which compiling on the target does not make much sense; * Buildroot aims at easing the cross-compilation, making native compilation on the target unnecessary. If you need a compiler on your target anyway, then Buildroot is not suitable for your purpose. In such case, you need a _real distribution_ and you should opt for something like: * http://www.openembedded.org[openembedded] * https://www.yoctoproject.org[yocto] * http://www.emdebian.org[emdebian] * https://fedoraproject.org/wiki/Architectures[Fedora] * http://en.opensuse.org/Portal:ARM[openSUSE ARM] * http://archlinuxarm.org[Arch Linux ARM] * ... [[faq-no-dev-files-on-target]] === Why are there no development files on the target? Since there is no compiler available on the target (see xref:faq-no-compiler-on-target[]), it does not make sense to waste space with headers or static libraries. Therefore, those files are always removed from the target since the Buildroot-2012.11 release. [[faq-no-doc-on-target]] === Why is there no documentation on the target? Because Buildroot mostly targets _small_ or _very small_ target hardware with limited resource onboard (CPU, ram, mass-storage), it does not make sense to waste space with the documentation data. If you need documentation data on your target anyway, then Buildroot is not suitable for your purpose, and you should look for a _real distribution_ (see: xref:faq-no-compiler-on-target[]). [[faq-why-not-visible-package]] === Why are some packages not visible in the Buildroot config menu? If a package exists in the Buildroot tree and does not appear in the config menu, this most likely means that some of the package's dependencies are not met. To know more about the dependencies of a package, search for the package symbol in the config menu (see xref:make-tips[]). Then, you may have to recursively enable several options (which correspond to the unmet dependencies) to finally be able to select the package. If the package is not visible due to some unmet toolchain options, then you should certainly run a full rebuild (see xref:make-tips[] for more explanations). [[faq-why-not-use-target-as-chroot]] === Why not use the target directory as a chroot directory? There are plenty of reasons to *not* use the target directory a chroot one, among these: * file ownerships, modes and permissions are not correctly set in the target directory; * device nodes are not created in the target directory. For these reasons, commands run through chroot, using the target directory as the new root, will most likely fail. If you want to run the target filesystem inside a chroot, or as an NFS root, then use the tarball image generated in +images/+ and extract it as root. [[faq-no-binary-packages]] === Why doesn't Buildroot generate binary packages (.deb, .ipkg...)? One feature that is often discussed on the Buildroot list is the general topic of "package management". To summarize, the idea would be to add some tracking of which Buildroot package installs what files, with the goals of: * being able to remove files installed by a package when this package gets unselected from the menuconfig; * being able to generate binary packages (ipk or other format) that can be installed on the target without re-generating a new root filesystem image. In general, most people think it is easy to do: just track which package installed what and remove it when the package is unselected. However, it is much more complicated than that: * It is not only about the +target/+ directory, but also the sysroot in +host/usr/<tuple>/sysroot+ and the +host/+ directory itself. All files installed in those directories by various packages must be tracked. * When a package is unselected from the configuration, it is not sufficient to remove just the files it installed. One must also remove all its reverse dependencies (i.e. packages relying on it) and rebuild all those packages. For example, package A depends optionally on the OpenSSL library. Both are selected, and Buildroot is built. Package A is built with crypto support using OpenSSL. Later on, OpenSSL gets unselected from the configuration, but package A remains (since OpenSSL is an optional dependency, this is possible.) If only OpenSSL files are removed, then the files installed by package A are broken: they use a library that is no longer present on the target. Although this is technically doable, it adds a lot of complexity to Buildroot, which goes against the simplicity we try to stick to. * In addition to the previous problem, there is the case where the optional dependency is not even known to Buildroot. For example, package A in version 1.0 never used OpenSSL, but in version 2.0 it automatically uses OpenSSL if available. If the Buildroot .mk file hasn't been updated to take this into account, then package A will not be part of the reverse dependencies of OpenSSL and will not be removed and rebuilt when OpenSSL is removed. For sure, the .mk file of package A should be fixed to mention this optional dependency, but in the mean time, you can have non-reproducible behaviors. * The request is to also allow changes in the menuconfig to be applied on the output directory without having to rebuild everything from scratch. However, this is very difficult to achieve in a reliable way: what happens when the suboptions of a package are changed (we would have to detect this, and rebuild the package from scratch and potentially all its reverse dependencies), what happens if toolchain options are changed, etc. At the moment, what Buildroot does is clear and simple so its behaviour is very reliable and it is easy to support users. If configuration changes done in menuconfig are applied after the next make, then it has to work correctly and properly in all situations, and not have some bizarre corner cases. The risk is to get bug reports like "I have enabled package A, B and C, then ran make, then disabled package C and enabled package D and ran make, then re-enabled package C and enabled package E and then there is a build failure". Or worse "I did some configuration, then built, then did some changes, built, some more changes, built, some more changes, built, and now it fails, but I don't remember all the changes I did and in which order". This will be impossible to support. For all these reasons, the conclusion is that adding tracking of installed files to remove them when the package is unselected, or to generate a repository of binary packages, is something that is very hard to achieve reliably and will add a lot of complexity. On this matter, the Buildroot developers make this position statement: * Buildroot strives to make it easy to generate a root filesystem (hence the name, by the way.) That is what we want to make Buildroot good at: building root filesystems. * Buildroot is not meant to be a distribution (or rather, a distribution generator.) It is the opinion of most Buildroot developers that this is not a goal we should pursue. We believe that there are other tools better suited to generate a distro than Buildroot is. For example, http://openembedded.org/[Open Embedded], or https://openwrt.org/[openWRT], are such tools. * We prefer to push Buildroot in a direction that makes it easy (or even easier) to generate complete root filesystems. This is what makes Buildroot stands out in the crowd (among other things, of course!) * We believe that for most embedded Linux systems, binary packages are not necessary, and potentially harmful. When binary packages are used, it means that the system can be partially upgraded, which creates an enormous number of possible combinations of package versions that should be tested before doing the upgrade on the embedded device. On the other hand, by doing complete system upgrades by upgrading the entire root filesystem image at once, the image deployed to the embedded system is guaranteed to really be the one that has been tested and validated. [[faq-speeding-up-build]] === How to speed-up the build process? Since Buildroot often involves doing full rebuilds of the entire system that can be quite long, we provide below a number of tips to help reduce the build time: * Use a pre-built external toolchain instead of the default Buildroot internal toolchain. By using a pre-built Linaro toolchain (on ARM) or a Sourcery CodeBench toolchain (for ARM, x86, x86-64, MIPS, etc.), you will save the build time of the toolchain at each complete rebuild, approximately 15 to 20 minutes. Note that temporarily using an external toolchain does not prevent you to switch back to an internal toolchain (that may provide a higher level of customization) once the rest of your system is working; * Use the +ccache+ compiler cache (see: xref:ccache[]); * Learn about rebuilding only the few packages you actually care about (see xref:rebuild-pkg[]), but beware that sometimes full rebuilds are anyway necessary (see xref:full-rebuild[]); * Make sure you are not using a virtual machine for the Linux system used to run Buildroot. Most of the virtual machine technologies are known to cause a significant performance impact on I/O, which is really important for building source code; * Make sure that you're using only local files: do not attempt to do a build over NFS, which significantly slows down the build. Having the Buildroot download folder available locally also helps a bit. * Buy new hardware. SSDs and lots of RAM are key to speeding up the builds.
shibajee/buildroot
docs/manual/faq-troubleshooting.txt
Text
mit
11,214
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[getting-buildroot]] == Getting Buildroot Buildroot releases are made every 3 months, in February, May, August and November. Release numbers are in the format YYYY.MM, so for example 2013.02, 2014.08. Release tarballs are available at http://buildroot.org/downloads/[]. For your convenience, a https://www.vagrantup.com/[Vagrantfile] is available in `support/misc/Vagrantfile` in the Buildroot source tree to quickly set up a virtual machine with the needed dependencies to get started. If you want to setup an isolated buildroot environment on Linux or Mac Os X, paste this line onto your terminal: -------------------- curl -O https://buildroot.org/downloads/Vagrantfile; vagrant up -------------------- If you are on Windows, paste this into your powershell: -------------------- (new-object System.Net.WebClient).DownloadFile( "https://buildroot.org/downloads/Vagrantfile","Vagrantfile"); vagrant up -------------------- If you want to follow development, you can use the daily snapshots or make a clone of the Git repository. Refer to the http://buildroot.org/download[Download page] of the Buildroot website for more details.
shibajee/buildroot
docs/manual/getting.txt
Text
mit
1,192
// -*- mode:doc; -*- // vim: set syntax=asciidoc: == How Buildroot works As mentioned above, Buildroot is basically a set of Makefiles that download, configure, and compile software with the correct options. It also includes patches for various software packages - mainly the ones involved in the cross-compilation toolchain (+gcc+, +binutils+ and +uClibc+). There is basically one Makefile per software package, and they are named with the +.mk+ extension. Makefiles are split into many different parts. * The +toolchain/+ directory contains the Makefiles and associated files for all software related to the cross-compilation toolchain: +binutils+, +gcc+, +gdb+, +kernel-headers+ and +uClibc+. * The +arch/+ directory contains the definitions for all the processor architectures that are supported by Buildroot. * The +package/+ directory contains the Makefiles and associated files for all user-space tools and libraries that Buildroot can compile and add to the target root filesystem. There is one sub-directory per package. * The +linux/+ directory contains the Makefiles and associated files for the Linux kernel. * The +boot/+ directory contains the Makefiles and associated files for the bootloaders supported by Buildroot. * The +system/+ directory contains support for system integration, e.g. the target filesystem skeleton and the selection of an init system. * The +fs/+ directory contains the Makefiles and associated files for software related to the generation of the target root filesystem image. Each directory contains at least 2 files: * +something.mk+ is the Makefile that downloads, configures, compiles and installs the package +something+. * +Config.in+ is a part of the configuration tool description file. It describes the options related to the package. The main Makefile performs the following steps (once the configuration is done): * Create all the output directories: +staging+, +target+, +build+, etc. in the output directory (+output/+ by default, another value can be specified using +O=+) * Generate the toolchain target. When an internal toolchain is used, this means generating the cross-compilation toolchain. When an external toolchain is used, this means checking the features of the external toolchain and importing it into the Buildroot environment. * Generate all the targets listed in the +TARGETS+ variable. This variable is filled by all the individual components' Makefiles. Generating these targets will trigger the compilation of the userspace packages (libraries, programs), the kernel, the bootloader and the generation of the root filesystem images, depending on the configuration.
shibajee/buildroot
docs/manual/how-buildroot-works.txt
Text
mit
2,703
// -*- mode:doc; -*- // vim: set syntax=asciidoc: == About Buildroot Buildroot is a tool that simplifies and automates the process of building a complete Linux system for an embedded system, using cross-compilation. In order to achieve this, Buildroot is able to generate a cross-compilation toolchain, a root filesystem, a Linux kernel image and a bootloader for your target. Buildroot can be used for any combination of these options, independently (you can for example use an existing cross-compilation toolchain, and build only your root filesystem with Buildroot). Buildroot is useful mainly for people working with embedded systems. Embedded systems often use processors that are not the regular x86 processors everyone is used to having in his PC. They can be PowerPC processors, MIPS processors, ARM processors, etc. Buildroot supports numerous processors and their variants; it also comes with default configurations for several boards available off-the-shelf. Besides this, a number of third-party projects are based on, or develop their BSP footnote:[BSP: Board Support Package] or SDK footnote:[SDK: Software Development Kit] on top of Buildroot.
shibajee/buildroot
docs/manual/introduction.txt
Text
mit
1,164
// -*- mode:doc; -*- // vim: set syntax=asciidoc: == Known issues * It is not possible to pass extra linker options via +BR2_TARGET_LDFLAGS+ if such options contain a +$+ sign. For example, the following is known to break: +BR2_TARGET_LDFLAGS="-Wl,-rpath=\'$ORIGIN/../lib'"+ * The +ltp-testsuite+ package does not build with the default uClibc configuration used by the Buildroot toolchain backend. The LTP testsuite uses several functions that are considered obsolete, such as sigset() and others. uClibc configuration options such as DO_XSI_MATH, UCLIBC_HAS_OBSOLETE_BSD_SIGNAL and UCLIBC_SV4_DEPRECATED are needed if one wants to build the +ltp-testsuite+ package with uClibc. You need to either use a glibc based toolchain, or enable the appropriate options in the uClibc configuration. * The +xfsprogs+ package does not build with the default uClibc configuration used by the Buildroot toolchain backend. You need to either use a glibc based toolchain, or enable the appropriate options in the uClibc configuration. * The +mrouted+ package does not build with the default uClibc configuration used by the Buildroot toolchain backend. You need to either use a glibc based toolchain, or enable the appropriate options in the uClibc configuration. * The +libffi+ package is not supported on the SuperH 2 and ARC architectures. * The +prboom+ package triggers a compiler failure with the SuperH 4 compiler from Sourcery CodeBench, version 2012.09.
shibajee/buildroot
docs/manual/known-issues.txt
Text
mit
1,493
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[legal-info]] == Legal notice and licensing === Complying with open source licenses All of the end products of Buildroot (toolchain, root filesystem, kernel, bootloaders) contain open source software, released under various licenses. Using open source software gives you the freedom to build rich embedded systems, choosing from a wide range of packages, but also imposes some obligations that you must know and honour. Some licenses require you to publish the license text in the documentation of your product. Others require you to redistribute the source code of the software to those that receive your product. The exact requirements of each license are documented in each package, and it is your responsibility (or that of your legal office) to comply with those requirements. To make this easier for you, Buildroot can collect for you some material you will probably need. To produce this material, after you have configured Buildroot with +make menuconfig+, +make xconfig+ or +make gconfig+, run: -------------------- make legal-info -------------------- Buildroot will collect legally-relevant material in your output directory, under the +legal-info/+ subdirectory. There you will find: * A +README+ file, that summarizes the produced material and contains warnings about material that Buildroot could not produce. * +buildroot.config+: this is the Buildroot configuration file that is usually produced with +make menuconfig+, and which is necessary to reproduce the build. * The source code for all packages; this is saved in the +sources/+ and +host-sources/+ subdirectories for target and host packages respectively. The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be saved. Patches that were applied are also saved, along with a file named +series+ that lists the patches in the order they were applied. Patches are under the same license as the files that they modify. Note: Buildroot applies additional patches to Libtool scripts of autotools-based packages. These patches can be found under +support/libtool+ in the Buildroot source and, due to technical limitations, are not saved with the package sources. You may need to collect them manually. * A manifest file (one for host and one for target packages) listing the configured packages, their version, license and related information. Some of this information might not be defined in Buildroot; such items are marked as "unknown". * The license texts of all packages, in the +licenses/+ and +host-licenses/+ subdirectories for target and host packages respectively. If the license file(s) are not defined in Buildroot, the file is not produced and a warning in the +README+ indicates this. Please note that the aim of the +legal-info+ feature of Buildroot is to produce all the material that is somehow relevant for legal compliance with the package licenses. Buildroot does not try to produce the exact material that you must somehow make public. Certainly, more material is produced than is needed for a strict legal compliance. For example, it produces the source code for packages released under BSD-like licenses, that you are not required to redistribute in source form. Moreover, due to technical limitations, Buildroot does not produce some material that you will or may need, such as the toolchain source code and the Buildroot source code itself (including patches to packages for which source distribution is required). When you run +make legal-info+, Buildroot produces warnings in the +README+ file to inform you of relevant material that could not be saved. [[legal-info-list-licenses]] === License abbreviations Here is a list of the licenses that are most widely used by packages in Buildroot, with the name used in the manifest files: * `AGPLv3`: http://www.gnu.org/licenses/agpl-3.0.en.html[ GNU Affero General Public License, version 3]; * `GPLv2`: http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[ GNU General Public License, version 2]; * `GPLv2+`: http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[ GNU General Public License, version 2] or (at your option) any later version; * `GPLv3`: http://www.gnu.org/licenses/gpl.html[ GNU General Public License, version 3]; * `GPLv3+`: http://www.gnu.org/licenses/gpl.html[ GNU General Public License, version 3] or (at your option) any later version; * `GPL`: http://www.gnu.org/licenses/gpl.html[ GNU General Public License] (any version); * `LGPLv2`: http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[ GNU Library General Public License, version 2]; * `LGPLv2+`: http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[ GNU Library General Public License, version 2] or (at your option) any later version; * `LGPLv2.1`: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[ GNU Lesser General Public License, version 2.1]; * `LGPLv2.1+`: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[ GNU Lesser General Public License, version 2.1] or (at your option) any later version; * `LGPLv3`: http://www.gnu.org/licenses/lgpl.html[ GNU Lesser General Public License, version 3]; * `LGPLv3+`: http://www.gnu.org/licenses/lgpl.html[ GNU Lesser General Public License, version 3] or (at your option) any later version; * `LGPL`: http://www.gnu.org/licenses/lgpl.html[ GNU Lesser General Public License] (any version); * `BSD-4c`: http://directory.fsf.org/wiki/License:BSD_4Clause[ Original BSD 4-clause license]; * `BSD-3c`: http://opensource.org/licenses/BSD-3-Clause[ BSD 3-clause license]; * `BSD-2c`: http://opensource.org/licenses/BSD-2-Clause[ BSD 2-clause license]; * `MIT`: http://opensource.org/licenses/mit-license.html[ MIT-style license]; * `Apache-2.0`: http://apache.org/licenses/LICENSE-2.0.html[ Apache License, version 2.0]; [[legal-info-buildroot]] === Complying with the Buildroot license Buildroot itself is an open source software, released under the http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General Public License, version 2] or (at your option) any later version, with the exception of the package patches detailed below. However, being a build system, it is not normally part of the end product: if you develop the root filesystem, kernel, bootloader or toolchain for a device, the code of Buildroot is only present on the development machine, not in the device storage. Nevertheless, the general view of the Buildroot developers is that you should release the Buildroot source code along with the source code of other packages when releasing a product that contains GPL-licensed software. This is because the http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU GPL] defines the "'complete source code'" for an executable work as "'all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable'". Buildroot is part of the 'scripts used to control compilation and installation of the executable', and as such it is considered part of the material that must be redistributed. Keep in mind that this is only the Buildroot developers' opinion, and you should consult your legal department or lawyer in case of any doubt. ==== Patches to packages Buildroot also bundles patch files, which are applied to the sources of the various packages. Those patches are not covered by the license of Buildroot. Instead, they are covered by the license of the software to which the patches are applied. When said software is available under multiple licenses, the Buildroot patches are only provided under the publicly accessible licenses. See xref:patch-policy[] for the technical details.
shibajee/buildroot
docs/manual/legal-notice.txt
Text
mit
7,804
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[make-tips]] === 'make' tips This is a collection of tips that help you make the most of Buildroot. .Display all commands executed by make: -------------------- $ make V=1 <target> -------------------- .Display the list of boards with a defconfig: -------------------- $ make list-defconfigs -------------------- .Display all available targets: -------------------- $ make help -------------------- Not all targets are always available, some settings in the +.config+ file may hide some targets: * +busybox-menuconfig+ only works when +busybox+ is enabled; * +linux-menuconfig+ and +linux-savedefconfig+ only work when +linux+ is enabled; * +uclibc-menuconfig+ is only available when the uClibc C library is selected in the internal toolchain backend; * +barebox-menuconfig+ and +barebox-savedefconfig+ only work when the +barebox+ bootloader is enabled. * +uboot-menuconfig+ and +uboot-savedefconfig+ only work when the +U-Boot+ bootloader is enabled. .Cleaning: Explicit cleaning is required when any of the architecture or toolchain configuration options are changed. To delete all build products (including build directories, host, staging and target trees, the images and the toolchain): -------------------- $ make clean -------------------- .Generating the manual: The present manual sources are located in the 'docs/manual' directory. To generate the manual: --------------------------------- $ make manual-clean $ make manual --------------------------------- The manual outputs will be generated in 'output/docs/manual'. .Notes - A few tools are required to build the documentation (see: xref:requirement-optional[]). .Resetting Buildroot for a new target: To delete all build products as well as the configuration: -------------------- $ make distclean -------------------- .Notes If +ccache+ is enabled, running +make clean+ or +distclean+ does not empty the compiler cache used by Buildroot. To delete it, refer to xref:ccache[].
shibajee/buildroot
docs/manual/make-tips.txt
Text
mit
2,034
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[makedev-syntax]] == Makedev syntax documentation The makedev syntax is used in several places in Buildroot to define changes to be made for permissions, or which device files to create and how to create them, in order to avoid calls to mknod. This syntax is derived from the makedev utility, and more complete documentation can be found in the +package/makedevs/README+ file. It takes the form of a space separated list of fields, one file per line; the fields are: |=========================================================== |name |type |mode |uid |gid |major |minor |start |inc |count |=========================================================== There are a few non-trivial blocks: - +name+ is the path to the file you want to create/modify - +type+ is the type of the file, being one of: * f: a regular file * d: a directory * r: a directory recursively * c: a character device file * b: a block device file * p: a named pipe - +mode+ are the usual permissions settings (only numerical values are allowed) - +uid+ and +gid+ are the UID and GID to set on this file; can be either numerical values or actual names - +major+ and +minor+ are here for device files, set to +-+ for other files - +start+, +inc+ and +count+ are for when you want to create a batch of files, and can be reduced to a loop, beginning at +start+, incrementing its counter by +inc+ until it reaches +count+ Let's say you want to change the permissions of a given file; using this syntax, you will need to write: ---- /usr/bin/foo f 755 0 0 - - - - - /usr/bin/bar f 755 root root - - - - - /data/buz f 644 buz-user buz-group - - - - - ---- Alternatively, if you want to change owner/permission of a directory recursively, you can write (to set UID to foo, GID to bar and access rights to rwxr-x--- for the directory /usr/share/myapp and all files and directories below it): ---- /usr/share/myapp r 750 foo bar - - - - - ---- On the other hand, if you want to create the device file +/dev/hda+ and the corresponding 15 files for the partitions, you will need for +/dev/hda+: ---- /dev/hda b 640 root root 3 0 0 0 - ---- and then for device files corresponding to the partitions of +/dev/hda+, +/dev/hdaX+, +X+ ranging from 1 to 15: ---- /dev/hda b 640 root root 3 1 1 1 15 ---- Extended attributes are supported if +BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES+ is enabled. This is done by adding a line starting with +|xattr+ after the line describing the file. Right now, only capability is supported as extended attribute. |===================== | \|xattr | capability |===================== - +|xattr+ is a "flag" that indicate an extended attribute - +capability+ is a capability to add to the previous file If you want to add the capability cap_sys_admin to the binary foo, you will write : ---- /usr/bin/foo f 755 root root - - - - - |xattr cap_sys_admin+eip ---- You can add several capabilities to a file by using several +|xattr+ lines. If you want to add the capability cap_sys_admin and cap_net_admin to the binary foo, you will write : ---- /usr/bin/foo f 755 root root - - - - - |xattr cap_sys_admin+eip |xattr cap_net_admin+eip ----
shibajee/buildroot
docs/manual/makedev-syntax.txt
Text
mit
3,225
// -*- mode:doc -*- ; // vim: set syntax=asciidoc: [[makeuser-syntax]] == Makeusers syntax documentation The syntax to create users is inspired by the makedev syntax, above, but is specific to Buildroot. The syntax for adding a user is a space-separated list of fields, one user per line; the fields are: |================================================================= |username |uid |group |gid |password |home |shell |groups |comment |================================================================= Where: - +username+ is the desired user name (aka login name) for the user. It can not be +root+, and must be unique. If set to +-+, then just a group will be created. - +uid+ is the desired UID for the user. It must be unique, and not +0+. If set to +-1+, then a unique UID will be computed by Buildroot in the range [1000...1999] - +group+ is the desired name for the user's main group. It can not be +root+. If the group does not exist, it will be created. - +gid+ is the desired GID for the user's main group. It must be unique, and not +0+. If set to +-1+, and the group does not already exist, then a unique GID will be computed by Buildroot in the range [1000..1999] - +password+ is the crypt(3)-encoded password. If prefixed with +!+, then login is disabled. If prefixed with +=+, then it is interpreted as clear-text, and will be crypt-encoded (using MD5). If prefixed with +!=+, then the password will be crypt-encoded (using MD5) and login will be disabled. If set to +*+, then login is not allowed. If set to +-+, then no password value will be set. - +home+ is the desired home directory for the user. If set to '-', no home directory will be created, and the user's home will be +/+. Explicitly setting +home+ to +/+ is not allowed. - +shell+ is the desired shell for the user. If set to +-+, then +/bin/false+ is set as the user's shell. - +groups+ is the comma-separated list of additional groups the user should be part of. If set to +-+, then the user will be a member of no additional group. Missing groups will be created with an arbitrary +gid+. - +comment+ (aka https://en.wikipedia.org/wiki/Gecos_field[GECOS] field) is an almost-free-form text. There are a few restrictions on the content of each field: * except for +comment+, all fields are mandatory. * except for +comment+, fields may not contain spaces. * no field may contain a colon (+:+). If +home+ is not +-+, then the home directory, and all files below, will belong to the user and its main group. Examples: ---- foo -1 bar -1 !=blabla /home/foo /bin/sh alpha,bravo Foo user ---- This will create this user: - +username+ (aka login name) is: +foo+ - +uid+ is computed by Buildroot - main +group+ is: +bar+ - main group +gid+ is computed by Buildroot - clear-text +password+ is: +blabla+, will be crypt(3)-encoded, and login is disabled. - +home+ is: +/home/foo+ - +shell+ is: +/bin/sh+ - +foo+ is also a member of +groups+: +alpha+ and +bravo+ - +comment+ is: +Foo user+ ---- test 8000 wheel -1 = - /bin/sh - Test user ---- This will create this user: - +username+ (aka login name) is: +test+ - +uid+ is : +8000+ - main +group+ is: +wheel+ - main group +gid+ is computed by Buildroot, and will use the value defined in the rootfs skeleton - +password+ is empty (aka no password). - +home+ is +/+ but will not belong to +test+ - +shell+ is: +/bin/sh+ - +test+ is not a member of any additional +groups+ - +comment+ is: +Test user+
shibajee/buildroot
docs/manual/makeusers-syntax.txt
Text
mit
3,476
################################################################################ # # The Buildroot manual # ################################################################################ MANUAL_SOURCES = $(sort $(wildcard docs/manual/*.txt) $(wildcard docs/images/*)) MANUAL_RESOURCES = $(TOPDIR)/docs/images # Our manual needs to generate lists define MANUAL_GEN_LISTS $(Q)$(call MESSAGE,"Updating the manual lists...") $(Q)$(COMMON_CONFIG_ENV) \ BR2_DEFCONFIG="" \ TOPDIR=$(TOPDIR) \ O=$(@D) \ python -B $(TOPDIR)/support/scripts/gen-manual-lists.py endef MANUAL_POST_RSYNC_HOOKS += MANUAL_GEN_LISTS # Our list-generating script requires argparse define MANUAL_CHECK_LISTS_DEPS $(Q)if ! python -c "import argparse" >/dev/null 2>&1 ; then \ echo "You need python with argparse on your host to generate" \ "the list of packages in the manual"; \ exit 1; \ fi endef MANUAL_CHECK_DEPENDENCIES_HOOKS += MANUAL_CHECK_LISTS_DEPS $(eval $(call asciidoc-document))
shibajee/buildroot
docs/manual/manual.mk
mk
mit
983
// -*- mode:doc; -*- // vim: set syntax=asciidoc: = The Buildroot user manual :toc: Buildroot {sys:echo $\{BR2_VERSION%%-git*\}} manual generated on {localdate} {localtime} from git revision {sys:git rev-parse --short HEAD} The Buildroot manual is written by the Buildroot developers. It is licensed under the GNU General Public License, version 2. Refer to the http://git.buildroot.org/buildroot/tree/COPYING[COPYING] file in the Buildroot sources for the full text of this license. Copyright (C) 2004-2014 The Buildroot developers image::logo.png[] = Getting started include::introduction.txt[] include::prerequisite.txt[] include::getting.txt[] include::quickstart.txt[] include::resources.txt[] = User guide include::configure.txt[] include::configure-other-components.txt[] include::common-usage.txt[] include::customize.txt[] include::faq-troubleshooting.txt[] include::known-issues.txt[] include::legal-notice.txt[] include::beyond-buildroot.txt[] = Developer guide include::how-buildroot-works.txt[] include::writing-rules.txt[] include::adding-board-support.txt[] include::adding-packages.txt[] include::patch-policy.txt[] include::download-infra.txt[] include::debugging-buildroot.txt[] include::contribute.txt[] = Appendix include::appendix.txt[]
shibajee/buildroot
docs/manual/manual.txt
Text
mit
1,289
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[pkg-build-steps]] ==== Package-specific _make_ targets Running +make <package>+ builds and installs that particular package and its dependencies. For packages relying on the Buildroot infrastructure, there are numerous special make targets that can be called independently like this: ------------ make <package>-<target> ------------ The package build targets are (in the order they are executed): [width="90%",cols="^1,4",options="header"] |=================================================== | command/target | Description | +source+ | Fetch the source (download the tarball, clone the source repository, etc) | +depends+ | Build and install all dependencies required to build the package | +extract+ | Put the source in the package build directory (extract the tarball, copy the source, etc) | +patch+ | Apply the patches, if any | +configure+ | Run the configure commands, if any | +build+ | Run the compilation commands | +install-staging+ | *target package:* Run the installation of the package in the staging directory, if necessary | +install-target+ | *target package:* Run the installation of the package in the target directory, if necessary | +install+ | *target package:* Run the 2 previous installation commands *host package:* Run the installation of the package in the host directory |=================================================== Additionally, there are some other useful make targets: [width="90%",cols="^1,4",options="header"] |=================================================== | command/target | Description | +show-depends+ | Displays the dependencies required to build the package | +graph-depends+ | Generate a dependency graph of the package, in the context of the current Buildroot configuration. See xref:graph-depends[this section] for more details about dependency graphs. | +dirclean+ | Remove the whole package build directory | +reinstall+ | Re-run the install commands | +rebuild+ | Re-run the compilation commands - this only makes sense when using the +OVERRIDE_SRCDIR+ feature or when you modified a file directly in the build directory | +reconfigure+ | Re-run the configure commands, then rebuild - this only makes sense when using the +OVERRIDE_SRCDIR+ feature or when you modified a file directly in the build directory |===================================================
shibajee/buildroot
docs/manual/package-make-target.txt
Text
mit
2,495
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[patch-policy]] == Patching a package While integrating a new package or updating an existing one, it may be necessary to patch the source of the software to get it cross-built within Buildroot. Buildroot offers an infrastructure to automatically handle this during the builds. It supports three ways of applying patch sets: downloaded patches, patches supplied within buildroot and patches located in a user-defined global patch directory. === Providing patches ==== Downloaded If it is necessary to apply a patch that is available for download, then add it to the +<packagename>_PATCH+ variable. It is downloaded from the same site as the package itself. It can be a single patch, or a tarball containing a patch series. This method is typically used for packages from Debian. ==== Within Buildroot Most patches are provided within Buildroot, in the package directory; these typically aim to fix cross-compilation, libc support, or other such issues. These patch files should be named +<number>-<description>.patch+. .Notes - The patch files coming with Buildroot should not contain any package version reference in their filename. - The field +<number>+ in the patch file name refers to the 'apply order', and shall start at 1; It is preferred to pad the number with zeros up to 4 digits, like 'git-format-patch' does. E.g.: +0001-foobar-the-buz.patch+ - Previously, it was mandatory for patches to be prefixed with the name of the package, like +<package>-<number>-<description>.patch+, but that is no longer the case. Existing packages will be fixed as time passes. 'Do not prefix patches with the package name.' - Previously, a +series+ file, as used by +quilt+, could also be added in the package directory. In that case, the +series+ file defines the patch application order. This is deprecated, and will be removed in the future. 'Do not use a series file.' ==== Global patch directory The +BR2_GLOBAL_PATCH_DIR+ configuration file option can be used to specify a space separated list of one or more directories containing global package patches. See xref:customize-patches[] for details. [[patch-apply-order]] === How patches are applied . Run the +<packagename>_PRE_PATCH_HOOKS+ commands if defined; . Cleanup the build directory, removing any existing +*.rej+ files; . If +<packagename>_PATCH+ is defined, then patches from these tarballs are applied; . If there are some +*.patch+ files in the package's Buildroot directory or in a package subdirectory named +<packageversion>+, then: + * If a +series+ file exists in the package directory, then patches are applied according to the +series+ file; + * Otherwise, patch files matching +*.patch+ are applied in alphabetical order. So, to ensure they are applied in the right order, it is highly recommended to name the patch files like this: +<number>-<description>.patch+, where +<number>+ refers to the 'apply order'. . If +BR2_GLOBAL_PATCH_DIR+ is defined, the directories will be enumerated in the order they are specified. The patches are applied as described in the previous step. . Run the +<packagename>_POST_PATCH_HOOKS+ commands if defined. If something goes wrong in the steps _3_ or _4_, then the build fails. === Format and licensing of the package patches Patches are released under the same license as the software they apply to (see xref:legal-info-buildroot[]). A message explaining what the patch does, and why it is needed, should be added in the header commentary of the patch. You should add a +Signed-off-by+ statement in the header of the each patch to help with keeping track of the changes and to certify that the patch is released under the same license as the software that is modified. If the software is under version control, it is recommended to use the upstream SCM software to generate the patch set. Otherwise, concatenate the header with the output of the +diff -purN package-version.orig/ package-version/+ command. If you update an existing patch (e.g. when bumping the package version), make sure the existing From header and Signed-off-by tags are not removed, but do update the rest of the patch comment when appropriate. At the end, the patch should look like: --------------- configure.ac: add C++ support test Signed-off-by: John Doe <john.doe@noname.org> --- configure.ac.orig +++ configure.ac @@ -40,2 +40,12 @@ AC_PROG_MAKE_SET + +AC_CACHE_CHECK([whether the C++ compiler works], + [rw_cv_prog_cxx_works], + [AC_LANG_PUSH([C++]) + AC_LINK_IFELSE([AC_LANG_PROGRAM([], [])], + [rw_cv_prog_cxx_works=yes], + [rw_cv_prog_cxx_works=no]) + AC_LANG_POP([C++])]) + +AM_CONDITIONAL([CXX_WORKS], [test "x$rw_cv_prog_cxx_works" = "xyes"]) --------------- === Integrating patches found on the Web When integrating a patch of which you are not the author, you have to add a few things in the header of the patch itself. Depending on whether the patch has been obtained from the project repository itself, or from somewhere on the web, add one of the following tags: --------------- Backported from: <some commit id> --------------- or --------------- Fetch from: <some url> --------------- It is also sensible to add a few words about any changes to the patch that may have been necessary.
shibajee/buildroot
docs/manual/patch-policy.txt
Text
mit
5,435
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[requirement]] == System requirements Buildroot is designed to run on Linux systems. While Buildroot itself will build most host packages it needs for the compilation, certain standard Linux utilities are expected to be already installed on the host system. Below you will find an overview of the mandatory and optional packages (note that package names may vary between distributions). [[requirement-mandatory]] === Mandatory packages * Build tools: ** +which+ ** +sed+ ** +make+ (version 3.81 or any later) ** +binutils+ ** +build-essential+ (only for Debian based systems) ** +gcc+ (version 2.95 or any later) ** `g++` (version 2.95 or any later) ** +bash+ ** +patch+ ** +gzip+ ** +bzip2+ ** +perl+ (version 5.8.7 or any later) ** +tar+ ** +cpio+ ** +python+ (version 2.6 or any later) ** +unzip+ ** +rsync+ * Source fetching tools: ** +wget+ [[requirement-optional]] === Optional packages * Configuration interface dependencies: + For these libraries, you need to install both runtime and development data, which in many distributions are packaged separately. The development packages typically have a _-dev_ or _-devel_ suffix. + ** +ncurses5+ to use the 'menuconfig' interface ** +qt4+ to use the 'xconfig' interface ** +glib2+, +gtk2+ and +glade2+ to use the 'gconfig' interface * Source fetching tools: + In the official tree, most of the package sources are retrieved using +wget+ from _ftp_, _http_ or _https_ locations. A few packages are only available through a version control system. Moreover, Buildroot is capable of downloading sources via other tools, like +rsync+ or +scp+ (refer to xref:download-infra[] for more details). If you enable packages using any of these methods, you will need to install the corresponding tool on the host system: + ** +bazaar+ ** +cvs+ ** +git+ ** +mercurial+ ** +rsync+ ** +scp+ ** +subversion+ * Java-related packages, if the Java Classpath needs to be built for the target system: ** The +javac+ compiler ** The +jar+ tool * Documentation generation tools: ** +asciidoc+, version 8.6.3 or higher ** +w3m+ ** +python+ with the +argparse+ module (automatically present in 2.7+ and 3.2+) ** +dblatex+ (required for the pdf manual only) * Graph generation tools: ** +graphviz+ to use 'graph-depends' and '<pkg>-graph-depends' ** +python-matplotlib+ to use 'graph-build'
shibajee/buildroot
docs/manual/prerequisite.txt
Text
mit
2,386
// -*- mode:doc; -*- // vim: set syntax=asciidoc: == Buildroot quick start *Important*: you can and should *build everything as a normal user*. There is no need to be root to configure and use Buildroot. By running all commands as a regular user, you protect your system against packages behaving badly during compilation and installation. The first step when using Buildroot is to create a configuration. Buildroot has a nice configuration tool similar to the one you can find in the http://www.kernel.org/[Linux kernel] or in http://www.busybox.net/[BusyBox]. From the buildroot directory, run -------------------- $ make menuconfig -------------------- for the original curses-based configurator, or -------------------- $ make nconfig -------------------- for the new curses-based configurator, or -------------------- $ make xconfig -------------------- for the Qt-based configurator, or -------------------- $ make gconfig -------------------- for the GTK-based configurator. All of these "make" commands will need to build a configuration utility (including the interface), so you may need to install "development" packages for relevant libraries used by the configuration utilities. Refer to xref:requirement[] for more details, specifically the xref:requirement-optional[optional requirements] to get the dependencies of your favorite interface. For each menu entry in the configuration tool, you can find associated help that describes the purpose of the entry. Refer to xref:configure[] for details on some specific configuration aspects. Once everything is configured, the configuration tool generates a +.config+ file that contains the entire configuration. This file will be read by the top-level Makefile. To start the build process, simply run: -------------------- $ make -------------------- You *should never* use +make -jN+ with Buildroot: top-level parallel make is currently not supported. Instead, use the +BR2_JLEVEL+ option to tell Buildroot to run the compilation of each individual package with +make -jN+. The `make` command will generally perform the following steps: * download source files (as required); * configure, build and install the cross-compilation toolchain, or simply import an external toolchain; * configure, build and install selected target packages; * build a kernel image, if selected; * build a bootloader image, if selected; * create a root filesystem in selected formats. Buildroot output is stored in a single directory, +output/+. This directory contains several subdirectories: * +images/+ where all the images (kernel image, bootloader and root filesystem images) are stored. These are the files you need to put on your target system. * +build/+ where all the components are built (this includes tools needed by Buildroot on the host and packages compiled for the target). This directory contains one subdirectory for each of these components. * +staging/+ which contains a hierarchy similar to a root filesystem hierarchy. This directory contains the headers and libraries of the cross-compilation toolchain and all the userspace packages selected for the target. However, this directory is 'not' intended to be the root filesystem for the target: it contains a lot of development files, unstripped binaries and libraries that make it far too big for an embedded system. These development files are used to compile libraries and applications for the target that depend on other libraries. * +target/+ which contains 'almost' the complete root filesystem for the target: everything needed is present except the device files in +/dev/+ (Buildroot can't create them because Buildroot doesn't run as root and doesn't want to run as root). Also, it doesn't have the correct permissions (e.g. setuid for the busybox binary). Therefore, this directory *should not be used on your target*. Instead, you should use one of the images built in the +images/+ directory. If you need an extracted image of the root filesystem for booting over NFS, then use the tarball image generated in +images/+ and extract it as root. Compared to +staging/+, +target/+ contains only the files and libraries needed to run the selected target applications: the development files (headers, etc.) are not present, the binaries are stripped. * +host/+ contains the installation of tools compiled for the host that are needed for the proper execution of Buildroot, including the cross-compilation toolchain. These commands, +make menuconfig|nconfig|gconfig|xconfig+ and +make+, are the basic ones that allow to easily and quickly generate images fitting your needs, with all the features and applications you enabled. More details about the "make" command usage are given in xref:make-tips[].
shibajee/buildroot
docs/manual/quickstart.txt
Text
mit
4,805
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[full-rebuild]] === Understanding when a full rebuild is necessary Buildroot does not attempt to detect what parts of the system should be rebuilt when the system configuration is changed through +make menuconfig+, +make xconfig+ or one of the other configuration tools. In some cases, Buildroot should rebuild the entire system, in some cases, only a specific subset of packages. But detecting this in a completely reliable manner is very difficult, and therefore the Buildroot developers have decided to simply not attempt to do this. Instead, it is the responsibility of the user to know when a full rebuild is necessary. As a hint, here are a few rules of thumb that can help you understand how to work with Buildroot: * When the target architecture configuration is changed, a complete rebuild is needed. Changing the architecture variant, the binary format or the floating point strategy for example has an impact on the entire system. * When the toolchain configuration is changed, a complete rebuild generally is needed. Changing the toolchain configuration often involves changing the compiler version, the type of C library or its configuration, or some other fundamental configuration item, and these changes have an impact on the entire system. * When an additional package is added to the configuration, a full rebuild is not necessarily needed. Buildroot will detect that this package has never been built, and will build it. However, if this package is a library that can optionally be used by packages that have already been built, Buildroot will not automatically rebuild those. Either you know which packages should be rebuilt, and you can rebuild them manually, or you should do a full rebuild. For example, let's suppose you have built a system with the +ctorrent+ package, but without +openssl+. Your system works, but you realize you would like to have SSL support in +ctorrent+, so you enable the +openssl+ package in Buildroot configuration and restart the build. Buildroot will detect that +openssl+ should be built and will be build it, but it will not detect that +ctorrent+ should be rebuilt to benefit from +openssl+ to add OpenSSL support. You will either have to do a full rebuild, or rebuild +ctorrent+ itself. * When a package is removed from the configuration, Buildroot does not do anything special. It does not remove the files installed by this package from the target root filesystem or from the toolchain _sysroot_. A full rebuild is needed to get rid of this package. However, generally you don't necessarily need this package to be removed right now: you can wait for the next lunch break to restart the build from scratch. * When the sub-options of a package are changed, the package is not automatically rebuilt. After making such changes, rebuilding only this package is often sufficient, unless enabling the package sub-option adds some features to the package that are useful for another package which has already been built. Again, Buildroot does not track when a package should be rebuilt: once a package has been built, it is never rebuilt unless explicitly told to do so. * When a change to the root filesystem skeleton is made, a full rebuild is needed. However, when changes to the root filesystem overlay, a post-build script or a post-image script are made, there is no need for a full rebuild: a simple +make+ invocation will take the changes into account. Generally speaking, when you're facing a build error and you're unsure of the potential consequences of the configuration changes you've made, do a full rebuild. If you get the same build error, then you are sure that the error is not related to partial rebuilds of packages, and if this error occurs with packages from the official Buildroot, do not hesitate to report the problem! As your experience with Buildroot progresses, you will progressively learn when a full rebuild is really necessary, and you will save more and more time. For reference, a full rebuild is achieved by running: --------------- $ make clean all --------------- [[rebuild-pkg]] === Understanding how to rebuild packages One of the most common questions asked by Buildroot users is how to rebuild a given package or how to remove a package without rebuilding everything from scratch. Removing a package is unsupported by Buildroot without rebuilding from scratch. This is because Buildroot doesn't keep track of which package installs what files in the +output/staging+ and +output/target+ directories, or which package would be compiled differently depending on the availability of another package. The easiest way to rebuild a single package from scratch is to remove its build directory in +output/build+. Buildroot will then re-extract, re-configure, re-compile and re-install this package from scratch. You can ask buildroot to do this with the +make <package>-dirclean+ command. On the other hand, if you only want to restart the build process of a package from its compilation step, you can run +make <package>-rebuild+, followed by +make+ or +make <package>+. It will restart the compilation and installation of the package, but not from scratch: it basically re-executes +make+ and +make install+ inside the package, so it will only rebuild files that changed. If you want to restart the build process of a package from its configuration step, you can run +make <package>-reconfigure+, followed by +make+ or +make <package>+. It will restart the configuration, compilation and installation of the package. Internally, Buildroot creates so-called _stamp files_ to keep track of which build steps have been completed for each package. They are stored in the package build directory, +output/build/<package>-<version>/+ and are named +.stamp_<step-name>+. The commands detailed above simply manipulate these stamp files to force Buildroot to restart a specific set of steps of a package build process. Further details about package special make targets are explained in xref:pkg-build-steps[].
shibajee/buildroot
docs/manual/rebuilding-packages.txt
Text
mit
6,177
// -*- mode:doc; -*- // vim: set syntax=asciidoc: [[community-resources]] == Community resources Like any open source project, Buildroot has different ways to share information in its community and outside. Each of those ways may interest you if you are looking for some help, want to understand Buildroot or contribute to the project. Mailing List:: + Buildroot has a mailing list for discussion and development. It is the main method of interaction for Buildroot users and developers. + Only subscribers to the Buildroot mailing list are allowed to post to this list. You can subscribe via the http://lists.buildroot.org/mailman/listinfo/buildroot[mailing list info page]. + Mails that are sent to the mailing list are also available in the http://lists.buildroot.org/pipermail/buildroot[mailing list archives] and via http://gmane.org[Gmane], at http://dir.gmane.org/gmane.comp.lib.uclibc.buildroot[+gmane.comp.lib.uclibc.buildroot+]. Please search the mailing list archives before asking questions, since there is a good chance someone else has asked the same question before. IRC:: + The Buildroot IRC channel irc://freenode.net/#buildroot[#buildroot] is hosted on http://webchat.freenode.net[Freenode]. It is a useful place to ask quick questions or discuss on certain topics. + When asking for help on IRC, share relevant logs or pieces of code using a code sharing website, such as http://code.bulix.org. + Note that for certain questions, posting to the mailing list may be better as it will reach more people, both developers and users. Bug tracker:: + Bugs in Buildroot can be reported via the mailing list or alternatively via the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot bugtracker]. Please refer to xref:reporting-bugs[] before creating a bug report. Wiki:: + http://elinux.org/Buildroot[The Buildroot wiki page] is hosted on the http://elinux.org[eLinux] wiki. It contains some useful links, an overview of past and upcoming events, and a TODO list. Patchwork:: + Patchwork is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project. Patches that have been sent to a mailing list are \'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too. For more information on Patchwork see http://jk.ozlabs.org/projects/patchwork/[]. + Buildroot's Patchwork website is mainly for use by Buildroot's maintainer to ensure patches aren't missed. It is also used by Buildroot patch reviewers (see also xref:apply-patches-patchwork[]). However, since the website exposes patches and their corresponding review comments in a clean and concise web interface, it can be useful for all Buildroot developers. + The Buildroot patch management interface is available at http://patchwork.buildroot.org[].
shibajee/buildroot
docs/manual/resources.txt
Text
mit
2,881
// -*- mode:doc; -*- // vim: set syntax=asciidoc: ==== Using +gdb+ in Buildroot Buildroot allows to do cross-debugging, where the debugger runs on the build machine and communicates with +gdbserver+ on the target to control the execution of the program. To achieve this: * If you are using an _internal toolchain_ (built by Buildroot), you must enable +BR2_PACKAGE_HOST_GDB+, +BR2_PACKAGE_GDB+ and +BR2_PACKAGE_GDB_SERVER+. This ensures that both the cross gdb and gdbserver get built, and that gdbserver gets installed to your target. * If you are using an _external toolchain_, you should enable +BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY+, which will copy the gdbserver included with the external toolchain to the target. If your external toolchain does not have a cross gdb or gdbserver, it is also possible to let Buildroot build them, by enabling the same options as for the _internal toolchain backend_. Now, to start debugging a program called +foo+, you should run on the target: ---------------------------- gdbserver :2345 foo ---------------------------- This will cause +gdbserver+ to listen on TCP port 2345 for a connection from the cross gdb. Then, on the host, you should start the cross gdb using the following command line: ---------------------------- <buildroot>/output/host/usr/bin/<tuple>-gdb -x <buildroot>/output/staging/usr/share/buildroot/gdbinit foo ---------------------------- Of course, +foo+ must be available in the current directory, built with debugging symbols. Typically you start this command from the directory where +foo+ is built (and not from +output/target/+ as the binaries in that directory are stripped). The +<buildroot>/output/staging/usr/share/buildroot/gdbinit+ file will tell the cross gdb where to find the libraries of the target. Finally, to connect to the target from the cross gdb: ---------------------------- (gdb) target remote <target ip address>:2345 ----------------------------
shibajee/buildroot
docs/manual/using-buildroot-debugger.txt
Text
mit
1,968
// -*- mode:doc; -*- // vim: set syntax=asciidoc: ==== Using Buildroot during development The normal operation of Buildroot is to download a tarball, extract it, configure, compile and install the software component found inside this tarball. The source code is extracted in +output/build/<package>-<version>+, which is a temporary directory: whenever +make clean+ is used, this directory is entirely removed, and re-created at the next +make+ invocation. Even when a Git or Subversion repository is used as the input for the package source code, Buildroot creates a tarball out of it, and then behaves as it normally does with tarballs. This behavior is well-suited when Buildroot is used mainly as an integration tool, to build and integrate all the components of an embedded Linux system. However, if one uses Buildroot during the development of certain components of the system, this behavior is not very convenient: one would instead like to make a small change to the source code of one package, and be able to quickly rebuild the system with Buildroot. Making changes directly in +output/build/<package>-<version>+ is not an appropriate solution, because this directory is removed on +make clean+. Therefore, Buildroot provides a specific mechanism for this use case: the +<pkg>_OVERRIDE_SRCDIR+ mechanism. Buildroot reads an _override_ file, which allows the user to tell Buildroot the location of the source for certain packages. By default this _override_ file is named +local.mk+ and located in the top directory of the Buildroot source tree, but a different location can be specified through the +BR2_PACKAGE_OVERRIDE_FILE+ configuration option. In this _override_ file, Buildroot expects to find lines of the form: ------------------ <pkg1>_OVERRIDE_SRCDIR = /path/to/pkg1/sources <pkg2>_OVERRIDE_SRCDIR = /path/to/pkg2/sources ------------------ For example: ------------------ LINUX_OVERRIDE_SRCDIR = /home/bob/linux/ BUSYBOX_OVERRIDE_SRCDIR = /home/bob/busybox/ ------------------ When Buildroot finds that for a given package, an +<pkg>_OVERRIDE_SRCDIR+ has been defined, it will no longer attempt to download, extract and patch the package. Instead, it will directly use the source code available in in the specified directory and +make clean+ will not touch this directory. This allows to point Buildroot to your own directories, that can be managed by Git, Subversion, or any other version control system. To achieve this, Buildroot will use _rsync_ to copy the source code of the component from the specified +<pkg>_OVERRIDE_SRCDIR+ to +output/build/<package>-custom/+. This mechanism is best used in conjunction with the +make <pkg>-rebuild+ and +make <pkg>-reconfigure+ targets. A +make <pkg>-rebuild all+ sequence will _rsync_ the source code from +<pkg>_OVERRIDE_SRCDIR+ to +output/build/<package>-custom+ (thanks to _rsync_, only the modified files are copied), and restart the build process of just this package. In the example of the +linux+ package above, the developer can then make a source code change in +/home/bob/linux+ and then run: ----------------------- make linux-rebuild all ----------------------- and in a matter of seconds gets the updated Linux kernel image in +output/images+. Similarly, a change can be made to the BusyBox source code in +/home/bob/busybox+, and after: ----------------------- make busybox-rebuild all ----------------------- the root filesystem image in +output/images+ contains the updated BusyBox.
shibajee/buildroot
docs/manual/using-buildroot-development.txt
Text
mit
3,481
// -*- mode:doc; -*- // vim: set syntax=asciidoc: ==== Using the generated toolchain outside Buildroot You may want to compile, for your target, your own programs or other software that are not packaged in Buildroot. In order to do this you can use the toolchain that was generated by Buildroot. The toolchain generated by Buildroot is located by default in +output/host/+. The simplest way to use it is to add +output/host/usr/bin/+ to your PATH environment variable and then to use +ARCH-linux-gcc+, +ARCH-linux-objdump+, +ARCH-linux-ld+, etc. It is possible to relocate the toolchain - but then +--sysroot+ must be passed every time the compiler is called to tell where the libraries and header files are. It is also possible to generate the Buildroot toolchain in a directory other than +output/host+ by using the +Build options -> Host dir+ option. This could be useful if the toolchain must be shared with other users.
shibajee/buildroot
docs/manual/using-buildroot-toolchain.txt
Text
mit
930
// -*- mode:doc; -*- // vim: set syntax=asciidoc: == Coding style Overall, these coding style rules are here to help you to add new files in Buildroot or refactor existing ones. If you slightly modify some existing file, the important thing is to keep the consistency of the whole file, so you can: * either follow the potentially deprecated coding style used in this file, * or entirely rework it in order to make it comply with these rules. [[writing-rules-config-in]] === +Config.in+ file +Config.in+ files contain entries for almost anything configurable in Buildroot. An entry has the following pattern: --------------------- config BR2_PACKAGE_LIBFOO bool "libfoo" depends on BR2_PACKAGE_LIBBAZ select BR2_PACKAGE_LIBBAR help This is a comment that explains what libfoo is. http://foosoftware.org/libfoo/ --------------------- * The +bool+, +depends on+, +select+ and +help+ lines are indented with one tab. * The help text itself should be indented with one tab and two spaces. * The help text should be wrapped to fit 72 columns. The +Config.in+ files are the input for the configuration tool used in Buildroot, which is the regular _Kconfig_. For further details about the _Kconfig_ language, refer to http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[]. [[writing-rules-mk]] === The +.mk+ file * Header: The file starts with a header. It contains the module name, preferably in lowercase, enclosed between separators made of 80 hashes. A blank line is mandatory after the header: + --------------------- ################################################################################ # # libfoo # ################################################################################ --------------------- + * Assignment: use +=+ preceded and followed by one space: + --------------------- LIBFOO_VERSION = 1.0 LIBFOO_CONF_OPTS += --without-python-support --------------------- + Do not align the +=+ signs. * Indentation: use tab only: + --------------------- define LIBFOO_REMOVE_DOC $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/doc \ $(TARGET_DIR)/usr/share/man/man3/libfoo* endef --------------------- + Note that commands inside a +define+ block should always start with a tab, so _make_ recognizes them as commands. * Optional dependency: ** Prefer multi-line syntax. + YES: + --------------------- ifeq ($(BR2_PACKAGE_PYTHON),y) LIBFOO_CONF_OPTS += --with-python-support LIBFOO_DEPENDENCIES += python else LIBFOO_CONF_OPTS += --without-python-support endif --------------------- + NO: + --------------------- LIBFOO_CONF_OPTS += --with$(if $(BR2_PACKAGE_PYTHON),,out)-python-support LIBFOO_DEPENDENCIES += $(if $(BR2_PACKAGE_PYTHON),python,) --------------------- ** Keep configure options and dependencies close together. * Optional hooks: keep hook definition and assignment together in one if block. + YES: + --------------------- ifneq ($(BR2_LIBFOO_INSTALL_DATA),y) define LIBFOO_REMOVE_DATA $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/data endef LIBFOO_POST_INSTALL_TARGET_HOOKS += LIBFOO_REMOVE_DATA endif --------------------- + NO: + --------------------- define LIBFOO_REMOVE_DATA $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/data endef ifneq ($(BR2_LIBFOO_INSTALL_DATA),y) LIBFOO_POST_INSTALL_TARGET_HOOKS += LIBFOO_REMOVE_DATA endif --------------------- === The documentation The documentation uses the http://www.methods.co.nz/asciidoc/[asciidoc] format. For further details about the http://www.methods.co.nz/asciidoc/[asciidoc] syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[].
shibajee/buildroot
docs/manual/writing-rules.txt
Text
mit
3,576
<!--#include file="header.html" --> <div class="container"> <div class="row nh"> <div class="col-lg-10 col-lg-offset-1 col-md-12 col-sm-12 col-xs-12"> <div class="panel panel-primary"> <div class="panel-heading">Contribute</div> <div class="panel-body"> <p>Buildroot is an open source project and you are very welcome to contribute to it.<br /> There are many different ways to contribute:</p> <ul> <li>Reproducing, analyzing and fixing bugs from our <a href="https://bugs.buildroot.org/">bug tracker</a></li> <li>Analyzing and fixing <a href="http://autobuild.buildroot.org/"> autobuild failures</a></li> <li>Reviewing and testing patches sent by other developers. See the <a href="http://lists.buildroot.org/mailman/listinfo/buildroot">mailing list </a> or <a href="http://patchwork.ozlabs.org/project/buildroot/list/"> patchwork</a>.</li> <li>Working on items from the <a href="http://www.elinux.org/Buildroot#Todo_list">TODO list</a></li> <li><a href="http://buildroot.org/manual.html#submitting-patches">Submitting your own patches</a> through the <a href="http://lists.buildroot.org/mailman/listinfo/buildroot">mailing list </a></li> </ul> <p>For more details on these topics, check out the <a href="http://buildroot.org/manual.html#_contributing_to_buildroot"> Contributing to buildroot</a> chapter in the Buildroot manual. Thanks for your help!</p> <p>If you need any support yourself, have a look at <a href="./support.html"> Support</a>.</p> </div> </div> </div><!--/.col-sm-10 --> </div><!--/.row --> </div> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/contribute.html
HTML
mit
1,651
The code and graphics on this website (and it's mirror sites, if any) are Copyright (c) 1999-2005 by Erik Andersen, 2006-2014 The Buildroot developers. All rights reserved. Documents on this Web site including their graphical elements, design, and layout are protected by trade dress and other laws and MAY BE COPIED OR IMITATED IN WHOLE OR IN PART. THIS WEBSITE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE WEBSITE TO THE EXTENT PERMITTED BY APPLICABLE LAW. SHOULD THIS WEBSITE PROVE DEFECTIVE, YOU MAY ASSUME THAT SOMEONE MIGHT GET AROUND TO SERVICING, REPAIRING OR CORRECTING IT SOMETIME WHEN THEY HAVE NOTHING BETTER TO DO. REGARDLESS, YOU GET TO KEEP BOTH PIECES. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THIS WEBSITE AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THIS WEBSITE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR LOSS OF HAIR, LOSS OF LIFE, LOSS OF MEMORY, LOSS OF YOUR CARKEYS, MISPLACEMENT OF YOUR PAYCHECK, OR COMMANDER DATA BEING RENDERED UNABLE TO ASSIST THE STARFLEET OFFICERS ABORD THE STARSHIP ENTERPRISE TO RECALIBRATE THE MAIN DEFLECTOR ARRAY, LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE WEBSITE TO OPERATE WITH YOUR WEBBROWSER), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You have been warned. You can contact the webmaster at <buildroot@buildroot.org> if you have some sort of problem with this.
shibajee/buildroot
docs/website/copyright.txt
Text
mit
1,630
/* * Author: Carlos Alvarez * URL: http://alvarez.is * * Project Name: FLATTY - Free Bootstrap 3 Theme * Version: 1.0 * URL: http://blacktie.co */ body { background-color: #f2f2f2; font-family: 'Roboto', sans-serif; font-weight: 300; font-size: 16px; color: #555; -webkit-font-smoothing: antialiased; -webkit-overflow-scrolling: touch; } /* Titles */ h1, h2, h3, h4, h5, h6 { font-family: 'Roboto', sans-serif; font-weight: 300; color: #333; } h1 { font-size: 40px; } h3 { color: #95a5a6; font-weight: 400; } h4 { color: #95a5a6; font-weight: 400; font-size: 20px; } .ellipsis p { margin-bottom:10px; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; } .centered { text-align: center; } /* Links */ a { color: #3498db; word-wrap: break-word; -webkit-transition: color 0.1s ease-in, background 0.1s ease-in; -moz-transition: color 0.1s ease-in, background 0.1s ease-in; -ms-transition: color 0.1s ease-in, background 0.1s ease-in; -o-transition: color 0.1s ease-in, background 0.1s ease-in; transition: color 0.1s ease-in, background 0.1s ease-in; } a:hover, a:focus { color: #7b7b7b; text-decoration: none; outline: 0; } a:before, a:after { -webkit-transition: color 0.1s ease-in, background 0.1s ease-in; -moz-transition: color 0.1s ease-in, background 0.1s ease-in; -ms-transition: color 0.1s ease-in, background 0.1s ease-in; -o-transition: color 0.1s ease-in, background 0.1s ease-in; transition: color 0.1s ease-in, background 0.1s ease-in; } hr { display: block; height: 1px; border: 0; border-top: 1px solid #ccc; margin: 1em 0; padding: 0; } .navbar-default { background-color: #3498db; border-color: transparent; } .navbar-default .navbar-brand { color: white; } .navbar-default .navbar-nav > li > a { color: white; } /* Helpers */ .mt { margin-top: 40px; margin-bottom: 40px; } .nh { margin-top: 80px; margin-bottom: 40px; } .form-control { height: 42px; font-size: 18px; width: 280px; } i { margin: 8px; color: #3498db; } /* HeaderWrap */ #headerwrap { /* background: url(../img/bg01.jpg) no-repeat center top; */ background-color: #3498db; margin-top: -20px; padding-top:120px; background-attachment: relative; background-position: center center; min-height: 400px; max-height: 800px; width: 100%; -webkit-background-size: 100%; -moz-background-size: 100%; -o-background-size: 100%; background-size: 100%; -webkit-background-size: cover; -moz-background-size: cover; -o-background-size: cover; background-size: cover; } #headerwrap h1 { color: white; font-size: 60px; font-weight: bold; letter-spacing: 1px; } #menubutton { max-height: 50px; margin-top: 6px; padding-top: 15px; margin-left: 10px; } .panel-sponsor { min-height: 350px; text-align: justify; text-justify: inter-word; } @media (min-width: 768px) and (max-width: 991px) { .navbar-collapse.collapse { display: none !important; } .navbar-collapse.collapse.in { display: block !important; } .navbar-header .collapse, .navbar-toggle { display:block !important; } .navbar-header { float:none; } .navbar-collapse { overflow:hidden; } #menubutton { margin-right: 40px; width: 45px; } .text-shrink { visibility: hidden; } } @media (max-width:767px) { #menubutton { max-height: 50px; margin-top: 6px; padding-top: 15px; margin-left: 15px; margin-right: 15px; } } /* entire container, keeps perspective */ .flip-container { perspective: 1000; } /* flip the pane when hovered */ .flip-container:hover .flipper, .flip-container.hover .flipper { transform: rotateY(180deg); } .flip-container, .front, .back { width: 180px; height: 180px; } /* flip speed goes here */ .flipper { transition: 0.6s; transform-style: preserve-3d; position: relative; } /* hide back of pane during swap */ .front, .back { backface-visibility: hidden; position: absolute; top: 0; left: 0; } /* front pane, placed above back */ .front { z-index: 2; /* for firefox 31 */ transform: rotateY(0deg); } /* back, initially hidden pane */ .back { transform: rotateY(180deg); } .back img { -moz-transform: scaleX(-1); -o-transform: scaleX(-1); -webkit-transform: scaleX(-1); transform: scaleX(-1); filter: FlipH; -ms-filter: "FlipH"; } .panel-box p { height: 1.5em; }
shibajee/buildroot
docs/website/css/main.css
CSS
mit
4,315
.timeline { list-style: none; padding: 20px 0 20px; position: relative; } .timeline:before { top: 0; bottom: 0; position: absolute; content: " "; width: 3px; background-color: #E4E4E4; left: 50%; margin-left: -1.5px; } .timeline > li { margin-bottom: 20px; position: relative; } .timeline > li:before, .timeline > li:after { content: " "; display: table; } .timeline > li:after { clear: both; } .timeline > li:before, .timeline > li:after { content: " "; display: table; } .timeline > li:after { clear: both; } .timeline > li > .timeline-panel { width: 46%; float: left; border: 1px solid #d4d4d4; border-radius: 2px; padding: 20px; position: relative; -webkit-box-shadow: 0 1px 6px rgba(0, 0, 0, 0.175); box-shadow: 0 1px 6px rgba(0, 0, 0, 0.175); background-color: white; } .timeline > li > .timeline-panel:before { position: absolute; top: 26px; right: -15px; display: inline-block; border-top: 15px solid transparent; border-left: 15px solid #ccc; border-right: 0 solid #ccc; border-bottom: 15px solid transparent; content: " "; } .timeline > li > .timeline-panel:after { position: absolute; top: 27px; right: -14px; display: inline-block; border-top: 14px solid transparent; border-left: 14px solid #fff; border-right: 0 solid #fff; border-bottom: 14px solid transparent; content: " "; } .timeline > li > .timeline-badge { color: #fff; width: 50px; height: 50px; line-height: 50px; font-size: 1.4em; text-align: center; position: absolute; top: 16px; left: 50%; margin-left: -25px; background-color: #E6E6E6; z-index: 100; border-top-right-radius: 50%; border-top-left-radius: 50%; border-bottom-right-radius: 50%; border-bottom-left-radius: 50%; } .timeline > li.timeline-inverted > .timeline-panel { float: right; } .timeline > li.timeline-inverted > .timeline-panel:before { border-left-width: 0; border-right-width: 15px; left: -15px; right: auto; } .timeline > li.timeline-inverted > .timeline-panel:after { border-left-width: 0; border-right-width: 14px; left: -14px; right: auto; } .timeline-badge.primary { background-color: #2e6da4 !important; } .timeline-badge.success { background-color: #3f903f !important; } .timeline-badge.warning { background-color: #f0ad4e !important; } .timeline-badge.danger { background-color: #d9534f !important; } .timeline-badge.info { background-color: #5bc0de !important; } .timeline-title { margin-top: 0; color: inherit; } .timeline-body > p, .timeline-body > ul { margin-bottom: 0; } .timeline-body > p + p { margin-top: 5px; } @media (max-width: 767px) { ul.timeline:before { left: 40px; } ul.timeline > li > .timeline-panel { width: calc(100% - 90px); width: -moz-calc(100% - 90px); width: -webkit-calc(100% - 90px); } ul.timeline > li > .timeline-badge { left: 15px; margin-left: 0; top: 16px; } ul.timeline > li > .timeline-panel { float: right; } ul.timeline > li > .timeline-panel:before { border-left-width: 0; border-right-width: 15px; left: -15px; right: auto; } ul.timeline > li > .timeline-panel:after { border-left-width: 0; border-right-width: 14px; left: -14px; right: auto; } }
shibajee/buildroot
docs/website/css/timeline.css
CSS
mit
3,197
<!--#include file="header.html" --> <div class="container"> <div class="row nh"> <div class="col-lg-10 col-lg-offset-1 col-md-12 col-sm-12 col-xs-12"> <div class="panel panel-primary"> <div class="panel-heading">Documentation</div> <div class="panel-body"> <p>The Buildroot user manual is where you want to start reading if you wish to understand how Buildroot works, or wish to change/extend/fix things. It is available as:</p> <div class="row mt centered"> <div class="col-sm-4"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <a href="/manual.html"><img src="images/browser.png" width="180" alt=""></a> </div> <div class="back"> <a href="/manual.html"><img src="images/browser.png" width="180" alt=""></a> </div> </div> </div> <h3>HTML <br> <a href="/manual.html">Stable</a> | <a href="http://nightly.buildroot.org/manual.html">Nightly</a> </h3> </div> <div class="col-sm-4"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <img src="images/pdf-icon.png" width="180" alt=""> </div> <div class="back"> <img src="images/pdf-icon.png" width="180" alt=""> </div> </div> </div> <h3>PDF <br> <a href="/downloads/manual/manual.pdf">Stable</a> | <a href="http://nightly.buildroot.org/manual.pdf">Nightly</a> </h3> </div> <div class="col-sm-4"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <img src="images/text.png" width="180" alt=""> </div> <div class="back"> <img src="images/text.png" width="180" alt=""> </div> </div> </div> <h3>ASCII <br> <a href="/downloads/manual/manual.text">Stable</a> | <a href="http://nightly.buildroot.org/manual.text">Nightly</a> </h3> </div> </div> <p>If you find any errors (factual, grammatical, whatever) please report them to us.</p> </div> </div> <div class="panel panel-primary"> <div class="panel-heading">Training</div> <div class="panel-body"> <p><a href="http://www.free-electrons.com">Free Electrons</a> offers a complete <a href="http://free-electrons.com/training/buildroot/">3-days training course on Buildroot</a>. They also make the training materials freely available:</p> <div class="row"> <div class="col-sm-8"> <div class="panel panel-success"> <div class="panel-heading">Slides preview</div> <div class="panel-body"> <div id="slides" style="width: 100%; padding-bottom: 75%; position: relative"> <a href="http://free-electrons.com/doc/training/buildroot/buildroot-slides.pdf"><img src="images/buildroot-slides.png" alt="buildroot slides" style="position:absolute; width:100%; height:100%; top:0; left:0;"></a> </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default "> <div class="panel-heading">Training materials</div> <div class="panel-body"> <ul> <li><a href="http://free-electrons.com/doc/training/buildroot/buildroot-slides.pdf">slides (PDF)</a></li> <li><a href="http://free-electrons.com/doc/training/buildroot/buildroot-labs.pdf">practical labs (PDF)</a></li> <li><a href="http://free-electrons.com/doc/training/buildroot/buildroot-labs.tar.xz">practical labs data (.tar.xz)</a></li> </ul> </div> </div> </div> </div> </div> </div> </div> </div> </div> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/docs.html
HTML
mit
3,706
<!--#include file="header.html" --> <div class="container"> <div class="row nh"> <div class="col-lg-10 col-lg-offset-1 col-md-12 col-sm-12 col-xs-12"> <div class="panel panel-primary"> <div class="panel-heading">Download</div> <div class="panel-body"> <h3 style="text-align: center;">Latest stable release: <b>2016.08</b></h3> <div class="row mt centered"> <div class="col-sm-6"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <a href="/downloads/buildroot-2016.08.tar.gz"><img src="images/zip.png" width="180" alt=""></a> </div> <div class="back"> <a href="/downloads/buildroot-2016.08.tar.gz"><img src="images/zip.png" width="180" alt=""></a> </div> </div> </div> <h3><a href="/downloads/buildroot-2016.08.tar.gz">buildroot-2016.08.tar.gz</a></h3> <p><a href="/downloads/buildroot-2016.08.tar.gz.sign">PGP signature</a></p> </div> <div class="col-sm-6"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <a href="/downloads/buildroot-2016.08.tar.bz2"><img src="images/package.png" width="180" alt=""></a> </div> <div class="back"> <a href="/downloads/buildroot-2016.08.tar.bz2"><img src="images/package.png" width="180" alt=""></a> </div> </div> </div> <h3><a href="/downloads/buildroot-2016.08.tar.bz2">buildroot-2016.08.tar.bz2</a></h3> <p><a href="/downloads/buildroot-2016.08.tar.bz2.sign">PGP signature</a></p> </div> </div> <!-- <h3 style="text-align: center;">Latest release candidate: <b>2016.08-rc3</b></h3> <div class="row mt centered"> <div class="col-sm-6"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <a href="/downloads/buildroot-2016.08-rc3.tar.gz"><img src="images/zip.png" width="180" alt=""></a> </div> <div class="back"> <a href="/downloads/buildroot-2016.08-rc3.tar.gz"><img src="images/zip.png" width="180" alt=""></a> </div> </div> </div> <h3><a href="/downloads/buildroot-2016.08-rc3.tar.gz">buildroot-2016.08-rc3.tar.gz</a></h3> <p><a href="/downloads/buildroot-2016.08-rc3.tar.gz.sign">PGP signature</a></p> </div> <div class="col-sm-6"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <a href="/downloads/buildroot-2016.08-rc3.tar.bz2"><img src="images/package.png" width="180" alt=""></a> </div> <div class="back"> <a href="/downloads/buildroot-2016.08-rc3.tar.bz2"><img src="images/package.png" width="180" alt=""></a> </div> </div> </div> <h3><a href="/downloads/buildroot-2016.08-rc3.tar.bz2">buildroot-2016.08-rc3.tar.bz2</a></h3> <p><a href="/downloads/buildroot-2016.08-rc3.tar.bz2.sign">PGP signature</a></p> </div> </div> --> This and earlier releases (and their PGP signatures) can always be downloaded from <a href="/downloads/">http://buildroot.net/downloads/</a>. </div> </div> <div class="panel panel-primary"> <div class="panel-heading">Source code</div> <div class="panel-body"> <div class="row"> <div class="col-sm-7"> <div class="panel panel-success"> <div class="panel-heading">Repository</div> <div class="panel-body"> <P>The buildroot repository can be browsed online through cgit at <a href="http://git.buildroot.net/buildroot/">http://git.buildroot.net/buildroot</a>. To grab a copy of the repository use</p> <div class="input-group" style="width: 100%;"> <input class="form-control" style="width: 85%;" id="giturl" value="git clone git://git.buildroot.net/buildroot" type="text" readonly></input> <span class="input-group-button"> <button class="btn pull-right" type="button" data-clipboard-target="#giturl" data-toggle="tooltip" data-placement="bottom" data-trigger="manual" title="Copied!"> <img class="clippy" src="images/clippy.svg" alt="Copy to clipboard" width="13"> </button> </span> </div><br> <p> Or if you're behind a firewall blocking git: </p> <div class="input-group" style="width: 100%;"> <input class="form-control" style="width: 85%;" id="giturlhttps" value="git clone https://git.buildroot.net/buildroot" type="text" readonly></input> <span class="input-group-button"> <button class="btn pull-right" type="button" data-clipboard-target="#giturlhttps" data-toggle="tooltip" data-placement="bottom" data-trigger="click" title="Copied!"> <img class="clippy" src="images/clippy.svg" alt="Copy to clipboard" width="13"> </button> </span> </div><br> <p> Please use the native git protocol if at all possible, as it's a lot more efficient than HTTP. <p> If you are not already familiar with using Git, we recommend you visit <a href="http://git-scm.org">the Git website</a>. <p> Once you've checked out a copy of the source tree, you can update your source tree at any time so it is in sync with the latest and greatest by entering your buildroot directory and running the command: <pre> git pull </pre> Because you've only been granted anonymous access to the tree, you won't be able to push your changes to the repo. Changes can instead be submitted for inclusion by posting them to the buildroot mailing list. </div> </div> </div> <div class="col-sm-5"> <div class="panel panel-default "> <div class="panel-heading">Tarballs</div> <div class="panel-body"> You can also obtain daily snapshots of the latest Buildroot source tree if you want to follow development, but cannot or do not wish to use Git. <ul> <li>You can download the <a href="downloads/snapshots/buildroot-snapshot.tar.bz2">latest snapshot </a> or view recent <a href="downloads/snapshots/">daily snapshots</a>. </li> <li>You can also <a href="http://git.buildroot.net/buildroot">browse the source tree online</a>. </li> </ul> <p> Older versions can be downloaded from <a href="/downloads/">the release archive</a>. </p> </div> </div> </div> </div> </div> </div> </div><!--/.col-sm-10 --> </div><!--/.row --> </div> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/download.html
HTML
mit
6,546
<script src="https://code.jquery.com/jquery-1.11.3.min.js"></script> <script src="https://oss.maxcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script> <script type="text/javascript" src="https://www.google.com/jsapi"></script> <script src="https://cdn.rawgit.com/zenorocha/clipboard.js/master/dist/clipboard.min.js"></script> <script type="text/javascript" src="js/buildroot.js"></script> </body> </html>
shibajee/buildroot
docs/website/footer.html
HTML
mit
411
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta name="Buildroot" content=""> <meta name="angelo.compagnucci@gmail.com" content=""> <link rel="shortcut icon" href="images/favicon.png"> <title>Buildroot - Making Embedded Linux Easy</title> <link href="https://oss.maxcdn.com/bootswatch/3.3.5/paper/bootstrap.min.css" rel="stylesheet"> <link href="css/main.css" rel="stylesheet"> <!--[if lt IE 9]> <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script> <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script> <![endif]--> </head> <body> <!-- Fixed navbar --> <div class="navbar navbar-default navbar-fixed-top"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse"> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a class="navbar-brand" href="/"><b>Buildroot</b></a> </div> <div class="navbar-collapse collapse"> <ul class="nav navbar-nav navbar-right"> <li><a href="/news.html"> <span class="glyphicon glyphicon-star"></span> News</a></li> <li><a href="/docs.html"> <span class="glyphicon glyphicon-book"></span> Documentation</a></li> <li><a href="/support.html"> <span class="glyphicon glyphicon-question-sign"></span> Support</a></li> <li><a href="/contribute.html"> <span class="glyphicon glyphicon-share"></span> Contribute</a></li> <li><a href="/sponsors.html"> <span class="glyphicon glyphicon-usd"></span> Sponsors</a></li> <li><a id="menubutton" class="btn btn-success btn-shrink" href="/download.html"> <span class="glyphicon glyphicon-cloud-download"></span> <span class="text-shrink" >Download</span></a></li> </ul> </div><!--/.nav-collapse --> </div> </div>
shibajee/buildroot
docs/website/header.html
HTML
mit
2,044
<svg height="1024" width="896" xmlns="http://www.w3.org/2000/svg"> <path d="M128 768h256v64H128v-64z m320-384H128v64h320v-64z m128 192V448L384 640l192 192V704h320V576H576z m-288-64H128v64h160v-64zM128 704h160v-64H128v64z m576 64h64v128c-1 18-7 33-19 45s-27 18-45 19H64c-35 0-64-29-64-64V192c0-35 29-64 64-64h192C256 57 313 0 384 0s128 57 128 128h192c35 0 64 29 64 64v320h-64V320H64v576h640V768zM128 256h512c0-35-29-64-64-64h-64c-35 0-64-29-64-64s-29-64-64-64-64 29-64 64-29 64-64 64h-64c-35 0-64 29-64 64z"/> </svg>
shibajee/buildroot
docs/website/images/clippy.svg
svg
mit
517
<!--#include file="header.html" --> <div id="headerwrap"> <div class="container"> <div class="row"> <div class="col-sm-6"> <img class="img-responsive center-block" src="images/logo.png" alt="" style="max-width:300px"> </div><!-- /col-lg-6 --> <div class="col-sm-6"> <h1>Buildroot<br> <small>Making Embedded Linux Easy</small></h1> <div class="col-sm-6" style="margin-top:1em; padding-left:0px;"> <a class="btn btn-default btn-lg" style="width:100%;" href="#about"><span class="glyphicon glyphicon-info-sign"></span>&nbsp; Learn more</a> </div> <div class="col-sm-6" style="margin-top:1em; padding-left:0px;"> <a class="btn btn-default btn-lg" style="width:100%; margin-bottom: 20px;" href="/download.html"><span class="glyphicon glyphicon-cloud-download"></span>&nbsp; Download</a> </div> </div><!-- /col-lg-6 --> </div><!-- /row --> </div><!-- /container --> </div><!-- /headerwrap --> <a name="about"></a> <div class="container"> <div class="row mt centered"> <div class="col-lg-8 col-lg-offset-2"> <h1>Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation.</h1> </div> </div><!-- /row --> <div class="row mt centered"> <div class="col-md-4"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <img src="images/tux-flat.png" width="180" alt=""> </div> <div class="back"> <img src="images/tux-flat.png" width="180" alt=""> </div> </div> </div> <h4>Can handle everything</h4> <p>Cross-compilation toolchain, root filesystem generation, kernel image compilation and bootloader compilation.</p> </div><!--/col-lg-4 --> <div class="col-md-4"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <img src="images/hammer.png" width="180" alt=""> </div> <div class="back"> <img src="images/hammer.png" width="180" alt=""> </div> </div> </div> <h4>Is very easy</h4> <p>Thanks to its kernel-like menuconfig, gconfig and xconfig configuration interfaces, building a basic system with Buildroot is easy and typically takes 15-30 minutes.</p> </div><!--/col-lg-4 --> <div class="col-md-4"> <div class="flip-container center-block" ontouchstart="this.classList.toggle('hover');"> <div class="flipper"> <div class="front"> <img src="images/gift.png" width="180" alt=""> </div> <div class="back"> <img src="images/gift.png" width="180" alt=""> </div> </div> </div> <h4>Supports hundreds of packages</h4> <p>X.org stack, Gtk3, Qt 5, GStreamer, Webkit, Kodi, a large number of network-related and system-related utilities are supported.</p> </div><!--/col-lg-4 --> </div><!-- /row --> <hr> </div><!-- /container --> <div class="container"> <div class="row mt centered"> <div class="col-lg-6 col-lg-offset-3"> <h1>Buildroot is for Everyone.</h1> <h3>Has a simple structure that makes it easy to understand and extend. It relies only on the well-known Makefile language.</h3> </div> </div><!-- /row --> <div class="row mt centered"> <div class="col-lg-8 col-lg-offset-2"> <div id="carousel-example-generic" class="carousel slide" data-ride="carousel"> <!-- Wrapper for slides --> <div class="carousel-inner"> <div class="item active"> <img src="images/nconfig.png" alt=""> </div> <div class="item"> <img src="images/menuconfig.png" alt=""> </div> <div class="item"> <img src="images/xconfig.png" alt=""> </div> </div> <!-- Indicators --> <ol class="carousel-indicators" style="margin-top:10px"> <li data-target="#carousel-example-generic" data-slide-to="0" class="active"></li> <li data-target="#carousel-example-generic" data-slide-to="1"></li> <li data-target="#carousel-example-generic" data-slide-to="2"></li> </ol> </div> </div><!-- /col-lg-8 --> </div><!-- /row --> </div><!-- /container --> <div class="container"> <div class="row mt centered"> <div class="col-lg-6 col-lg-offset-3"> <h1>Our recent activity.</h1> <h3>Buildroot is an open source project: many developers contribute to it daily.</h3> </div> </div><!-- /row --> </div><!-- /container --> <div class="container"> <div class="row"> <div class="col-sm-6"> <div class="panel panel-primary"> <div class="panel-heading"><a href="http://git.buildroot.net/buildroot"><h5>Recent commits</h5></a></div> <div class="panel-box panel-body ellipsis" id="commit-activity"> </div> </div> </div> <div class="col-sm-6" > <div class="panel panel-primary"> <div class="panel-heading"><a href="http://dir.gmane.org/gmane.comp.lib.uclibc.buildroot"><h5>Recent discussions</h5></a></div> <div class="panel-box panel-body ellipsis" id="mailing-list-activity"> </div> </div> </div> </div> </div><!-- /container --> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/index.html
HTML
mit
5,132
function load_activity(feedurl, divid) { var feed = new google.feeds.Feed(feedurl); var container = document.getElementById(divid); var loaded = 0; var nb_display = 8; feed.setNumEntries(30); feed.load(function(result) { if (result.error) { return; } for (var i = 0; i < result.feed.entries.length; i++) { var entry = result.feed.entries[i]; if (entry.title.indexOf("git commit") != -1) continue; loaded += 1; if (loaded > nb_display) break; var div = document.createElement("p"); var link = document.createElement("a"); var d = new Date(entry.publishedDate); var data = '[' + d.toLocaleDateString() + '] ' + entry.title var text = document.createTextNode(data); link.appendChild(text); link.title = entry.title; link.href = entry.link div.appendChild(link); container.appendChild(div); } var empty = nb_display - loaded; for (var i = 0; i < empty; i++) { container.appendChild(document.createElement("p")); } }); } function initialize() { load_activity("http://rss.gmane.org/topics/excerpts/gmane.comp.lib.uclibc.buildroot", "mailing-list-activity"); load_activity("http://git.buildroot.org/buildroot/atom/?h=master", "commit-activity"); } function google_analytics() { var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-21761074-1']); _gaq.push(['_setDomainName', 'none']); _gaq.push(['_setAllowLinker', true]); _gaq.push(['_trackPageview']); var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); } $(function() { $('a[href*=#]:not([href=#])').click(function() { if (location.pathname.replace(/^\//,'') == this.pathname.replace(/^\//,'') && location.hostname == this.hostname) { var target = $(this.hash); target = target.length ? target : $('[name=' + this.hash.slice(1) +']'); if (target.length) { $('html,body').animate({ scrollTop: target.offset().top }, 1000); return false; } } }); }); google.load("feeds", "1"); google.setOnLoadCallback(initialize); google_analytics(); jQuery(document).ready(function($) { var url = window.location.href; // Get the basename of the URL url = url.split(/[\\/]/).pop() $('.nav a[href="/' + url + '"]').parent().addClass('active'); $('#slides').html('<iframe src="https://docs.google.com/gview?url=http://free-electrons.com/doc/training/buildroot/buildroot-slides.pdf&embedded=true" style="position:absolute; width:100%; height:100%; top:0; left:0;" frameborder="0"></iframe>') }); function showTooltip(elem, msg) { elem.setAttribute('class', 'btn tooltipped tooltipped-s'); elem.setAttribute('aria-label', msg); } var clipboard = new Clipboard('.btn'); $(function () { $('[data-toggle="tooltip"]').tooltip() }) clipboard.on('success', function(e) { e.clearSelection(); $(e.trigger).tooltip('show'); }); $(function() { $('a[href*=#]:not([href=#])').click(function() { if (location.pathname.replace(/^\//,'') == this.pathname.replace(/^\//,'') && location.hostname == this.hostname) { var target = $(this.hash); target = target.length ? target : $('[name=' + this.hash.slice(1) +']'); if (target.length) { $('html,body').animate({ scrollTop: target.offset().top }, 1000); return false; } } }); });
shibajee/buildroot
docs/website/js/buildroot.js
JavaScript
mit
3,821
<!--#include file="header.html" --> <link href="css/timeline.css" rel="stylesheet"> <div class="container"> <div class="row nh"> <div class="col-lg-10 col-lg-offset-1 col-md-12 col-sm-12 col-xs-12"> <h2>News</h2> <ul class="timeline"> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 September 2016</small></p> </div> <div class="timeline-body"> <p>The stable 2016.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.08">CHANGES</a> file for more details and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.08.tar.bz2">2016.08 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.08-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 August 2016</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and security / build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.08-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.08-rc3.tar.bz2">2016.08-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>17 August 2016</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.08-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.08-rc2.tar.bz2">2016.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>6 August 2016</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.08-rc1">CHANGES</a> file for details and read the <a href="http://lists.busybox.net/pipermail/buildroot/2016-August/169277.html">announcement</a> </p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.08-rc1.tar.bz2">2016.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.buildroot.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 March 2016</small></p> </div> <div class="timeline-body"> <p>The stable 2016.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.05">CHANGES</a> file for more details, read the <a href="http://lists.busybox.net/pipermail/buildroot/2016-May/162428.html">announcement<a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.05.tar.bz2">2016.05 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 May 2016</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and security / build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.05-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.05-rc3.tar.bz2">2016.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>17 May 2016</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.05-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.05-rc2.tar.bz2">2016.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>10 May 2016</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.05-rc1">CHANGES</a> file for details and read the <a href="http://lists.busybox.net/pipermail/buildroot/2016-May/160897.html">announcement</a>. </p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.05-rc1.tar.bz2">2016.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.buildroot.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 March 2016</small></p> </div> <div class="timeline-body"> <p>The stable 2016.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.02">CHANGES</a> file for more details, read the <a href="http://lists.busybox.net/pipermail/buildroot/2016-March/154535.html">announcement<a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.02.tar.bz2">2016.02 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.02-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>27 February 2016</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and security / build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.02-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.02-rc3.tar.bz2">2016.02-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 February 2016</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.02-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.02-rc2.tar.bz2">2016.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2016.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>10 February 2016</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.02-rc1">CHANGES</a> file for details and read the <a href="http://lists.busybox.net/pipermail/buildroot/2016-February/152420.html">announcement</a>. </p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2016.02-rc1.tar.bz2">2016.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.11.1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>5 December 2015</small></p> </div> <div class="timeline-body"> <p>The 2015.11.1 bugfix release is out - Thanks to everyone contributing. This release fixes critical issues discovered since the 2015.11 release. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.11.1">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.11.1.tar.bz2">2015.11.1 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 November 2015</small></p> </div> <div class="timeline-body"> <p>The stable 2015.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.11">CHANGES</a> file for more details, read the <a href="http://lists.busybox.net/pipermail/buildroot/2015-November/145727.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.11.tar.bz2">2015.11 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.11-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 November 2015</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and security / build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.11-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.11-rc3.tar.bz2">2015.11-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>19 November 2015</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.11-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.11-rc2.tar.bz2">2015.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>7 November 2015</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.11-rc1">CHANGES</a> file for details. See also the <a href="http://lists.busybox.net/pipermail/buildroot/2015-November/144026.html">announcement e-mail</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.11-rc1.tar.bz2">2015.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.08.1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>6 September 2015</small></p> </div> <div class="timeline-body"> <p>The 2015.08.1 bugfix release is out - Thanks to everyone contributing. This release fixes critical issues discovered since the 2015.08 release. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.08.1">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.08.1.tar.bz2">2015.08.1 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 August 2015</small></p> </div> <div class="timeline-body"> <p>The stable 2015.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.08">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-August/138336.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.08.tar.bz2">2015.08 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>24 August 2015</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.08-rc2">CHANGES</a> file for details, and the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-August/137879.html">release announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.08-rc2.tar.bz2">2015.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>5 August 2015</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.08-rc1">CHANGES</a> file for details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-August/135417.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.08-rc1.tar.bz2">2015.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 May 2015</small></p> </div> <div class="timeline-body"> <p>The stable 2015.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.05">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-May/129209.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.05.tar.bz2">2015.05 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>22 May 2015</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and security / build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.05-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.05-rc3.tar.bz2">2015.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>11 May 2015</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.05-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.05-rc2.tar.bz2">2015.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>4 May 2015</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.05-rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-May/127794.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.05-rc1.tar.bz2">2015.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 March 2015</small></p> </div> <div class="timeline-body"> <p>The stable 2015.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.02">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-March/120396.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.02.tar.bz2">2015.02 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.02-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>24 February 2015</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and security / build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.02-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.02-rc3.tar.bz2">2015.02-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>15 February 2015</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.02-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.02-rc2.tar.bz2">2015.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2015.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>8 February 2015</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2015.02-rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2015-February/118982.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2015.02-rc1.tar.bz2">2015.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 December 2014</small></p> </div> <div class="timeline-body"> <p>The stable 2014.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.11">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.11.tar.bz2">2014.11 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.11-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>28 November 2014</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.11-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.11-rc3.tar.bz2">2014.11-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>21 November 2014</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.11-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.11-rc2.tar.bz2">2014.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Report from Buildroot Developers Meeting</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>13 November 2014</small></p> </div> <div class="timeline-body"> <p>A report from the recent <a href="http://elinux.org/Buildroot:DeveloperDaysELCE2014"> Buildroot Developers Meeting</a> is now <a href="http://lists.buildroot.org/pipermail/buildroot/2014-October/109966.html">available</a>.</p> <p>Once again, thanks to all the participants and to <a href="http://www.mind.be">Mind</a> for sponsoring the event.</p> <p>The next Developer Days will take place on February 2nd and 3rd in Brussels, Belgium, right after <a href="http://fosdem.org">FOSDEM</a>. See the <a href="http://elinux.org/Buildroot:DeveloperDaysFOSDEM2015">wiki</a> for more details.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>12 November 2014</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.11-rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2014-November/111946.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.11-rc1.tar.bz2">2014.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 September 2014</small></p> </div> <div class="timeline-body"> <p>The stable 2014.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.08">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2014-September/105257.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.08.tar.bz2">2014.08 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.08-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 August 2014</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.08-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.08-rc3.tar.bz2">2014.08-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 August 2014</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.08-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.08-rc2.tar.bz2">2014.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>8 August 2014</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.08-rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2014-August/103972.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.08-rc1.tar.bz2">2014.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 May 2014</small></p> </div> <div class="timeline-body"> <p>The stable 2014.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.05">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2014-May/097863.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.05.tar.bz2">2014.05 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>28 May 2014</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.05-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.05-rc3.tar.bz2">2014.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>21 May 2014</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.05-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.05-rc2.tar.bz2">2014.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>13 May 2014</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.05-rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2014-May/096492.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.05-rc1.tar.bz2">2014.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">27 February 2014</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>2014.02 released</small></p> </div> <div class="timeline-body"> <p>The stable 2014.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.02">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.02.tar.bz2">2014.02 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">25 February 2014</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>2014.02-rc3 released</small></p> </div> <div class="timeline-body"> <p>Release candidate 3 is out with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.02-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.02-rc3.tar.bz2">2014.02-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">20 February 2014</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>2014.02-rc2 released</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.02-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.02-rc2.tar.bz2">2014.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2014.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>11 February 2014</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2014.02-rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2014-February/089055.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2014.02-rc1.tar.bz2">2014.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">9 February 2014</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>Report from Buildroot Developers Meeting</small></p> </div> <div class="timeline-body"> <p>A report from the recent <a href="http://elinux.org/Buildroot:DeveloperDaysFOSDEM2014"> Buildroot Developers Meeting</a> is now <a href="http://lists.buildroot.org/pipermail/buildroot/2014-February/088373.html">available</a>.</p> <p>Once again, thanks to all the participants and to <a href="http://www.google.com">Google</a> and <a href="http://www.mind.be">Mind</a> for sponsoring the event.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Upcoming Buildroot Developers meeting</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 January 2014</small></p> </div> <div class="timeline-body"> <p>The upcoming Buildroot Developers meeting will take place in Brussels on February, 3rd and 4th, after the <a href="http://www.fosdem.org">FOSDEM</a> conference. Additional details about the meeting can be found on the corresponding <a href="http://elinux.org/Buildroot:DeveloperDaysFOSDEM2014"> wiki page</a>.</p> <p>Persons not able to join the meeting in Brussels can participate remotely using Google Hangouts. Simply give your Google address to <code>thomas.petazzoni@free-electrons.com</code>.</p> <p>This meeting is sponsored by <a href="http://www.google.com">Google</a> (for the meeting room) and <a href="http://www.mind.be">Mind</a> (for the dinner). Thanks to our sponsors!</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 November 2013</small></p> </div> <div class="timeline-body"> <p>The stable 2013.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.11">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2013-November/083600.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.11.tar.bz2">2013.11 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Slides from Embedded Linux Conference Europe</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 November 2013</small></p> </div> <div class="timeline-body"> <p>The slides from the Buildroot presentation at the recent <a href="http://events.linuxfoundation.org/events/embedded-linux-conference-europe">Embedded Linux Conference Europe 2013</a> are now <a href="http://elinux.org/images/2/23/Buildroot-whats-new-elce2013.pdf">available</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.11-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 November 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.11-rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.11-rc3.tar.bz2">2013.11-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 November 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.11-rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.11-rc2.tar.bz2">2013.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Announcement of the next Buildroot Developer Days</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>13 November 2013</small></p> </div> <div class="timeline-body"> <p>The next <i>Buildroot Developer Days</i> meeting will take place on Monday 3rd and Tuesday 4th February 2014 in Brussels, Belgium - Just after <a href="http://www.fosdem.org">FOSDEM</a> (February 1st/2nd). This two days meeting is mainly open to Buildroot developers and contributors, or Buildroot users having a prior experience with the tool. It will allow developers to work on Buildroot and discuss current issues, the future directions, and more.</p> <p>In addition to the Buildroot event, we encourage embedded Linux developers to propose talks for the Embedded and Mobile Developer Room at FOSDEM. See the <a href="https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html">CFP</a>.</p> <p>We would like to thank our sponsor <a href="http://www.google.com">Google</a> for sponsoring the event by providing all the needed logistics.</p> <p>For more details, see the <a href="http://www.elinux.org/Buildroot:DeveloperDaysFOSDEM2014">wiki page</a> dedicated to the meeting.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>12 November 2013</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.11_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2013-November/082514.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.11-rc1.tar.bz2">2013.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Report from Buildroot Developers Meeting</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>11 November 2013</small></p> </div> <div class="timeline-body"> <p>A report from the recent <a href="http://elinux.org/Buildroot:DeveloperDaysELCE2013"> Buildroot Developers Meeting</a> is now <a href="http://lists.buildroot.org/pipermail/buildroot/2013-November/082401.html">available</a>.</p> <p>Once again, thanks to all the participants and to <a href="http://www.imgtec.com/">Imagination Technologies</a> for sponsoring the event.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.08.1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>17 September 2013</small></p> </div> <div class="timeline-body"> <p>The 2013.08.1 bugfix release is out - Thanks to everyone contributing. This release fixes critical issues discovered since the 2013.08 release. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.08.1">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.08.1.tar.bz2">2013.08.1 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot Developer Days</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>16 September 2013</small></p> </div> <div class="timeline-body"> <p>The next <i>Buildroot Developer Days</i> meeting will take place on Saturday October 26th and Sunday October 27th 2013 in Edinburgh, UK - Just after the <a href="https://events.linuxfoundation.org/events/embedded-linux-conference-europe"> Embedded Linux Conference Europe</a> (October 23th-24th). This two days meeting is mainly open to Buildroot developers and contributors, or Buildroot users having a prior experience with the tool. It will allow developers to work on Buildroot and discuss current issues, the future directions, and more.</p> <p>For more details, see the <a href="http://www.elinux.org/Buildroot:DeveloperDaysELCE2013">wiki page</a> dedicated to the meeting.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 August 2013</small></p> </div> <div class="timeline-body"> <p>The stable 2013.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.08">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2013-August/077224.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.08.tar.bz2">2013.08 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.08-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>29 August 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.08_rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.08-rc3.tar.bz2">2013.08-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>16 August 2013</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.08_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.08-rc2.tar.bz2">2013.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>5 August 2013</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.08_rc1">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.08-rc1.tar.bz2">2013.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 May 2013</small></p> </div> <div class="timeline-body"> <p>The stable 2013.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.05">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2013-May/073121.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.05.tar.bz2">2013.05 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>25 May 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.05_rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.05-rc3.tar.bz2">2013.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>15 May 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.05_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.05-rc2.tar.bz2">2013.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>8 May 2013</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.05_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2013-May/071737.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.05-rc1.tar.bz2">2013.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>28 February 2013</small></p> </div> <div class="timeline-body"> <p>The stable 2013.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.02">CHANGES</a> file for more details and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.02.tar.bz2">2013.02 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.02-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 February 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.02_rc3">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.02-rc3.tar.bz2">2013.02-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>19 February 2013</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.02_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.02-rc2.tar.bz2">2013.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2013.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>10 February 2013</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2013.02_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2013-February/067148.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2013.02-rc1.tar.bz2">2013.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Report from Buildroot Developers Meeting</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>10 February 2013</small></p> </div> <div class="timeline-body"> <p>A report from the recent Buildroot Developers Meeting is now <a href="http://lists.buildroot.org/pipermail/buildroot/2013-February/067105.html">available</a>. <a href="http://emlinews.net">Embedded Linux News</a> also has a <a href="http://www.emlinews.net/2013/02/buildroot-developers-meeting-report/"> writeup about the event</a>, including photos.</p> <p>Once again, thanks to all the participants and to <a href="http://www.google.com">Google</a> for sponsoring the event.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Next Buildroot Developers Meeting next to FOSDEM, Brussels</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>12 January 2013</small></p> </div> <div class="timeline-body"> <p>The next Buildroot Developers Meeting will take place on Monday 4th February 2013 and Tuesday 5th February 2013 in Brussels, Belgium. Those dates have been chosen to immediately follow the great <a href="http://www.fosdem.org">FOSDEM</a> conference.</p> <p>Attending this meeting is free, after registration by contacting <a href="mailto:thomas.petazzoni@free-electrons.com">Thomas Petazzoni</a>. For more details about the meeting, please see the <a href="http://elinux.org/Buildroot:DeveloperDaysFOSDEM2013">related Wiki page</a>.</p> <p>We would like to thank <a href="http://www.google.com">Google</a> for providing the meeting location and the Internet connection, and offering free lunch and refreshments to the participants.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.11.1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>3 January 2013</small></p> </div> <div class="timeline-body"> <p>The 2012.11.1 bugfix release is out - Thanks to everyone contributing. This release fixes critical issues discovered since the 2012.11 release, most importantly with non-largefile builds on recent Ubuntu versions. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.11.1">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.11.1.tar.bz2">2012.11.1 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>2 December 2012</small></p> </div> <div class="timeline-body"> <p>The stable 2012.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.11">CHANGES</a> file for more details and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.11.tar.bz2">2012.11 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 November 2012</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more bugfixes - See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.11_rc2">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.11-rc2.tar.bz2">2012.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>17 November 2012</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.11_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2012-November/061995.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.11-rc1.tar.bz2">2012.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot Developer Day</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>17 November 2012</small></p> </div> <div class="timeline-body"> <p>A report from the recent <i>Buildroot Developer Days</i> meeting in Barcelona, Spain is now <a href="http://lists.buildroot.org/pipermail/buildroot/2012-November/061558.html">available</a>. Many thanks to all the participants, and a special thanks to Arnout Vandecappelle from <a href="http://mind.be/">mind</a> for taking notes and Thomas Petazzoni from <a href="http://free-electrons.com/">Free Electrons</a> for handling all the practical arrangements, and naturally our sponsors, <a href="http://www.fluendo.com/">Fluendo</a> and <a href="http://www.synopsys.com/">Synopsis</a>. </p> <p>The next Developer Days will take place on February 4th and 5th in Brussels, Belgium, right after <a href="http://fosdem.org">FOSDEM</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 August 2012</small></p> </div> <div class="timeline-body"> <p>The stable 2012.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.08">CHANGES</a> file for more details and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.08.tar.bz2">2012.08 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.08-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>25 August 2012</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Various fixes, and addition of licensing informations on many packages. See <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.08_rc3">CHANGES</a> file for details</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.08-rc3.tar.bz2">2012.08-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>15 August 2012</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Various fixes, and addition of licensing informations on many packages. See <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.08_rc2">CHANGES</a> file for details</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.08-rc2.tar.bz2">2012.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 August 2012</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.08_rc1">CHANGES</a> file for details</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.08-rc1.tar.bz2">2012.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot Developer Day</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>22 July 2012</small></p> </div> <div class="timeline-body"> <p>The next <i>Buildroot Developer Day</i> meeting will take place on Saturday November 3th and Sunday November 4th 2012 in Barcelona, Spain, just before the <a href="https://events.linuxfoundation.org/events/embedded-linux-conference-europe">Embedded Linux Conference Europe</a> (November 5th-7th). This two days meeting is mainly opened to Buildroot developers and contributors, or Buildroot users having a prior experience with the tool. This meeting will allow developers to work and Buildroot, and discuss current issues, the future directions, and more.</p> <p>For more details, see the <a href="http://elinux.org/Buildroot#Buildroot_Developers_Meeting.2C_3-4_November_2012.2C_Barcelona_Spain">wiki page</a> dedicated to the meeting.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 May 2012</small></p> </div> <div class="timeline-body"> <p>The stable 2012.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.05">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2012-May/054342.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.05.tar.bz2">2012.05 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>25 May 2012</small></p> </div> <div class="timeline-body"> <p>RC3 is out with more bugfixes - See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.05_rc3">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.05-rc3.tar.bz2">2012.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 May 2012</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.05_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.05-rc2.tar.bz2">2012.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>10 May 2012</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.05_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2012-May/053736.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.05-rc1.tar.bz2">2012.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Autobuilder Results Online</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>20 April 2012</small></p> </div> <div class="timeline-body"> <p>The status of the autobuilders, which do repeated <code>randpackageconfig</code> builds for continuous integration testing, is now online at <a href='http://autobuild.buildroot.org'>autobuild.buildroot.org</a>. The code behind it can be found in <a href='http://git.buildroot.net/buildroot-test/'>git</a>.</p> <p>Thanks to Thomas Petazzoni for running the web interface, and to <a href='http://gcc.gnu.org/wiki/CompileFarm'>The GCC Compile Farm</a> and <a href='http://free-electrons.com/'>Free Electrons</a> for hosting builders. Thomas also sends out a daily summary of the build status to the mailing list.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>29 February 2012</small></p> </div> <div class="timeline-body"> <p>The stable 2012.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.02">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2012-February/050752.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.02.tar.bz2">2012.02 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.02-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>27 February 2012</small></p> </div> <div class="timeline-body"> <p>RC3 is out with more bugfixes - See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.02_rc3">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.02-rc3.tar.bz2">2012.02-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>19 February 2012</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with more cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.02_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.02-rc2.tar.bz2">2012.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2012.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>12 February 2012</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.02_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2012-February/050234.html">announcement</a>.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2012.02-rc1.tar.bz2">2012.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot Developer Day</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 January 2012</small></p> </div> <div class="timeline-body"> <p>Another <i>Buildroot Developer Day</i> will take place on Friday, February 3rd in Brussels, Belgium - The day before <a href="http://fosdem.org">FOSDEM</a>. See the <a href="http://lists.buildroot.org/pipermail/buildroot/2012-January/049340.html">announcement</a> or the <a href="http://free-electrons.com/blog/bdd-2012-brussels/">Free Electrons blog</a> for more info.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 November 2011</small></p> </div> <div class="timeline-body"> <p>The stable 2011.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.11">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-November/047926.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.11.tar.bz2">2011.11 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.11-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 November 2011</small></p> </div> <div class="timeline-body"> <p>RC3 is out with more bugfixes - See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.11_rc3">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.11-rc3.tar.bz2">2011.11-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 November 2011</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with a bunch of cleanups and build fixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.11_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.11-rc2.tar.bz2">2011.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>11 November 2011</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.11_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-November/047395.html">announcement</a> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.11-rc1.tar.bz2">2011.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 August 2011</small></p> </div> <div class="timeline-body"> <p>The stable 2011.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.08">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.08.tar.bz2">2011.08 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>29 August 2011</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more bugfixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.08_rc2">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-August/045211.html">announcement</a>. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.08-rc2.tar.bz2">2011.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>4 August 2011</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.08_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-August/044855.html">announcement</a>. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.08-rc1.tar.bz2">2011.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>27 May 2011</small></p> </div> <div class="timeline-body"> <p>The stable 2011.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.05">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.05.tar.bz2">2011.05 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>24 May 2011</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more bugfixes. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.05_rc2">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.05-rc2.tar.bz2">2011.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>18 May 2011</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.05_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-May/043317.html">announcement</a>. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.05-rc1.tar.bz2">2011.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>28 February 2011</small></p> </div> <div class="timeline-body"> <p>The stable 2011.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.02">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-February/041662.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.02.tar.bz2">2011.02 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>24 February 2011</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.02_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.02-rc2.tar.bz2">2011.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2011.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>14 February 2011</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2011.02_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2011-February/041365.html">announcement</a>. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2011.02-rc1.tar.bz2">2011.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 November 2010</small></p> </div> <div class="timeline-body"> <p>The stable 2010.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.11">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2010-November/039135.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.11.tar.bz2">2010.11 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>25 November 2010</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.11_rc2">CHANGES</a> file for details.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.11-rc2.tar.bz2">2010.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>8 November 2010</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.11_rc1">CHANGES</a> file for details, and read the <a href="http://lists.buildroot.org/pipermail/buildroot/2010-November/038645.html">announcement</a>. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.11-rc1.tar.bz2">2010.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot Developer Day</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>28 September 2010</small></p> </div> <div class="timeline-body"> <p>A <i>Buildroot Developer Day</i> will take place on Friday, October 29th in Cambridge, UK - Just the day after the <a href="http://www.embeddedlinuxconference.com/elc_europe10/">Embedded Linux Conference Europe</a>. This <i>Developer Day</i> aims at allowing Buildroot developers to meet and exchange ideas on the project and its future. See the <a href="http://lists.buildroot.org/pipermail/buildroot/2010-September/037930.html">announcement</a> for more info.</p> <p>Thanks to Thomas Petazzoni for taking care of the practical arrangements.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 August 2010</small></p> </div> <div class="timeline-body"> <p>The stable 2010.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.08">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2010-August/037078.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.08.tar.bz2">2010.08 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 August 2010</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.08_rc2">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.08-rc2.tar.bz2">2010.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> This is very much expected to be the final release candidate, so give it a good test and expect a final 2010.08 release before September unless critical issues are found.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 July 2010</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.08_rc1">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.08-rc1.tar.bz2">2010.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>30 May 2010</small></p> </div> <div class="timeline-body"> <p>The stable 2010.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.05">CHANGES</a> file for more details, read the <a href="http://lists.buildroot.org/pipermail/buildroot/2010-May/034878.html">announcement</a> and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.05.tar.bz2">2010.05 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>27 May 2010</small></p> </div> <div class="timeline-body"> <p>RC3 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.05_rc3">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.05-rc3.tar.bz2">2010.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>11 May 2010</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with a bunch of cleanups and build fixes.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.05-rc2.tar.bz2">2010.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>3 May 2010</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.05_rc1">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.05-rc1.tar.bz2">2010.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">FOSDEM slides online</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>2 May 2010</small></p> </div> <div class="timeline-body"> <p>The slides from the <a href="http://fosdem.org/2010/schedule/events/emb_cross_build">Cross Build Systems: Present & Future</a> session at <a href="http://fosdem.org/2010">FOSDEM</a> are now <a href="http://send-patches.org/news/20100211-1-FOSDEM-Crossdev-Workshop.pdf">online</a>. </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 February 2010</small></p> </div> <div class="timeline-body"> <p>The stable 2010.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.02">CHANGES</a> file for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.02.tar.bz2">2010.02 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>23 February 2010</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.02_rc2">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.02-rc2.tar.bz2">2010.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2010.02-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>9 February 2010</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.02_rc1">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2010.02-rc1.tar.bz2">2010.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.11 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 December 2009</small></p> </div> <div class="timeline-body"> <p>The stable 2009.11 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://lists.buildroot.org/pipermail/buildroot/2009-December/030672.html">announcement</a> or <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.11">CHANGES</a> for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.11.tar.bz2">2009.11 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.11-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>29 November 2009</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.11_rc2">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.11-rc2.tar.bz2">2009.11-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.11-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>23 November 2009</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.11_rc1">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.11-rc1.tar.bz2">2009.11-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">First Buildroot Developer Day</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>7 September 2009</small></p> </div> <div class="timeline-body"> <p>The first <i>Buildroot Developer Day</i> will take place on Saturday, October 17th in Grenoble, France, just the day after Embedded Linux Conference Europe. This <i>Developer Day</i> aims at allowing Buildroot developers to meet and exchange ideas on the project and its future.</p> <p>As the number of places is limited, interested candidates are invited to send an e-mail to Peter Korsgaard (<code>jacmet at uclibc dot org</code>) and Thomas Petazzoni (<code>thomas dot petazzoni at free-electrons dot com</code>).</p> <p>This <i>Developer Day</i> will take place thanks to the sponsoring of <a href="http://www.calao-systems.com">Calao Systems</a> and <a href="http://www.free-electrons.com">Free Electrons</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.08 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 August 2009</small></p> </div> <div class="timeline-body"> <p>The stable 2009.08 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://lists.buildroot.org/pipermail/buildroot/2009-August/029018.html">announcement</a> or <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.08">CHANGES</a> for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.08.tar.bz2">2009.08 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.08-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>26 August 2009</small></p> </div> <div class="timeline-body"> <p>A number of bugfixes have been added to the tree since RC2 (especially thanks to Thomas Petazzoni) - See the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.08_rc3">CHANGES</a> file for details. This is very much expected to be the final release candidate, so give it a good test and expect a final 2009.08 release next weekend unless critical issues are found.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.08-rc3.tar.bz2">2009.08-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.08-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>6 August 2009</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bugfixes, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.08_rc2">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.08-rc2.tar.bz2">2009.08-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.08-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>2 August 2009</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.08_rc1">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.08-rc1.tar.bz2">2009.08-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.05 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>1 June 2009</small></p> </div> <div class="timeline-body"> <p>The stable 2009.05 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://lists.buildroot.org/pipermail/buildroot/2009-June/027640.html">announcement</a> or <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05">CHANGES</a> for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.05.tar.bz2">2009.05 release</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.05-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>27 May 2009</small></p> </div> <div class="timeline-body"> <p>We had a number of fixes post-RC2, so RC3 is out (see <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05_rc3">CHANGES</a> for details). Now is the moment to test and verify that everything is working for your favorite config - Expect a final 2009.05 very soon.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.05-rc3.tar.bz2">2009.05-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.05-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>19 May 2009</small></p> </div> <div class="timeline-body"> <p>RC2 is out with more cleanups and bug fixes (see <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05_rc2">CHANGES</a>). Unless big issues are found, expect this to be the last release candidate before the release - So give it a good test.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.05-rc2.tar.bz2">2009.05-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot.org</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>14 May 2009</small></p> </div> <div class="timeline-body"> <p>Earl Levine has been so kind to donate the <b>buildroot.org</b> domain to us, so the website can now also be reached at <a href="http://www.buildroot.org">www.buildroot.org</a> (and git at <a href="http://git.buildroot.org/buildroot">git.buildroot.org</a>). Thanks a lot Earl!</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.05-rc1 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>5 May 2009</small></p> </div> <div class="timeline-body"> <p>We have a new release candidate! Lots of changes all over the tree, see the <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05_rc1">CHANGES</a> file for details. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.05-rc1.tar.bz2">2009.05-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Moved to git</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>3 May 2009</small></p> </div> <div class="timeline-body"> <p>We've moved the source code from <a href="http://subversion.tigris.org">Subversion</a> to <a href="http://git-scm.org">Git</a>. You can browse the repo online <a href="http://git.buildroot.net/buildroot">here</a>, and clone the repo using: <pre>git clone git://git.buildroot.net/buildroot</pre> See the <a href="/git.html">Git Access</a> page for more details. </p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title"><new Logo/h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>27 March 2009</small></p> </div> <div class="timeline-body"> <p>We have a <a href="images/logo.png">logo</a>! We have so far been using the <a href="http://busybox.net">Busybox</a> logo on the website, as the website was a copy of the <a href="http://busybox.net">Busybox</a> one - But not anymore, we now have a shiny new logo of our own.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.02 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>12 February 2009</small></p> </div> <div class="timeline-body"> <p>The stable 2009.02 release is out - Thanks to everyone contributing and testing the release candidates. See the <a href="http://lists.buildroot.org/pipermail/buildroot/2009-February/025974.html">announcement</a> for more details, and go to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.02.tar.bz2">2009.02 release</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.02-rc4 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>9 February 2009</small></p> </div> <div class="timeline-body"> <p>We had more than 50 changes since RC3, several of them toolchain related, so decided to make a RC4 as well. This is very much expected to be the final release candidate, so give it a good test and expect a final 2009.02 release this week unless critical issues are found.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.02-rc4.tar.bz2">2009.02-rc4 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.02-rc3 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>31 January 2009</small></p> </div> <div class="timeline-body"> <p>RC3 is out with more cleanups and bug fixes. Unless big issues are found, expect this to be the last release candidate before the release - So give it a good test.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.02-rc3.tar.bz2">2009.02-rc3 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">2009.02-rc2 released</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>23 January 2009</small></p> </div> <div class="timeline-body"> <p>Another week, another release candidate with a bunch of cleanups and build fixes.</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.02-rc2.tar.bz2">2009.02-rc2 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Release candidate and new maintainer</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>16 January 2009</small></p> </div> <div class="timeline-body"> <p>It has been a long time coming, but we finally have a new release candidate! - And a new maintainer to match (Peter Korsgaard).</p> <p>Head to the <a href="/downloads/">downloads page</a> to pick up the <a href="/downloads/buildroot-2009.02-rc1.tar.bz2">2009.02-rc1 release candidate</a>, and report any problems found to the <a href="support.html">mailing list</a> or <a href="https://bugs.uclibc.org">bug tracker</a>. The plan is to release 2009.02 in time for <a href="http://www.fosdem.org/2009/">FOSDEM</a>.</p> </div> </div> </li> <li> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot mailing list</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>16 July 2006</small></p> </div> <div class="timeline-body"> <p>Buildroot now has its own <a href=support.html>mailing list</a>.</p> </div> </div> </li> <li class="timeline-inverted"> <div class="timeline-badge"><i class="glyphicon glyphicon-thumbs-up"></i></div> <div class="timeline-panel"> <div class="timeline-heading"> <h4 class="timeline-title">Buildroot webpage added</h4> <p><small class="text-muted"><i class="glyphicon glyphicon-time"></i>21 February 2005</small></p> <p>Buildroot is a set of Makefiles and patches that makes it easy generate a cross-compilation toolchain and root filesystem for your target Linux system using the <a href= "http://www.uclibc.org/">uClibc C library</a>. Buildroot is useful mainly for people working with small or embedded systems. Embedded systems often use processors that are not the regular x86 processors everyone is used to using on their PC. It can be PowerPC processors, MIPS processors, ARM processors, etc. And to be extra safe, you do not need to be root to build or run buildroot.</p> <p>And as of today buildroot even has its own webpage, making it a first class citizen of uclibc.org and busybox.net, and more importantly, make it easy to find and point to buildroot.</p> <p>If you find a bug in buildroot, or wish to submit a patch to fix a problem or add a shiny new feature, please use the <a href="https://bugs.uclibc.org/">Bug and Patch Tracking System</a> to post the details, to make certain your work is not lost</p> </div> </div> </li> </ul> </div><!--/.col-sm-10 --> </div><!--/.row --> </div> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/news.html
HTML
mit
131,183
User-agent: * Disallow: /cgi-bin/
shibajee/buildroot
docs/website/robots.txt
Text
mit
34
<!--#include file="header.html" --> <div class="container"> <div class="row nh"><!-- current sponsor row --> <div class="col-lg-10 col-lg-offset-1 col-md-12 col-sm-12 col-xs-12"> <div class="panel panel-primary"> <div class="panel-heading">Current sponsors</div> <div class="panel-body"> <div class="row"> <div class="col-sm-12"> <div class="panel panel-default"> <div class="panel-body"> <div class="col-sm-4"> <a href="http://ingenierie.openwide.fr"> <img class="img-responsive center-block" src="images/owi-smile-logo.png"/> </a> </div> <div class="col-sm-8"> <a href="http://ingenierie.openwide.fr">OpenWide/Smile</a> is sponsoring the Buildroot Summer Camp taking place on July 1-5 2016 in Toulouse, France. OpenWide/Smile is sponsoring the participation of Romain Naour and paid the food expenses for the meeting participants. </div> </div> </div> </div> </div> </div> </div> <div class="panel panel-primary"> <div class="panel-heading">Past sponsors</div> <div class="panel-body"> <p>Throughout its history, the Buildroot project has been sponsored by various companies, that we would like to thank below.</p> <div class="row"> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <a href="http://www.mind.be"> <img class="img-responsive center-block" src="images/mind-logo.png"/> </a> </div> <div class="col-sm-12"> <a href="http://www.mind.be">Mind</a> sponsored the dinner of the FOSDEM 2014, 2015 and 2016 Developers Meeting (Brussels), the meeting room and the dinner for the ELCE 2014 Developers Meeting (Düsseldorf). </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://www.google.com"> <img class="img-responsive center-block" src="images/google-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://www.google.com">Google</a> provided the logistics for the FOSDEM 2013, FOSDEM 2014, FOSDEM 2015 and FOSDEM 2016 Developer Days in Brussels, Belgium.</p> </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://www.imgtec.com/"> <img class="img-responsive center-block" src="images/imgtec-logo.png"/></a></p> </div> <div class="col-sm-12"> <a href="http://www.imgtec.com/">Imagination Technologies</a> sponsored the meeting room and dinner of the ELCE 2013 Developer Days in Edinburgh, UK. </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://circuitco.com/"> <img class="img-responsive center-block" src="images/circuitco-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://circuitco.com/">CircuitCo</a> sponsored several development boards for the Google Summer of Code 2013 project on Buildroot.</p> </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://boundarydevices.com/"> <img class="img-responsive center-block" src="images/boundary-devices-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://boundarydevices.com/">BoundaryDevices</a> sponsored an i.MX6 development board for the Google Summer of Code 2013 project on Buildroot.</p> </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://www.fluendo.com/"> <img class="img-responsive center-block" src="images/fluendo-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://www.fluendo.com/">Fluendo</a> sponsored the meeting room for the ELCE 2012 Developer Days in Barcelona Spain.</p> </div> </div> </div> </div> </div> <div class="row"> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://www.synopsys.com"> <img class="img-responsive center-block" src="images/synopsys-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://www.synopsys.com">Synopsys</a> sponsored the dinner for the ELCE 2012 Developer Days in Barcelona, Spain.</p> </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://www.calao-systems.com/"> <img class="img-responsive center-block" src="images/calao-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://www.calao-systems.com/">Calao Systems</a> provided a a meeting room for the ELCE 2009 Developer Days in Grenoble, France.</p> </div> </div> </div> </div> <div class="col-sm-4"> <div class="panel panel-default panel-sponsor"> <div class="panel-body"> <div class="col-sm-12"> <p><a href="http://www.free-electrons.com"> <img class="img-responsive center-block" src="images/free-electrons-logo.png"/></a></p> </div> <div class="col-sm-12"> <p><a href="http://www.free-electrons.com">Free Electrons</a> sponsored the lunch for the ELCE 2009 Developer Days in Grenoble, France.</p> </div> </div> </div> </div> </div> </div> </div> </div> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/sponsors.html
HTML
mit
6,058
<!--#include file="header.html" --> <div class="container"> <div class="row nh"> <div class="col-lg-10 col-lg-offset-1 col-md-12 col-sm-12 col-xs-12"> <div class="panel panel-primary"> <div class="panel-heading">Support</div> <div class="panel-body"> <p>You can get support for Buildroot through three main channels:</p> <div class="row"> <div class="col-sm-12"> <div class="panel panel-primary"> <div class="panel-heading">IRC</div> <div class="panel-body"> <div class="row"> <div class="col-sm-1"> <img class="img-responsive" src="images/irc.png" style="max-width:50px; margin-bottom:10px;"> </div> <div class="col-sm-11"> <p>The Buildroot IRC channel is <a href="irc://freenode.net/#buildroot"> #buildroot</a>, hosted on Freenode. If you do not have an IRC client, you can use the <a href="http://webchat.freenode.net">Freenode web interface</a>. When asking for help on IRC, share relevant logs or pieces of code using a code sharing website.</p> </div> </div> </div> </div> </div> <div class="col-sm-12"> <div class="panel panel-primary"> <div class="panel-heading">Mailing List Information</div> <div class="panel-body"> <div class="row"> <div class="col-sm-1"> <img class="img-responsive" src="images/email.png" style="max-width:50px; margin-bottom:10px;"> </div> <div class="col-sm-11"> <p>The <a href="/lists/buildroot/">mailing list</a> is for discussion and development. You can subscribe by visiting <a href="http://lists.buildroot.org/mailman/listinfo/buildroot">this page</a>. Only subscribers to the Buildroot mailing list are allowed to post to this list.</p> <h4>Search the List Archives</h4> <p>Please search the mailing list archives before asking questions on the mailing list, since there is a good chance someone else has asked the same question before.</p> <form method="get" action="http://search.gmane.org/"> <input type="text" name="query"> <input type="hidden" name="group" value="gmane.comp.lib.uclibc.buildroot"> <button type="submit" class="btn btn-default">Submit</button> </form> </div> </div> </div> </div> </div> <div class="col-sm-12"> <div class="panel panel-primary"> <div class="panel-heading">Bug Tracker</div> <div class="panel-body"> <div class="row"> <div class="col-sm-1"> <img class="img-responsive" src="images/bug-buddy.png" style="max-width:50px; margin-bottom:10px;"> </div> <div class="col-sm-11"> <p>If you encounter any problem while using Buildroot, you can use the <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or participate to find solutions to existing problems.</p> <p>Note: patches are only accepted through the mailing list.</p> </div> </div> </div> </div> </div> </div> </div> </div> </div><!--/.col-sm-10 --> </div><!--/.row --> </div> <!--#include file="footer.html" -->
shibajee/buildroot
docs/website/support.html
HTML
mit
3,079
menu "Filesystem images" source "fs/axfs/Config.in" source "fs/cloop/Config.in" source "fs/cpio/Config.in" source "fs/cramfs/Config.in" source "fs/ext2/Config.in" source "fs/initramfs/Config.in" source "fs/iso9660/Config.in" source "fs/jffs2/Config.in" source "fs/romfs/Config.in" source "fs/squashfs/Config.in" source "fs/tar/Config.in" source "fs/ubifs/Config.in" source "fs/yaffs2/Config.in" endmenu
shibajee/buildroot
fs/Config.in
in
mit
405
config BR2_TARGET_ROOTFS_AXFS bool "axfs root filesystem" help The Advanced XIP File System is a Linux kernel filesystem driver that enables files to be executed directly from flash or ROM memory rather than being copied into RAM. It has the ability to store individual *pages* in a file uncompressed/XIP or compressed/Demand Paged. So far, the only supported mode is 'XIP all', so all the files that have the execute attribute set will be XIP'ed. At the moment, the FS is not supported in Linux mainline (v4.3-rc5), so the kernel has to be built with the axfs patches to be able to read it. Patches can be found at: https://github.com/jaredeh/axfs
shibajee/buildroot
fs/axfs/Config.in
in
mit
687
################################################################################ # # Build the axfs root filesystem image # ################################################################################ ROOTFS_AXFS_DEPENDENCIES = host-axfsutils define ROOTFS_AXFS_CMD $(HOST_DIR)/usr/bin/mkfs.axfs -s -a $(TARGET_DIR) $@ endef $(eval $(call ROOTFS_TARGET,axfs))
shibajee/buildroot
fs/axfs/axfs.mk
mk
mit
368
config BR2_TARGET_ROOTFS_CLOOP bool "cloop root filesystem for the target device" help Build a cloop root filesystem cloop is a Linux kernel module that enables compressed loopback filesystem support. With it you can mount a compressed filesystem like a block device and seamlessly decompress its data while accessing it. The majority of the software on an LNX-BBC is accessed in this fashion.
shibajee/buildroot
fs/cloop/Config.in
in
mit
416
################################################################################ # # Build the compressed loop root filesystem image # ################################################################################ ROOTFS_CLOOP_DEPENDENCIES = host-cloop host-cdrkit define ROOTFS_CLOOP_CMD $(HOST_DIR)/usr/bin/genisoimage -r $(TARGET_DIR) | \ $(HOST_DIR)/usr/bin/create_compressed_fs - 65536 > $@ endef $(eval $(call ROOTFS_TARGET,cloop))
shibajee/buildroot
fs/cloop/cloop.mk
mk
mit
446
# # Macro that builds the needed Makefile target to create a root # filesystem image. # # The following variable must be defined before calling this macro # # ROOTFS_$(FSTYPE)_CMD, the command that generates the root # filesystem image. A single command is allowed. The filename of the # filesystem image that it must generate is $$@. # # The following variables can optionaly be defined # # ROOTFS_$(FSTYPE)_DEPENDENCIES, the list of dependencies needed to # build the root filesystem (usually host tools) # # ROOTFS_$(FSTYPE)_PRE_GEN_HOOKS, a list of hooks to call before # generating the filesystem image # # ROOTFS_$(FSTYPE)_POST_GEN_HOOKS, a list of hooks to call after # generating the filesystem image # # ROOTFS_$(FSTYPE)_POST_TARGETS, the list of targets that should be # run after running the main filesystem target. This is useful for # initramfs, to rebuild the kernel once the initramfs is generated. # # In terms of configuration option, this macro assumes that the # BR2_TARGET_ROOTFS_$(FSTYPE) config option allows to enable/disable # the generation of a filesystem image of a particular type. If # the configuration options BR2_TARGET_ROOTFS_$(FSTYPE)_GZIP, # BR2_TARGET_ROOTFS_$(FSTYPE)_BZIP2 or # BR2_TARGET_ROOTFS_$(FSTYPE)_LZMA exist and are enabled, then the # macro will automatically generate a compressed filesystem image. FAKEROOT_SCRIPT = $(BUILD_DIR)/_fakeroot.fs FULL_DEVICE_TABLE = $(BUILD_DIR)/_device_table.txt ROOTFS_DEVICE_TABLES = $(call qstrip,$(BR2_ROOTFS_DEVICE_TABLE) \ $(BR2_ROOTFS_STATIC_DEVICE_TABLE)) USERS_TABLE = $(BUILD_DIR)/_users_table.txt ROOTFS_USERS_TABLES = $(call qstrip,$(BR2_ROOTFS_USERS_TABLES)) # Since this function will be called from within an $(eval ...) # all variable references except the arguments must be $$-quoted. define ROOTFS_TARGET_INTERNAL # extra deps ROOTFS_$(2)_DEPENDENCIES += host-fakeroot host-makedevs \ $$(if $$(PACKAGES_USERS)$$(ROOTFS_USERS_TABLES),host-mkpasswd) ifeq ($$(BR2_TARGET_ROOTFS_$(2)_GZIP),y) ROOTFS_$(2)_COMPRESS_EXT = .gz ROOTFS_$(2)_COMPRESS_CMD = gzip -9 -c endif ifeq ($$(BR2_TARGET_ROOTFS_$(2)_BZIP2),y) ROOTFS_$(2)_COMPRESS_EXT = .bz2 ROOTFS_$(2)_COMPRESS_CMD = bzip2 -9 -c endif ifeq ($$(BR2_TARGET_ROOTFS_$(2)_LZMA),y) ROOTFS_$(2)_DEPENDENCIES += host-lzma ROOTFS_$(2)_COMPRESS_EXT = .lzma ROOTFS_$(2)_COMPRESS_CMD = $$(LZMA) -9 -c endif ifeq ($$(BR2_TARGET_ROOTFS_$(2)_LZO),y) ROOTFS_$(2)_DEPENDENCIES += host-lzop ROOTFS_$(2)_COMPRESS_EXT = .lzo ROOTFS_$(2)_COMPRESS_CMD = $$(LZOP) -9 -c endif ifeq ($$(BR2_TARGET_ROOTFS_$(2)_XZ),y) ROOTFS_$(2)_DEPENDENCIES += host-xz ROOTFS_$(2)_COMPRESS_EXT = .xz ROOTFS_$(2)_COMPRESS_CMD = xz -9 -C crc32 -c endif $$(BINARIES_DIR)/rootfs.$(1): target-finalize $$(ROOTFS_$(2)_DEPENDENCIES) @$$(call MESSAGE,"Generating root filesystem image rootfs.$(1)") $$(foreach hook,$$(ROOTFS_$(2)_PRE_GEN_HOOKS),$$(call $$(hook))$$(sep)) rm -f $$(FAKEROOT_SCRIPT) rm -f $$(TARGET_DIR_WARNING_FILE) rm -f $$(USERS_TABLE) echo '#!/bin/sh' > $$(FAKEROOT_SCRIPT) echo "set -e" >> $$(FAKEROOT_SCRIPT) echo "chown -h -R 0:0 $$(TARGET_DIR)" >> $$(FAKEROOT_SCRIPT) ifneq ($$(ROOTFS_USERS_TABLES),) cat $$(ROOTFS_USERS_TABLES) >> $$(USERS_TABLE) endif $$(call PRINTF,$$(PACKAGES_USERS)) >> $$(USERS_TABLE) PATH=$$(BR_PATH) $$(TOPDIR)/support/scripts/mkusers $$(USERS_TABLE) $$(TARGET_DIR) >> $$(FAKEROOT_SCRIPT) ifneq ($$(ROOTFS_DEVICE_TABLES),) cat $$(ROOTFS_DEVICE_TABLES) > $$(FULL_DEVICE_TABLE) ifeq ($$(BR2_ROOTFS_DEVICE_CREATION_STATIC),y) $$(call PRINTF,$$(PACKAGES_DEVICES_TABLE)) >> $$(FULL_DEVICE_TABLE) endif $$(call PRINTF,$$(PACKAGES_PERMISSIONS_TABLE)) >> $$(FULL_DEVICE_TABLE) echo "$$(HOST_DIR)/usr/bin/makedevs -d $$(FULL_DEVICE_TABLE) $$(TARGET_DIR)" >> $$(FAKEROOT_SCRIPT) endif $$(foreach s,$$(call qstrip,$$(BR2_ROOTFS_POST_FAKEROOT_SCRIPT)),\ echo "echo '$$(TERM_BOLD)>>> Executing fakeroot script $$(s)$$(TERM_RESET)'" >> $$(FAKEROOT_SCRIPT); \ echo $$(s) $$(TARGET_DIR) $$(BR2_ROOTFS_POST_SCRIPT_ARGS) >> $$(FAKEROOT_SCRIPT)$$(sep)) $$(call PRINTF,$$(ROOTFS_$(2)_CMD)) >> $$(FAKEROOT_SCRIPT) chmod a+x $$(FAKEROOT_SCRIPT) PATH=$$(BR_PATH) $$(HOST_DIR)/usr/bin/fakeroot -- $$(FAKEROOT_SCRIPT) $$(INSTALL) -m 0644 support/misc/target-dir-warning.txt $$(TARGET_DIR_WARNING_FILE) -@rm -f $$(FAKEROOT_SCRIPT) $$(FULL_DEVICE_TABLE) ifneq ($$(ROOTFS_$(2)_COMPRESS_CMD),) PATH=$$(BR_PATH) $$(ROOTFS_$(2)_COMPRESS_CMD) $$@ > $$@$$(ROOTFS_$(2)_COMPRESS_EXT) endif $$(foreach hook,$$(ROOTFS_$(2)_POST_GEN_HOOKS),$$(call $$(hook))$$(sep)) rootfs-$(1)-show-depends: @echo $$(ROOTFS_$(2)_DEPENDENCIES) rootfs-$(1): $$(BINARIES_DIR)/rootfs.$(1) $$(ROOTFS_$(2)_POST_TARGETS) .PHONY: rootfs-$(1) rootfs-$(1)-show-depends ifeq ($$(BR2_TARGET_ROOTFS_$(2)),y) TARGETS_ROOTFS += rootfs-$(1) PACKAGES += $$(filter-out rootfs-%,$$(ROOTFS_$(2)_DEPENDENCIES)) endif endef define ROOTFS_TARGET $(call ROOTFS_TARGET_INTERNAL,$(1),$(call UPPERCASE,$(1))) endef include $(sort $(wildcard fs/*/*.mk))
shibajee/buildroot
fs/common.mk
mk
mit
4,972
config BR2_TARGET_ROOTFS_CPIO bool "cpio the root filesystem (for use as an initial RAM filesystem)" help Build a cpio archive of the root filesystem. This is typically used for an initial RAM filesystem that is passed to the kernel by the bootloader. if BR2_TARGET_ROOTFS_CPIO choice prompt "Compression method" default BR2_TARGET_ROOTFS_CPIO_NONE help Select compressor for cpio filesystem of the root filesystem. If you use the cpio archive as an initial RAM filesystem, make sure the kernel contains the decompression algorithm selected here. config BR2_TARGET_ROOTFS_CPIO_NONE bool "no compression" help Do not compress the cpio filesystem. config BR2_TARGET_ROOTFS_CPIO_GZIP bool "gzip" help Do compress the cpio filesystem with gzip. config BR2_TARGET_ROOTFS_CPIO_BZIP2 bool "bzip2" help Do compress the cpio filesystem with bzip2. config BR2_TARGET_ROOTFS_CPIO_LZMA bool "lzma" help Do compress the cpio filesystem with lzma. config BR2_TARGET_ROOTFS_CPIO_LZO bool "lzo" help Do compress the cpio filesystem with lzop. config BR2_TARGET_ROOTFS_CPIO_XZ bool "xz" help Do compress the cpio filesystem with xz. endchoice config BR2_TARGET_ROOTFS_CPIO_UIMAGE bool "Create U-Boot image of the root filesystem" select BR2_PACKAGE_HOST_UBOOT_TOOLS help Add a U-Boot header to the cpio root filesystem. This allows the initramfs to be loaded with the bootm command in U-Boot. The U-Boot image will be called rootfs.cpio.uboot endif # BR2_TARGET_ROOTFS_CPIO
shibajee/buildroot
fs/cpio/Config.in
in
mit
1,538
################################################################################ # # cpio to archive target filesystem # ################################################################################ ifeq ($(BR2_ROOTFS_DEVICE_CREATION_STATIC),y) define ROOTFS_CPIO_ADD_INIT if [ ! -e $(TARGET_DIR)/init ]; then \ ln -sf sbin/init $(TARGET_DIR)/init; \ fi endef else # devtmpfs does not get automounted when initramfs is used. # Add a pre-init script to mount it before running init define ROOTFS_CPIO_ADD_INIT if [ ! -e $(TARGET_DIR)/init ]; then \ $(INSTALL) -m 0755 fs/cpio/init $(TARGET_DIR)/init; \ fi endef PACKAGES_PERMISSIONS_TABLE += /dev/console c 622 0 0 5 1 - - -$(sep) endif # BR2_ROOTFS_DEVICE_CREATION_STATIC ROOTFS_CPIO_PRE_GEN_HOOKS += ROOTFS_CPIO_ADD_INIT define ROOTFS_CPIO_CMD cd $(TARGET_DIR) && find . | cpio --quiet -o -H newc > $@ endef $(BINARIES_DIR)/rootfs.cpio.uboot: $(BINARIES_DIR)/rootfs.cpio host-uboot-tools $(MKIMAGE) -A $(MKIMAGE_ARCH) -T ramdisk \ -C none -d $<$(ROOTFS_CPIO_COMPRESS_EXT) $@ ifeq ($(BR2_TARGET_ROOTFS_CPIO_UIMAGE),y) ROOTFS_CPIO_POST_TARGETS += $(BINARIES_DIR)/rootfs.cpio.uboot endif $(eval $(call ROOTFS_TARGET,cpio))
shibajee/buildroot
fs/cpio/cpio.mk
mk
mit
1,196
#!/bin/sh # devtmpfs does not get automounted for initramfs /bin/mount -t devtmpfs devtmpfs /dev exec 0</dev/console exec 1>/dev/console exec 2>/dev/console exec /sbin/init $*
shibajee/buildroot
fs/cpio/init
none
mit
176
config BR2_TARGET_ROOTFS_CRAMFS bool "cramfs root filesystem" help Build a cramfs root filesystem http://sourceforge.net/projects/cramfs/
shibajee/buildroot
fs/cramfs/Config.in
in
mit
147
################################################################################ # # Build the cramfs root filesystem image # ################################################################################ ifeq ($(BR2_ENDIAN),"BIG") CRAMFS_OPTS = -b else CRAMFS_OPTS = -l endif define ROOTFS_CRAMFS_CMD $(HOST_DIR)/usr/bin/mkcramfs $(CRAMFS_OPTS) $(TARGET_DIR) $@ endef ROOTFS_CRAMFS_DEPENDENCIES = host-cramfs $(eval $(call ROOTFS_TARGET,cramfs))
shibajee/buildroot
fs/cramfs/cramfs.mk
mk
mit
454
config BR2_TARGET_ROOTFS_EXT2 bool "ext2/3/4 root filesystem" select BR2_PACKAGE_HOST_MKE2IMG help Build an ext2/3/4 root filesystem if BR2_TARGET_ROOTFS_EXT2 config BR2_TARGET_ROOTFS_EXT2_2 bool choice bool "ext2/3/4 variant" default BR2_TARGET_ROOTFS_EXT2_2r0 config BR2_TARGET_ROOTFS_EXT2_2r0 bool "ext2 (rev0)" select BR2_TARGET_ROOTFS_EXT2_2 config BR2_TARGET_ROOTFS_EXT2_2r1 bool "ext2 (rev1)" select BR2_TARGET_ROOTFS_EXT2_2 config BR2_TARGET_ROOTFS_EXT2_3 bool "ext3" config BR2_TARGET_ROOTFS_EXT2_4 bool "ext4" endchoice config BR2_TARGET_ROOTFS_EXT2_GEN int default 2 if BR2_TARGET_ROOTFS_EXT2_2 default 3 if BR2_TARGET_ROOTFS_EXT2_3 default 4 if BR2_TARGET_ROOTFS_EXT2_4 # All ext generations are revision 1, except ext2r0, which is revision 0 config BR2_TARGET_ROOTFS_EXT2_REV int default 0 if BR2_TARGET_ROOTFS_EXT2_2r0 default 1 if !BR2_TARGET_ROOTFS_EXT2_2r0 config BR2_TARGET_ROOTFS_EXT2_LABEL string "filesystem label" config BR2_TARGET_ROOTFS_EXT2_BLOCKS int "exact size in blocks (leave at 0 for auto calculation)" default 0 config BR2_TARGET_ROOTFS_EXT2_INODES int "exact number of inodes (leave at 0 for auto calculation)" default 0 config BR2_TARGET_ROOTFS_EXT2_EXTRA_BLOCKS int "extra size in blocks" if BR2_TARGET_ROOTFS_EXT2_BLOCKS = 0 default 0 help Enter here the number of extra blocks of free space you want on your filesystem. By default, Buildroot will not leave much space free. config BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES int "extra inodes" if BR2_TARGET_ROOTFS_EXT2_INODES = 0 default 0 help Enter here the number of extra free inodes you want on your filesystem. By default, Buildroot will not leave many free inodes. config BR2_TARGET_ROOTFS_EXT2_RESBLKS int "reserved blocks percentage" default 0 choice prompt "Compression method" default BR2_TARGET_ROOTFS_EXT2_NONE help Select compressor for ext2/3/4 filesystem of the root filesystem config BR2_TARGET_ROOTFS_EXT2_NONE bool "no compression" help Do not compress the ext2/3/4 filesystem. config BR2_TARGET_ROOTFS_EXT2_GZIP bool "gzip" help Do compress the ext2/3/4 filesystem with gzip. config BR2_TARGET_ROOTFS_EXT2_BZIP2 bool "bzip2" help Do compress the ext2/3/4 filesystem with bzip2. config BR2_TARGET_ROOTFS_EXT2_LZMA bool "lzma" help Do compress the ext2/3/4 filesystem with lzma. config BR2_TARGET_ROOTFS_EXT2_LZO bool "lzo" help Do compress the ext2 filesystem with lzop. config BR2_TARGET_ROOTFS_EXT2_XZ bool "xz" help Do compress the ext2 filesystem with xz. endchoice endif # BR2_TARGET_ROOTFS_EXT2
shibajee/buildroot
fs/ext2/Config.in
in
mit
2,618
################################################################################ # # Build the ext2 root filesystem image # ################################################################################ EXT2_OPTS = -G $(BR2_TARGET_ROOTFS_EXT2_GEN) -R $(BR2_TARGET_ROOTFS_EXT2_REV) ifneq ($(strip $(BR2_TARGET_ROOTFS_EXT2_BLOCKS)),0) EXT2_OPTS += -b $(BR2_TARGET_ROOTFS_EXT2_BLOCKS) endif EXT2_OPTS += -B $(BR2_TARGET_ROOTFS_EXT2_EXTRA_BLOCKS) ifneq ($(strip $(BR2_TARGET_ROOTFS_EXT2_INODES)),0) EXT2_OPTS += -i $(BR2_TARGET_ROOTFS_EXT2_INODES) endif EXT2_OPTS += -I $(BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES) ifneq ($(strip $(BR2_TARGET_ROOTFS_EXT2_RESBLKS)),0) EXT2_OPTS += -r $(BR2_TARGET_ROOTFS_EXT2_RESBLKS) endif # Not qstrip-ing the variable, because it may contain spaces, but we must # qstrip it when checking. Furthermore, we need to further quote it, so # that the quotes do not get eaten by the echo statement when creating the # fakeroot script ifneq ($(call qstrip,$(BR2_TARGET_ROOTFS_EXT2_LABEL)),) EXT2_OPTS += -l '$(BR2_TARGET_ROOTFS_EXT2_LABEL)' endif ROOTFS_EXT2_DEPENDENCIES = host-mke2img define ROOTFS_EXT2_CMD PATH=$(BR_PATH) mke2img -d $(TARGET_DIR) $(EXT2_OPTS) -o $@ endef rootfs-ext2-symlink: ln -sf rootfs.ext2$(ROOTFS_EXT2_COMPRESS_EXT) $(BINARIES_DIR)/rootfs.ext$(BR2_TARGET_ROOTFS_EXT2_GEN)$(ROOTFS_EXT2_COMPRESS_EXT) .PHONY: rootfs-ext2-symlink ifneq ($(BR2_TARGET_ROOTFS_EXT2_GEN),2) ROOTFS_EXT2_POST_TARGETS += rootfs-ext2-symlink endif $(eval $(call ROOTFS_TARGET,ext2))
shibajee/buildroot
fs/ext2/ext2.mk
mk
mit
1,516
config BR2_TARGET_ROOTFS_INITRAMFS bool "initial RAM filesystem linked into linux kernel" depends on BR2_LINUX_KERNEL select BR2_TARGET_ROOTFS_CPIO help Integrate the root filesystem generated by Buildroot as an initramfs inside the kernel image. This integration will take place automatically. A rootfs.cpio file will be generated in the images/ directory. This is the archive that will be included in the kernel image. The default rootfs compression set in the kernel configuration is used, regardless of how buildroot's cpio archive is configured. Note that enabling initramfs together with another filesystem formats doesn't make sense: you would end up having two identical root filesystems, one embedded inside the kernel image, and one separately. comment "initramfs needs a Linux kernel to be built" depends on !BR2_LINUX_KERNEL
shibajee/buildroot
fs/initramfs/Config.in
in
mit
878
################################################################################ # # Build a kernel with an integrated initial ramdisk # filesystem based on cpio. # ################################################################################ ROOTFS_INITRAMFS_DEPENDENCIES += rootfs-cpio ROOTFS_INITRAMFS_POST_TARGETS += linux-rebuild-with-initramfs # The generic fs infrastructure isn't very useful here. rootfs-initramfs: $(ROOTFS_INITRAMFS_DEPENDENCIES) $(ROOTFS_INITRAMFS_POST_TARGETS) rootfs-initramfs-show-depends: @echo $(ROOTFS_INITRAMFS_DEPENDENCIES) .PHONY: rootfs-initramfs rootfs-initramfs-show-depends ifeq ($(BR2_TARGET_ROOTFS_INITRAMFS),y) TARGETS_ROOTFS += rootfs-initramfs endif
shibajee/buildroot
fs/initramfs/initramfs.mk
mk
mit
708
config BR2_TARGET_ROOTFS_ISO9660 bool "iso image" depends on (BR2_i386 || BR2_x86_64) depends on BR2_LINUX_KERNEL depends on BR2_TARGET_GRUB || \ BR2_TARGET_GRUB2 || \ BR2_TARGET_SYSLINUX_ISOLINUX select BR2_LINUX_KERNEL_INSTALL_TARGET \ if (!BR2_TARGET_ROOTFS_ISO9660_INITRD && !BR2_TARGET_ROOTFS_INITRAMFS) help Build a bootable ISO9660 image. By default, the root filesystem is directly packed as the ISO9660 filesystem, which means the root filesystem will be read-only. It requires ISO9660 filesystem support and CDROM support in the kernel. However, if BR2_TARGET_ROOTFS_INITRAMFS or BR2_TARGET_ROOTFS_ISO9660_INITRD have been enabled, the ISO9660 filesystem will only contain a kernel image and optionally an external initrd image. In this case, the filesystem being in RAM, it will be read/write. No ISO9660 or CDROM support is needed in the kernel. if BR2_TARGET_ROOTFS_ISO9660 choice prompt "Bootloader" config BR2_TARGET_ROOTFS_ISO9660_GRUB bool "grub" depends on BR2_TARGET_GRUB select BR2_TARGET_GRUB_FS_ISO9660 config BR2_TARGET_ROOTFS_ISO9660_GRUB2 bool "grub2" depends on BR2_TARGET_GRUB2 help Use Grub 2 as the bootloader for the ISO9660 image. Make sure to enable the 'iso9660' module in BR2_TARGET_GRUB2_BUILTIN_MODULES and to use 'cd' as the boot partition in BR2_TARGET_GRUB2_BOOT_PARTITION=. config BR2_TARGET_ROOTFS_ISO9660_ISOLINUX bool "isolinux" depends on BR2_TARGET_SYSLINUX_ISOLINUX endchoice config BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU string "Boot menu config file" default "fs/iso9660/menu.lst" if BR2_TARGET_ROOTFS_ISO9660_GRUB default "fs/iso9660/grub.cfg" if BR2_TARGET_ROOTFS_ISO9660_GRUB2 default "fs/iso9660/isolinux.cfg" if BR2_TARGET_ROOTFS_ISO9660_ISOLINUX help Use this option to provide a custom bootloader configuration file (menu.lst for Grub, grub.cfg for Grub 2, isolinux.cfg for isolinux). Note that the strings __KERNEL_PATH__ and __INITRD_PATH__ will automatically be replaced by the path to the kernel and initrd images respectively. config BR2_TARGET_ROOTFS_ISO9660_INITRD bool "Use initrd" default y select BR2_TARGET_ROOTFS_CPIO help Enable this option to have the root filesystem bundled as an initrd/initramfs rather than directly as the ISO9660 filesystem. With this option enabled, the ISO9660 will only contain a kernel image, an initrd image (unless an initramfs linked into the kernel is used) and the bootloader. config BR2_TARGET_ROOTFS_ISO9660_HYBRID bool "Build hybrid image" depends on BR2_TARGET_ROOTFS_ISO9660_ISOLINUX help Enable this option to build an hybrid image, i.e an image which can either be booted from a CD-ROM or from a device which BIOS considers a hard disk or ZIP disk, e.g. a USB key or similar. endif comment "iso image needs a Linux kernel and one of grub, grub2 or isolinux to be built" depends on BR2_i386 || BR2_x86_64 depends on !BR2_LINUX_KERNEL || \ !(BR2_TARGET_GRUB || BR2_TARGET_GRUB2 || BR2_TARGET_SYSLINUX_ISOLINUX)
shibajee/buildroot
fs/iso9660/Config.in
in
mit
3,059
set default="0" set timeout="10" menuentry "Buildroot" { linux __KERNEL_PATH__ root=/dev/sr0 initrd __INITRD_PATH__ }
shibajee/buildroot
fs/iso9660/grub.cfg
INI
mit
121
################################################################################ # # Build the iso96600 root filesystem image # ################################################################################ # # We need to handle three cases: # # 1. The ISO9660 filesystem will really be the real root filesystem # itself. This is when BR2_TARGET_ROOTFS_ISO9660_INITRD is # disabled. # # 2. The ISO9660 filesystem will be a filesystem with just a kernel # image, initrd and grub. This is when # BR2_TARGET_ROOTFS_ISO9660_INITRD is enabled, but # BR2_TARGET_ROOTFS_INITRAMFS is disabled. # # 3. The ISO9660 filesystem will be a filesystem with just a kernel # image and grub. This is like (2), except that the initrd is # built into the kernel image. This is when # BR2_TARGET_ROOTFS_INITRAMFS is enabled (regardless of the value # of BR2_TARGET_ROOTFS_ISO9660_INITRD). ROOTFS_ISO9660_BOOT_MENU = $(call qstrip,$(BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU)) ROOTFS_ISO9660_DEPENDENCIES = host-cdrkit host-fakeroot linux ifeq ($(BR2_TARGET_ROOTFS_INITRAMFS),y) ROOTFS_ISO9660_USE_INITRD = YES endif ifeq ($(BR2_TARGET_ROOTFS_ISO9660_INITRD),y) ROOTFS_ISO9660_USE_INITRD = YES endif ifeq ($(ROOTFS_ISO9660_USE_INITRD),YES) ROOTFS_ISO9660_TARGET_DIR = $(BUILD_DIR)/rootfs.iso9660.tmp define ROOTFS_ISO9660_CREATE_TEMPDIR $(RM) -rf $(ROOTFS_ISO9660_TARGET_DIR) mkdir -p $(ROOTFS_ISO9660_TARGET_DIR) endef else ROOTFS_ISO9660_TARGET_DIR = $(TARGET_DIR) endif ifeq ($(BR2_TARGET_ROOTFS_ISO9660_GRUB),y) ROOTFS_ISO9660_DEPENDENCIES += grub ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH = \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/grub/menu.lst ROOTFS_ISO9660_BOOT_IMAGE = boot/grub/stage2_eltorito define ROOTFS_ISO9660_INSTALL_BOOTLOADER $(INSTALL) -D -m 0644 $(GRUB_DIR)/stage2/stage2_eltorito \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/grub/stage2_eltorito endef else ifeq ($(BR2_TARGET_ROOTFS_ISO9660_GRUB2),y) ROOTFS_ISO9660_DEPENDENCIES += grub2 ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH = \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/grub/grub.cfg ROOTFS_ISO9660_BOOT_IMAGE = boot/grub/grub-eltorito.img define ROOTFS_ISO9660_INSTALL_BOOTLOADER $(INSTALL) -D -m 0644 $(BINARIES_DIR)/grub-eltorito.img \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/grub/grub-eltorito.img endef else ifeq ($(BR2_TARGET_ROOTFS_ISO9660_ISOLINUX),y) ROOTFS_ISO9660_DEPENDENCIES += syslinux ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH = \ $(ROOTFS_ISO9660_TARGET_DIR)/isolinux/isolinux.cfg ROOTFS_ISO9660_BOOT_IMAGE = isolinux/isolinux.bin define ROOTFS_ISO9660_INSTALL_BOOTLOADER $(INSTALL) -D -m 0644 $(BINARIES_DIR)/syslinux/* \ $(ROOTFS_ISO9660_TARGET_DIR)/isolinux/ $(INSTALL) -D -m 0644 $(HOST_DIR)/usr/share/syslinux/ldlinux.c32 \ $(ROOTFS_ISO9660_TARGET_DIR)/isolinux/ldlinux.c32 endef endif define ROOTFS_ISO9660_PREPARATION $(INSTALL) -D -m 0644 $(ROOTFS_ISO9660_BOOT_MENU) \ $(ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH) $(SED) "s%__KERNEL_PATH__%/boot/$(LINUX_IMAGE_NAME)%" \ $(ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH) $(ROOTFS_ISO9660_INSTALL_BOOTLOADER) endef ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_PREPARATION # Grub splash screen disabling ifeq ($(BR2_TARGET_ROOTFS_ISO9660_GRUB),y) ifeq ($(BR2_TARGET_GRUB_SPLASH),) define ROOTFS_ISO9660_DISABLE_SPLASHSCREEN $(SED) '/^splashimage/d' $(ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH) endef ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_DISABLE_SPLASHSCREEN endif endif define ROOTFS_ISO9660_DISABLE_EXTERNAL_INITRD $(SED) '/__INITRD_PATH__/d' $(ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH) endef ifeq ($(ROOTFS_ISO9660_USE_INITRD),YES) # Copy Grub splashscreen to temporary filesystem ifeq ($(BR2_TARGET_ROOTFS_ISO9660_GRUB),y) ifeq ($(BR2_TARGET_GRUB_SPLASH),y) define ROOTFS_ISO9660_INSTALL_SPLASHSCREEN $(INSTALL) -D -m 0644 $(TARGET_DIR)/boot/grub/splash.xpm.gz \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/grub/splash.xpm.gz endef ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_INSTALL_SPLASHSCREEN endif endif # Copy the kernel to temporary filesystem define ROOTFS_ISO9660_COPY_KERNEL $(INSTALL) -D -m 0644 $(LINUX_IMAGE_PATH) \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/$(LINUX_IMAGE_NAME) endef ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_COPY_KERNEL # If initramfs is used, disable loading the initrd as the rootfs is # already inside the kernel image. Otherwise, make sure a cpio is # generated and use it as the initrd. ifeq ($(BR2_TARGET_ROOTFS_INITRAMFS),y) ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_DISABLE_EXTERNAL_INITRD else ROOTFS_ISO9660_DEPENDENCIES += rootfs-cpio define ROOTFS_ISO9660_COPY_INITRD $(INSTALL) -D -m 0644 $(BINARIES_DIR)/rootfs.cpio$(ROOTFS_CPIO_COMPRESS_EXT) \ $(ROOTFS_ISO9660_TARGET_DIR)/boot/initrd $(SED) "s%__INITRD_PATH__%/boot/initrd%" \ $(ROOTFS_ISO9660_BOOTLOADER_CONFIG_PATH) endef ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_COPY_INITRD endif else # ROOTFS_ISO9660_USE_INITRD ROOTFS_ISO9660_PRE_GEN_HOOKS += ROOTFS_ISO9660_DISABLE_EXTERNAL_INITRD endif # ROOTFS_ISO9660_USE_INITRD define ROOTFS_ISO9660_CMD $(HOST_DIR)/usr/bin/genisoimage -J -R -b $(ROOTFS_ISO9660_BOOT_IMAGE) \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -o $@ $(ROOTFS_ISO9660_TARGET_DIR) endef ifeq ($(BR2_TARGET_ROOTFS_ISO9660_HYBRID),y) define ROOTFS_ISO9660_GEN_HYBRID $(HOST_DIR)/usr/bin/isohybrid -t 0x96 $@ endef ROOTFS_ISO9660_POST_GEN_HOOKS += ROOTFS_ISO9660_GEN_HYBRID endif $(eval $(call ROOTFS_TARGET,iso9660))
shibajee/buildroot
fs/iso9660/iso9660.mk
mk
mit
5,424
default 1 label 1 kernel __KERNEL_PATH__ initrd __INITRD_PATH__ append root=/dev/sr0
shibajee/buildroot
fs/iso9660/isolinux.cfg
INI
mit
103
default 0 timeout 10 # Used when no splashimage is used color cyan/blue white/blue # Gets enabled/disabled depending on Grub support for splashimage splashimage /boot/grub/splash.xpm.gz # Used when a splashimage is enabled foreground 000000 background cccccc title Buildroot ISO9660 image kernel __KERNEL_PATH__ root=/dev/sr0 initrd __INITRD_PATH__ title Hard Drive (first partition) rootnoverify (hd0) chainloader +1
shibajee/buildroot
fs/iso9660/menu.lst
lst
mit
433
config BR2_TARGET_ROOTFS_JFFS2 bool "jffs2 root filesystem" help Build a jffs2 root filesystem if BR2_TARGET_ROOTFS_JFFS2 choice prompt "Flash Type" default BR2_TARGET_ROOTFS_JFFS2_FLASH_128 config BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_1056 bool "AT45 dataflash with 1056 byte pagesize" select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER config BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_528 bool "AT45 dataflash with 528 byte pagesize" select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER config BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_16K bool "NAND flash with 16 kB erasesize" select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER config BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K bool "NAND flash with 128 kB erasesize" select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER config BR2_TARGET_ROOTFS_JFFS2_FLASH_128 bool "Parallel flash with 128 kB erase size" config BR2_TARGET_ROOTFS_JFFS2_FLASH_64 bool "Parallel flash with 64 kB erase size" config BR2_TARGET_ROOTFS_JFFS2_CUSTOM bool "Select custom erase size" endchoice config BR2_TARGET_ROOTFS_JFFS2_CUSTOM_EBSIZE hex "Erase block size" depends on BR2_TARGET_ROOTFS_JFFS2_CUSTOM default 0x20000 help Set to erase size of memory config BR2_TARGET_ROOTFS_JFFS2_EBSIZE hex default 0x2100 if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_1056 default 0x1080 if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_528 default 0x4000 if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_16K default 0x20000 if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K default 0x20000 if BR2_TARGET_ROOTFS_JFFS2_FLASH_128 default 0x10000 if BR2_TARGET_ROOTFS_JFFS2_FLASH_64 default BR2_TARGET_ROOTFS_JFFS2_CUSTOM_EBSIZE if BR2_TARGET_ROOTFS_JFFS2_CUSTOM config BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER bool "Do not use Cleanmarker" default y if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_1056 default y if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_528 default y if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_16K default y if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K help Do not use cleanmarkers if using NAND flash or Dataflash where the pagesize is not a power of 2 config BR2_TARGET_ROOTFS_JFFS2_PAD bool "Pad output" config BR2_TARGET_ROOTFS_JFFS2_PADSIZE hex "Pad output size (0x0 = to end of EB)" depends on BR2_TARGET_ROOTFS_JFFS2_PAD default 0x0 help Set to 0x0 to pad to end of erase block. choice prompt "Endianess" default BR2_TARGET_ROOTFS_JFFS2_BE if BR2_ENDIAN = "BIG" config BR2_TARGET_ROOTFS_JFFS2_LE bool "little-endian" config BR2_TARGET_ROOTFS_JFFS2_BE bool "big-endian" endchoice config BR2_TARGET_ROOTFS_JFFS2_SUMMARY bool "Produce a summarized JFFS2 image" help A summarised image can be mounted faster if support is enabled in the kernel (CONFIG_JFFS2_SUMMARY) config BR2_TARGET_ROOTFS_JFFS2_USE_CUSTOM_PAGESIZE bool "Select custom virtual memory page size" help Use a custom virtual memory page size. Note that this is not related to the flash memory page size. Using this option is only needed if Linux is configured to use a page size different than 4kB. config BR2_TARGET_ROOTFS_JFFS2_CUSTOM_PAGESIZE hex "Virtual memory page size" depends on BR2_TARGET_ROOTFS_JFFS2_USE_CUSTOM_PAGESIZE default 0x1000 help Set to virtual memory page size of target system (in bytes). This value should match the virtual page size in Linux (i.e. this should have the same value as the value of the PAGE_SIZE macro in Linux). It is not related to the flash memory page size. endif
shibajee/buildroot
fs/jffs2/Config.in
in
mit
3,410
################################################################################ # # Build the jffs2 root filesystem image # ################################################################################ JFFS2_OPTS := -e $(BR2_TARGET_ROOTFS_JFFS2_EBSIZE) SUMTOOL_OPTS := $(JFFS2_OPTS) ifeq ($(BR2_TARGET_ROOTFS_JFFS2_PAD),y) ifneq ($(strip $(BR2_TARGET_ROOTFS_JFFS2_PADSIZE)),0x0) JFFS2_OPTS += --pad=$(strip $(BR2_TARGET_ROOTFS_JFFS2_PADSIZE)) else JFFS2_OPTS += -p endif SUMTOOL_OPTS += -p endif ifeq ($(BR2_TARGET_ROOTFS_JFFS2_LE),y) JFFS2_OPTS += -l SUMTOOL_OPTS += -l endif ifeq ($(BR2_TARGET_ROOTFS_JFFS2_BE),y) JFFS2_OPTS += -b SUMTOOL_OPTS += -b endif ifeq ($(BR2_TARGET_ROOTFS_JFFS2_USE_CUSTOM_PAGESIZE),y) JFFS2_OPTS += -s $(BR2_TARGET_ROOTFS_JFFS2_CUSTOM_PAGESIZE) endif ifeq ($(BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER),y) JFFS2_OPTS += -n SUMTOOL_OPTS += -n endif ROOTFS_JFFS2_DEPENDENCIES = host-mtd ifneq ($(BR2_TARGET_ROOTFS_JFFS2_SUMMARY),) define ROOTFS_JFFS2_CMD $(MKFS_JFFS2) $(JFFS2_OPTS) -d $(TARGET_DIR) -o $@.nosummary $(SUMTOOL) $(SUMTOOL_OPTS) -i $@.nosummary -o $@ rm $@.nosummary endef else define ROOTFS_JFFS2_CMD $(MKFS_JFFS2) $(JFFS2_OPTS) -d $(TARGET_DIR) -o $@ endef endif $(eval $(call ROOTFS_TARGET,jffs2))
shibajee/buildroot
fs/jffs2/jffs2.mk
mk
mit
1,254
config BR2_TARGET_ROOTFS_ROMFS bool "romfs root filesystem" help Build a romfs image of the root filesystem.
shibajee/buildroot
fs/romfs/Config.in
in
mit
114
################################################################################ # # Build the romfs root filesystem image # ################################################################################ ROOTFS_ROMFS_DEPENDENCIES = host-genromfs define ROOTFS_ROMFS_CMD $(HOST_DIR)/usr/bin/genromfs -d $(TARGET_DIR) -f $@ endef $(eval $(call ROOTFS_TARGET,romfs))
shibajee/buildroot
fs/romfs/romfs.mk
mk
mit
370
config BR2_TARGET_ROOTFS_SQUASHFS bool "squashfs root filesystem" help Build a squashfs root filesystem if BR2_TARGET_ROOTFS_SQUASHFS choice prompt "Compression algorithm" default BR2_TARGET_ROOTFS_SQUASHFS4_GZIP help Select the squashfs compression algorithm to use when generating the filesystem. config BR2_TARGET_ROOTFS_SQUASHFS4_GZIP bool "gzip" config BR2_TARGET_ROOTFS_SQUASHFS4_LZ4 bool "lz4" config BR2_TARGET_ROOTFS_SQUASHFS4_LZMA bool "lzma" config BR2_TARGET_ROOTFS_SQUASHFS4_LZO bool "lzo" config BR2_TARGET_ROOTFS_SQUASHFS4_XZ bool "xz" endchoice endif
shibajee/buildroot
fs/squashfs/Config.in
in
mit
594
################################################################################ # # Build the squashfs root filesystem image # ################################################################################ ROOTFS_SQUASHFS_DEPENDENCIES = host-squashfs ifeq ($(BR2_TARGET_ROOTFS_SQUASHFS4_LZ4),y) ROOTFS_SQUASHFS_ARGS += -comp lz4 -Xhc else ifeq ($(BR2_TARGET_ROOTFS_SQUASHFS4_LZO),y) ROOTFS_SQUASHFS_ARGS += -comp lzo else ifeq ($(BR2_TARGET_ROOTFS_SQUASHFS4_LZMA),y) ROOTFS_SQUASHFS_ARGS += -comp lzma else ifeq ($(BR2_TARGET_ROOTFS_SQUASHFS4_XZ),y) ROOTFS_SQUASHFS_ARGS += -comp xz else ROOTFS_SQUASHFS_ARGS += -comp gzip endif endif endif endif define ROOTFS_SQUASHFS_CMD $(HOST_DIR)/usr/bin/mksquashfs $(TARGET_DIR) $@ -noappend \ $(ROOTFS_SQUASHFS_ARGS) endef $(eval $(call ROOTFS_TARGET,squashfs))
shibajee/buildroot
fs/squashfs/squashfs.mk
mk
mit
813
config BR2_TARGET_ROOTFS_TAR bool "tar the root filesystem" default y help Build a tar archive of the root filesystem choice prompt "Compression method" default BR2_TARGET_ROOTFS_TAR_NONE depends on BR2_TARGET_ROOTFS_TAR help Select compressor for tar archive of the root filesystem config BR2_TARGET_ROOTFS_TAR_NONE bool "no compression" help Do not compress the tarball. config BR2_TARGET_ROOTFS_TAR_GZIP bool "gzip" help Do compress the tarball with gzip. config BR2_TARGET_ROOTFS_TAR_BZIP2 bool "bzip2" help Do compress the tarball with bzip2. config BR2_TARGET_ROOTFS_TAR_LZMA bool "lzma" help Do compress the tarball with lzma. config BR2_TARGET_ROOTFS_TAR_LZO bool "lzo" help Do compress the tarball with lzop. config BR2_TARGET_ROOTFS_TAR_XZ bool "xz" help Do compress the tarball with xz. endchoice config BR2_TARGET_ROOTFS_TAR_OPTIONS string "other random options to pass to tar" depends on BR2_TARGET_ROOTFS_TAR default "" help Any other flags you want to pass to tar Refer to tar --help for details
shibajee/buildroot
fs/tar/Config.in
in
mit
1,073
################################################################################ # # tar to archive target filesystem # ################################################################################ TAR_OPTS := $(call qstrip,$(BR2_TARGET_ROOTFS_TAR_OPTIONS)) define ROOTFS_TAR_CMD tar $(TAR_OPTS) -cf $@ --numeric-owner -C $(TARGET_DIR) . endef $(eval $(call ROOTFS_TARGET,tar))
shibajee/buildroot
fs/tar/tar.mk
mk
mit
385
config BR2_TARGET_ROOTFS_UBIFS bool "ubifs root filesystem" help Build a ubifs root filesystem if BR2_TARGET_ROOTFS_UBIFS config BR2_TARGET_ROOTFS_UBIFS_LEBSIZE hex "logical eraseblock size" default 0x1f800 help Logical eraseblock (LEB) size. The value provided here is passed to the -e/--leb-size option of mkfs.ubifs. config BR2_TARGET_ROOTFS_UBIFS_MINIOSIZE hex "minimum I/O unit size" default 0x800 help Minimum I/O unit size. The value provided here is passed to the -m/--min-io-size option of mkfs.ubifs/ubinize. config BR2_TARGET_ROOTFS_UBIFS_MAXLEBCNT int "maximum logical eraseblock count" default 2048 help Maximum logical eraseblock (LEB) count. The value provided here is passed to the -c/--max-leb-cnt option of mkfs.ubifs. choice prompt "ubifs runtime compression" default BR2_TARGET_ROOTFS_UBIFS_RT_LZO help Select which compression format to use at run-time within the ubifs file system. The choice made here is passed to the -x/--compr option of mkfs.ubifs config BR2_TARGET_ROOTFS_UBIFS_RT_NONE bool "no compression" help Don't use run-time compression. config BR2_TARGET_ROOTFS_UBIFS_RT_ZLIB bool "gzip" help Use zlib compression at run-time. config BR2_TARGET_ROOTFS_UBIFS_RT_LZO bool "lzo" help Use lzo compression at run-time. endchoice choice prompt "Compression method" default BR2_TARGET_ROOTFS_UBIFS_NONE help Select which compression format to compress the final image into. config BR2_TARGET_ROOTFS_UBIFS_NONE bool "no compression" help Do not compress the ubifs filesystem. config BR2_TARGET_ROOTFS_UBIFS_GZIP bool "gzip" help Do compress the ubifs filesystem with gzip. config BR2_TARGET_ROOTFS_UBIFS_BZIP2 bool "bzip2" help Do compress the ubifs filesystem with bzip2. config BR2_TARGET_ROOTFS_UBIFS_LZMA bool "lzma" help Do compress the ubifs filesystem with lzma. config BR2_TARGET_ROOTFS_UBIFS_LZO bool "lzo" help Do compress the ubifs filesystem with lzop. config BR2_TARGET_ROOTFS_UBIFS_XZ bool "xz" help Do compress the ubifs filesystem with xz. endchoice config BR2_TARGET_ROOTFS_UBIFS_OPTS string "Additional mkfs.ubifs options" help Any additional mkfs.ubifs options you may want to include. config BR2_TARGET_ROOTFS_UBI bool "Embed into an UBI image" help Build an ubi image from the ubifs one (with ubinize). if BR2_TARGET_ROOTFS_UBI config BR2_TARGET_ROOTFS_UBI_PEBSIZE hex "physical eraseblock size" default 0x20000 help Tells ubinize the physical eraseblock (PEB) size of the flash chip the ubi image is created for. The value provided here is passed to the -p/--peb-size option of ubinize. config BR2_TARGET_ROOTFS_UBI_SUBSIZE int "sub-page size" default 512 help Tells ubinize that the flash supports sub-pages and the sub-page size. Use 0 if sub-pages are not supported on flash chip. The value provided here is passed to the -s/--sub-page-size option of ubinize. config BR2_TARGET_ROOTFS_UBI_USE_CUSTOM_CONFIG bool "Use custom config file" help Select this option to use a custom ubinize configuration file, rather than the default configuration used by Buildroot (which defines a single dynamic volume marked as auto-resize). Passing a custom ubinize configuration file allows you to create several volumes, specify volume types, etc. As a convenience, buildroot replaces the string "BR2_ROOTFS_UBIFS_PATH" with the path to the built ubifs file. So the volume defined for the root filesystem can specify the image path as: image=BR2_ROOTFS_UBIFS_PATH config BR2_TARGET_ROOTFS_UBI_CUSTOM_CONFIG_FILE string "Configuration file path" depends on BR2_TARGET_ROOTFS_UBI_USE_CUSTOM_CONFIG help Path to the ubinize configuration file. config BR2_TARGET_ROOTFS_UBI_OPTS string "Additional ubinize options" help Any additional ubinize options you may want to include. endif # BR2_TARGET_ROOTFS_UBI endif # BR2_TARGET_ROOTFS_UBIFS
shibajee/buildroot
fs/ubifs/Config.in
in
mit
3,976
################################################################################ # # Embed the ubifs image into an ubi image # ################################################################################ UBI_UBINIZE_OPTS := -m $(BR2_TARGET_ROOTFS_UBIFS_MINIOSIZE) UBI_UBINIZE_OPTS += -p $(BR2_TARGET_ROOTFS_UBI_PEBSIZE) ifneq ($(BR2_TARGET_ROOTFS_UBI_SUBSIZE),0) UBI_UBINIZE_OPTS += -s $(BR2_TARGET_ROOTFS_UBI_SUBSIZE) endif UBI_UBINIZE_OPTS += $(call qstrip,$(BR2_TARGET_ROOTFS_UBI_OPTS)) ROOTFS_UBI_DEPENDENCIES = rootfs-ubifs ifeq ($(BR2_TARGET_ROOTFS_UBI_USE_CUSTOM_CONFIG),y) UBINIZE_CONFIG_FILE_PATH = $(call qstrip,$(BR2_TARGET_ROOTFS_UBI_CUSTOM_CONFIG_FILE)) else UBINIZE_CONFIG_FILE_PATH = fs/ubifs/ubinize.cfg endif define ROOTFS_UBI_CMD $(INSTALL) -m 0644 $(UBINIZE_CONFIG_FILE_PATH) $(BUILD_DIR)/ubinize.cfg $(SED) 's;BR2_ROOTFS_UBIFS_PATH;$@fs;' $(BUILD_DIR)/ubinize.cfg $(HOST_DIR)/usr/sbin/ubinize -o $@ $(UBI_UBINIZE_OPTS) $(BUILD_DIR)/ubinize.cfg rm $(BUILD_DIR)/ubinize.cfg endef $(eval $(call ROOTFS_TARGET,ubi))
shibajee/buildroot
fs/ubifs/ubi.mk
mk
mit
1,046
################################################################################ # # Build the ubifs root filesystem image # ################################################################################ UBIFS_OPTS := -e $(BR2_TARGET_ROOTFS_UBIFS_LEBSIZE) -c $(BR2_TARGET_ROOTFS_UBIFS_MAXLEBCNT) -m $(BR2_TARGET_ROOTFS_UBIFS_MINIOSIZE) ifeq ($(BR2_TARGET_ROOTFS_UBIFS_RT_ZLIB),y) UBIFS_OPTS += -x zlib endif ifeq ($(BR2_TARGET_ROOTFS_UBIFS_RT_LZO),y) UBIFS_OPTS += -x lzo endif ifeq ($(BR2_TARGET_ROOTFS_UBIFS_RT_NONE),y) UBIFS_OPTS += -x none endif UBIFS_OPTS += $(call qstrip,$(BR2_TARGET_ROOTFS_UBIFS_OPTS)) ROOTFS_UBIFS_DEPENDENCIES = host-mtd define ROOTFS_UBIFS_CMD $(HOST_DIR)/usr/sbin/mkfs.ubifs -d $(TARGET_DIR) $(UBIFS_OPTS) -o $@ endef $(eval $(call ROOTFS_TARGET,ubifs))
shibajee/buildroot
fs/ubifs/ubifs.mk
mk
mit
792
[ubifs] mode=ubi vol_id=0 vol_type=dynamic vol_name=rootfs vol_alignment=1 vol_flags=autoresize image=BR2_ROOTFS_UBIFS_PATH
shibajee/buildroot
fs/ubifs/ubinize.cfg
INI
mit
124
config BR2_TARGET_ROOTFS_YAFFS2 bool "yaffs2 root filesystem" help Build a yaffs2 root filesystem
shibajee/buildroot
fs/yaffs2/Config.in
in
mit
103
################################################################################ # # Build the yaffs2 root filesystem image # ################################################################################ ROOTFS_YAFFS2_DEPENDENCIES = host-yaffs2utils define ROOTFS_YAFFS2_CMD $(HOST_DIR)/usr/bin/mkyaffs2 --all-root $(TARGET_DIR) $@ endef $(eval $(call ROOTFS_TARGET,yaffs2))
shibajee/buildroot
fs/yaffs2/yaffs.mk
mk
mit
382
From 63a3f603413ffe82ad775f2d62a5afff87fd94a0 Mon Sep 17 00:00:00 2001 From: "H. Peter Anvin" <hpa@linux.intel.com> Date: Thu, 7 Feb 2013 17:14:08 -0800 Subject: [PATCH] timeconst.pl: Eliminate Perl warning defined(@array) is deprecated in Perl and gives off a warning. Restructure the code to remove that warning. [ hpa: it would be interesting to revert to the timeconst.bc script. It appears that the failures reported by akpm during testing of that script was due to a known broken version of make, not a problem with bc. The Makefile rules could probably be restructured to avoid the make bug, or it is probably old enough that it doesn't matter. ] Reported-by: Andi Kleen <ak@linux.intel.com> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: <stable@vger.kernel.org> Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com> --- Patch status: upstream kernel/timeconst.pl | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/kernel/timeconst.pl b/kernel/timeconst.pl index eb51d76..3f42652 100644 --- a/kernel/timeconst.pl +++ b/kernel/timeconst.pl @@ -369,10 +369,8 @@ if ($hz eq '--can') { die "Usage: $0 HZ\n"; } - @val = @{$canned_values{$hz}}; - if (!defined(@val)) { - @val = compute_values($hz); - } + $cv = $canned_values{$hz}; + @val = defined($cv) ? @$cv : compute_values($hz); output($hz, @val); } exit 0; -- 2.4.10
shibajee/buildroot
linux/0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional
conditional
mit
1,447
menu "Linux Kernel Extensions" # Xenomai config BR2_LINUX_KERNEL_EXT_XENOMAI bool "Adeos/Xenomai Real-time patch" depends on BR2_TOOLCHAIN_HAS_THREADS depends on BR2_i386 || BR2_x86_64 || BR2_arm || \ BR2_bfin || BR2_powerpc || BR2_sh4 select BR2_PACKAGE_XENOMAI help Xenomai is split in two parts: a kernel part and a userspace part. Enabling this option automatically selects the Xenomai package and helps in patching the Linux kernel built by Buildroot with the Xenomai kernel part (ie Adeos/Ipipe). You can find the currently supported kernel versions by looking at the available patches in the Xenomai sources tree: ksrc/arch/$(ARCH)/patches However, it is recommended to use the latest version of the Adeos/Ipipe patch available at http://download.gna.org/adeos/patches Xenomai is know to support Blackfin, SH4, x86, ARM, NIOS2 and PowerPC architectures. comment "xenomai needs a toolchain w/ threads" depends on BR2_i386 || BR2_x86_64 || BR2_arm || \ BR2_bfin || BR2_powerpc || BR2_sh4 depends on !BR2_TOOLCHAIN_HAS_THREADS config BR2_LINUX_KERNEL_EXT_XENOMAI_ADEOS_PATCH depends on BR2_LINUX_KERNEL_EXT_XENOMAI string "Path for Adeos patch file" help Optionally, explicitly specify the Adeos patch to use. Download it at http://download.gna.org/adeos/patches and verify that your kernel version in buildroot matches. # RTAI config BR2_LINUX_KERNEL_EXT_RTAI bool "RTAI Real-time patch" select BR2_PACKAGE_RTAI help RTAI Kernel part. # fbtft config BR2_LINUX_KERNEL_EXT_FBTFT bool "FB TFT drivers" select BR2_PACKAGE_FBTFT help Linux Framebuffer drivers for small TFT LCD display modules, e.g. Adafruit PiTFT displays for Raspberry Pi (this extra package is only needed for linux kernels until v3.19, since v4.0 the drivers are included in the staging area). To enable fbtft, e.g. for Adafruit 2.8 PiTFT, enable the following kernel configurations: - CONFIG_SPI - CONFIG_GPIOLIB - CONFIG_FB - CONFIG_FB_TFT - CONFIG_FB_TFT_ILI9341 https://github.com/notro/fbtft endmenu
shibajee/buildroot
linux/Config.ext.in
in
mit
2,097
menu "Kernel" config BR2_LINUX_KERNEL bool "Linux Kernel" help Enable this option if you want to build a Linux kernel for your embedded device if BR2_LINUX_KERNEL # Packages that need to have a kernel with support for loadable modules, # but do not use the kernel-modules infrastructure, should select that # option. config BR2_LINUX_NEEDS_MODULES bool # # Version selection. We provide the choice between: # # 1. A single fairly recent stable kernel version # 2. A custom stable version # 3. A custom tarball # 4. A set of custom repository locations # choice prompt "Kernel version" config BR2_LINUX_KERNEL_LATEST_VERSION bool "Latest version (4.7.2)" config BR2_LINUX_KERNEL_CUSTOM_VERSION bool "Custom version" help This option allows to use a specific official version from kernel.org, like 2.6.x, 2.6.x.y, 3.x.y, ... Note: you cannot use this option to select a _longterm_ 2.6 kernel, because these kernels are not located at the standard URL at kernel.org. Instead, select "Custom tarball" and specify the right URL directly. config BR2_LINUX_KERNEL_CUSTOM_TARBALL bool "Custom tarball" help This option allows to specify a URL pointing to a kernel source tarball. This URL can use any protocol recognized by Buildroot, like http://, ftp://, file:// or scp://. When pointing to a local tarball using file://, you may want to use a make variable like $(TOPDIR) to reference the root of the Buildroot tree. config BR2_LINUX_KERNEL_CUSTOM_GIT bool "Custom Git repository" help This option allows Buildroot to get the Linux kernel source code from a Git repository. config BR2_LINUX_KERNEL_CUSTOM_HG bool "Custom Mercurial repository" help This option allows Buildroot to get the Linux kernel source code from a Mercurial repository. config BR2_LINUX_KERNEL_CUSTOM_SVN bool "Custom Subversion repository" help This option allows Buildroot to get the Linux kernel source code from a Subversion repository. config BR2_LINUX_KERNEL_CUSTOM_LOCAL bool "Local directory" help This option allows Buildroot to get the Linux kernel source code from a local directory. endchoice config BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE string "Kernel version" depends on BR2_LINUX_KERNEL_CUSTOM_VERSION config BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION string "URL of custom kernel tarball" depends on BR2_LINUX_KERNEL_CUSTOM_TARBALL if BR2_LINUX_KERNEL_CUSTOM_GIT || BR2_LINUX_KERNEL_CUSTOM_HG || BR2_LINUX_KERNEL_CUSTOM_SVN config BR2_LINUX_KERNEL_CUSTOM_REPO_URL string "URL of custom repository" default BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL \ if BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL != "" # legacy config BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION string "Custom repository version" default BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION \ if BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION != "" # legacy help Revision to use in the typical format used by Git/Mercurial/Subversion E.G. a sha id, a tag, branch, .. endif config BR2_LINUX_KERNEL_CUSTOM_LOCAL_PATH string "Path to the local directory" depends on BR2_LINUX_KERNEL_CUSTOM_LOCAL help Path to the local directory with the Linux kernel source code. config BR2_LINUX_KERNEL_VERSION string default "4.7.2" if BR2_LINUX_KERNEL_LATEST_VERSION default BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE \ if BR2_LINUX_KERNEL_CUSTOM_VERSION default "custom" if BR2_LINUX_KERNEL_CUSTOM_TARBALL default BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION \ if BR2_LINUX_KERNEL_CUSTOM_GIT || BR2_LINUX_KERNEL_CUSTOM_HG || BR2_LINUX_KERNEL_CUSTOM_SVN default "custom" if BR2_LINUX_KERNEL_CUSTOM_LOCAL # # Patch selection # config BR2_LINUX_KERNEL_PATCH string "Custom kernel patches" depends on !BR2_LINUX_KERNEL_CUSTOM_LOCAL help A space-separated list of patches to apply to the kernel. Each patch can be described as an URL, a local file path, or a directory. In the case of a directory, all files matching *.patch in the directory will be applied. # # Configuration selection # choice prompt "Kernel configuration" default BR2_LINUX_KERNEL_USE_DEFCONFIG config BR2_LINUX_KERNEL_USE_DEFCONFIG bool "Using an in-tree defconfig file" config BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG bool "Use the architecture default configuration" help This option will use the default configuration for the selected architecture. I.e, it is equivalent to running "make ARCH=<foo> defconfig". This is useful on architectures that have a single defconfig file, such as ARM64. config BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG bool "Using a custom (def)config file" endchoice config BR2_LINUX_KERNEL_DEFCONFIG string "Defconfig name" depends on BR2_LINUX_KERNEL_USE_DEFCONFIG help Name of the kernel defconfig file to use, without the trailing _defconfig. The defconfig is located in arch/<arch>/configs in the kernel tree. config BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE string "Configuration file path" depends on BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG help Path to the kernel configuration file Note: this can be a defconfig file or a complete .config file, which can later be saved back with make linux-update-(def)config. config BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES string "Additional configuration fragment files" help A space-separated list of kernel configuration fragment files, that will be merged to the main kernel configuration file. # # Binary format # config BR2_LINUX_KERNEL_UBOOT_IMAGE bool choice prompt "Kernel binary format" default BR2_LINUX_KERNEL_ZIMAGE if BR2_arm || BR2_armeb config BR2_LINUX_KERNEL_UIMAGE bool "uImage" depends on BR2_arc || BR2_arm || BR2_armeb || BR2_bfin || \ BR2_powerpc || BR2_powerpc64 || BR2_powerpc64le || \ BR2_sh || BR2_sh64 || BR2_mips || BR2_mipsel || \ BR2_mips64 || BR2_mips64el select BR2_LINUX_KERNEL_UBOOT_IMAGE config BR2_LINUX_KERNEL_APPENDED_UIMAGE bool "uImage with appended DT" depends on BR2_arm || BR2_armeb select BR2_LINUX_KERNEL_DTS_SUPPORT select BR2_LINUX_KERNEL_APPENDED_DTB select BR2_LINUX_KERNEL_UBOOT_IMAGE config BR2_LINUX_KERNEL_BZIMAGE bool "bzImage" depends on BR2_i386 || BR2_x86_64 config BR2_LINUX_KERNEL_ZIMAGE bool "zImage" depends on BR2_arm || BR2_armeb || BR2_powerpc || \ BR2_powerpc64 || BR2_powerpc64le || BR2_sparc || \ BR2_sh || BR2_sh64 || BR2_xtensa config BR2_LINUX_KERNEL_ZIMAGE_EPAPR bool "zImage.epapr" depends on BR2_powerpc64 || BR2_powerpc64le config BR2_LINUX_KERNEL_APPENDED_ZIMAGE bool "zImage with appended DT" depends on BR2_arm || BR2_armeb select BR2_LINUX_KERNEL_DTS_SUPPORT select BR2_LINUX_KERNEL_APPENDED_DTB config BR2_LINUX_KERNEL_CUIMAGE bool "cuImage" depends on BR2_powerpc select BR2_LINUX_KERNEL_UBOOT_IMAGE select BR2_LINUX_KERNEL_DTS_SUPPORT select BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT config BR2_LINUX_KERNEL_SIMPLEIMAGE bool "simpleImage" depends on BR2_microblaze select BR2_LINUX_KERNEL_UBOOT_IMAGE select BR2_LINUX_KERNEL_DTS_SUPPORT select BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT config BR2_LINUX_KERNEL_IMAGE bool "Image" depends on BR2_aarch64 config BR2_LINUX_KERNEL_LINUX_BIN bool "linux.bin" depends on BR2_microblaze select BR2_LINUX_KERNEL_UBOOT_IMAGE config BR2_LINUX_KERNEL_VMLINUX_BIN bool "vmlinux.bin" depends on BR2_mips || BR2_mipsel || BR2_sh || BR2_sh64 config BR2_LINUX_KERNEL_VMLINUX bool "vmlinux" config BR2_LINUX_KERNEL_VMLINUZ bool "vmlinuz" depends on BR2_mips || BR2_mipsel config BR2_LINUX_KERNEL_VMLINUZ_BIN bool "vmlinuz.bin" depends on BR2_mips || BR2_mipsel config BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM bool "custom target" help For certain cases a board-specific target image must be used. For example, on powerPC where the OpenFirmware description is attached in a board-specific kernel image target like 'cuImage.mpc8379_rdb'. Select this option and specify the make target in "Kernel image target name". endchoice # # Kernel compression format # choice prompt "Kernel compression format" help This selection will just ensure that the correct host tools are build. The actual compression for the kernel should be selected in the kernel configuration menu. config BR2_LINUX_KERNEL_GZIP bool "gzip compression" config BR2_LINUX_KERNEL_LZ4 bool "lz4 compression" config BR2_LINUX_KERNEL_LZMA bool "lzma compression" config BR2_LINUX_KERNEL_LZO bool "lzo compression" config BR2_LINUX_KERNEL_XZ bool "xz compression" endchoice config BR2_LINUX_KERNEL_IMAGE_TARGET_NAME string "Kernel image target name" depends on BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM help Specify the kernel make target to build the kernel that you need. config BR2_LINUX_KERNEL_IMAGE_NAME string "Kernel image name" depends on BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM help The filename of the kernel image, if it is different from the make target (above). Only Xtensa uses a filename different from the make target. Defaults to BR2_LINUX_KERNEL_IMAGE_TARGET_NAME. If unsure, leave it empty. config BR2_LINUX_KERNEL_UIMAGE_LOADADDR string "load address (for 3.7+ multi-platform image)" depends on BR2_arm || BR2_armeb depends on BR2_LINUX_KERNEL_UIMAGE || BR2_LINUX_KERNEL_APPENDED_UIMAGE help If your ARM system's Linux kernel is configured with the new (3.7+) multi-architecture support (CONFIG_ARCH_MULTIPLATFORM=y in your kernel config), then it is necessary to specify a kernel load address when building the uImage. This should be a hexadecimal string beginning with 0x, for example: 0x00008000. If unsure, let this option empty. config BR2_LINUX_KERNEL_DTS_SUPPORT bool "Build a Device Tree Blob (DTB)" help Compile one or more device tree sources into device tree blobs. Select the dts files to compile in the options below. if BR2_LINUX_KERNEL_DTS_SUPPORT # We have mainly three cases when it comes to device tree support: # 1) We don't want any support at all. Then the ..DTS_SUPPORT # variable won't be set # 2) We want device tree support, so we need the user to enter the # device tree name or the path to the custom device he uses, but # the kernel abstracts this from us and only build an image that # looks like a regular kernel image. In this case, we only need # to derive the kernel image name from the given device tree # name, and all the rest is as usual # 3) We want device tree support, but the kernel requires us to # build the device tree blob separately. In this case, some # more logic will be needed. # The variable below address the second case, were you only want # limited actions from buildroot. config BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT bool config BR2_LINUX_KERNEL_APPENDED_DTB bool choice prompt "Device tree source" default BR2_LINUX_KERNEL_USE_INTREE_DTS config BR2_LINUX_KERNEL_USE_INTREE_DTS bool "Use a device tree present in the kernel." help Use a device tree source distributed with the kernel sources. The dts files are located in the arch/<arch>/boot/dts folder. config BR2_LINUX_KERNEL_USE_CUSTOM_DTS bool "Use a custom device tree file" help Use a custom device tree file, i.e, a device tree file that does not belong to the kernel source tree. endchoice config BR2_LINUX_KERNEL_INTREE_DTS_NAME string "Device Tree Source file names" depends on BR2_LINUX_KERNEL_USE_INTREE_DTS help Name of the device tree source file, without the trailing .dts. You can provide a list of dts files to build, separated by spaces. config BR2_LINUX_KERNEL_CUSTOM_DTS_PATH string "Device Tree Source file paths" depends on BR2_LINUX_KERNEL_USE_CUSTOM_DTS help Path to the device tree source files. You can provide a list of dts paths to copy and build, separated by spaces. endif config BR2_LINUX_KERNEL_INSTALL_TARGET bool "Install kernel image to /boot in target" depends on !BR2_TARGET_ROOTFS_INITRAMFS help Select this option to have the kernel image installed to /boot in the target root filesystem, as is typically done on x86/x86_64 systems. Note that this option also installs the Device Tree Blobs to /boot if DTBs have been generated by the kernel build process. # Linux extensions source "linux/Config.ext.in" # Linux tools source "linux/Config.tools.in" endif # BR2_LINUX_KERNEL endmenu
shibajee/buildroot
linux/Config.in
in
mit
12,332
menu "Linux Kernel Tools" config BR2_LINUX_KERNEL_TOOL_CPUPOWER bool "cpupower" depends on !BR2_bfin # pciutils depends on BR2_USE_WCHAR || !BR2_NEEDS_GETTEXT # gettext select BR2_PACKAGE_PCIUTILS select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT help cpupower is a collection of tools to examine and tune power saving related features of your processor. comment "cpupower needs a toolchain w/ wchar" depends on !BR2_bfin depends on !BR2_USE_WCHAR && BR2_NEEDS_GETTEXT config BR2_LINUX_KERNEL_TOOL_PERF bool "perf" help perf (sometimes "Perf Events" or perf tools, originally "Performance Counters for Linux") - is a performance analyzing tool in Linux, available from kernel version 2.6.31. User-space controlling utility, called 'perf' has git-like interface with subcommands. It is capable of statistical profiling of entire system (both kernel and user code), single CPU or severals threads. This will build and install the userspace 'perf' command. It is up to the user to ensure that the kernel configuration has all the suitable options enabled to allow a proper operation of 'perf'. https://perf.wiki.kernel.org/ config BR2_LINUX_KERNEL_TOOL_SELFTESTS bool"selftests" depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # bash depends on BR2_USE_MMU # bash select BR2_PACKAGE_BASH # runtime select BR2_PACKAGE_POPT select BR2_PACKAGE_LIBCAP_NG help Build and install (to /usr/lib/kselftests) kernel selftests. Use of this option implies you know the process of using and compiling the kernel selftests. The Makefile to build and install these is very noisy and may appear to cause your build to fail for strange reasons. This is very much a use at your risk option and may not work for every setup or every architecture. comment "selftests needs BR2_PACKAGE_BUSYBOX_SHOW_OTHERS" depends on BR2_USE_MMU depends on !BR2_PACKAGE_BUSYBOX_SHOW_OTHERS endmenu
shibajee/buildroot
linux/Config.tools.in
in
mit
1,944
################################################################################ # Linux fbtft extensions # # Patch the linux kernel with fbtft extension ################################################################################ LINUX_EXTENSIONS += fbtft # for linux >= 3.15 install to drivers/video/fbdev/fbtft # for linux < 3.15 install to drivers/video/fbtft define FBTFT_PREPARE_KERNEL if [ -e $(LINUX_DIR)/drivers/video/fbdev ]; then \ dest=drivers/video/fbdev ; \ else \ dest=drivers/video ; \ fi ; \ mkdir -p $(LINUX_DIR)/$${dest}/fbtft; \ cp -dpfr $(FBTFT_DIR)/* $(LINUX_DIR)/$${dest}/fbtft/ ; \ echo "source \"$${dest}/fbtft/Kconfig\"" \ >> $(LINUX_DIR)/$${dest}/Kconfig ; \ echo 'obj-y += fbtft/' >> $(LINUX_DIR)/$${dest}/Makefile endef
shibajee/buildroot
linux/linux-ext-fbtft.mk
mk
mit
768
################################################################################ # Linux RTAI extensions # # Patch the linux kernel with RTAI extension ################################################################################ LINUX_EXTENSIONS += rtai ifeq ($(KERNEL_ARCH),i386) RTAI_ARCH = x86 else ifeq ($(KERNEL_ARCH),x86_64) RTAI_ARCH = x86 else ifeq ($(KERNEL_ARCH),powerpc) RTAI_ARCH = ppc else RTAI_ARCH = $(KERNEL_ARCH) endif # Prepare kernel patch define RTAI_PREPARE_KERNEL kver=`$(MAKE) $(LINUX_MAKE_FLAGS) -C $(LINUX_DIR) --no-print-directory -s kernelversion` ; \ if test -f $(RTAI_DIR)/base/arch/$(RTAI_ARCH)/patches/hal-linux-$${kver}-*patch ; then \ $(APPLY_PATCHES) $(LINUX_DIR) \ $(RTAI_DIR)/base/arch/$(RTAI_ARCH)/patches/ \ hal-linux-$${kver}-*patch ; \ else \ echo "No RTAI patch for your kernel version" ; \ exit 1 ; \ fi endef
shibajee/buildroot
linux/linux-ext-rtai.mk
mk
mit
880
################################################################################ # Linux Adeos/Xenomai extensions # # Patch the linux kernel with xenomai extension ################################################################################ LINUX_EXTENSIONS += xenomai # Adeos patch version XENOMAI_ADEOS_PATCH = $(call qstrip,$(BR2_LINUX_KERNEL_EXT_XENOMAI_ADEOS_PATCH)) ifeq ($(XENOMAI_ADEOS_PATCH),) XENOMAI_ADEOS_OPTS = --default else XENOMAI_ADEOS_OPTS = --adeos=$(XENOMAI_ADEOS_PATCH) endif # Prepare kernel patch define XENOMAI_PREPARE_KERNEL $(XENOMAI_DIR)/scripts/prepare-kernel.sh \ --linux=$(LINUX_DIR) \ --arch=$(KERNEL_ARCH) \ $(XENOMAI_ADEOS_OPTS) \ --verbose endef
shibajee/buildroot
linux/linux-ext-xenomai.mk
mk
mit
696
################################################################################ # # cpupower # ################################################################################ LINUX_TOOLS += cpupower CPUPOWER_DEPENDENCIES = pciutils $(if $(BR2_NEEDS_GETTEXT),gettext) CPUPOWER_MAKE_OPTS = CROSS=$(TARGET_CROSS) \ CPUFREQ_BENCH=false \ NLS=false \ $(if $(BR2_NEEDS_GETTEXT),LDFLAGS=-lintl) \ DEBUG=false define CPUPOWER_BUILD_CMDS $(Q)if test ! -f $(@D)/tools/power/cpupower/Makefile ; then \ echo "Your kernel version is too old and does not have the cpupower tool." ; \ echo "At least kernel 3.4 must be used." ; \ exit 1 ; \ fi $(TARGET_MAKE_ENV) $(MAKE) -C $(@D)/tools \ $(CPUPOWER_MAKE_OPTS) \ cpupower endef define CPUPOWER_INSTALL_STAGING_CMDS $(TARGET_MAKE_ENV) $(MAKE) -C $(@D)/tools \ $(CPUPOWER_MAKE_OPTS) \ DESTDIR=$(STAGING_DIR) \ cpupower_install endef define CPUPOWER_INSTALL_TARGET_CMDS $(TARGET_MAKE_ENV) $(MAKE) -C $(@D)/tools \ $(CPUPOWER_MAKE_OPTS) \ DESTDIR=$(TARGET_DIR) \ cpupower_install endef
shibajee/buildroot
linux/linux-tool-cpupower.mk
mk
mit
1,056
################################################################################ # # perf # ################################################################################ LINUX_TOOLS += perf PERF_DEPENDENCIES = host-flex host-bison ifeq ($(KERNEL_ARCH),x86_64) PERF_ARCH=x86 else PERF_ARCH=$(KERNEL_ARCH) endif PERF_MAKE_FLAGS = \ $(LINUX_MAKE_FLAGS) \ JOBS=$(PARALLEL_JOBS) \ ARCH=$(PERF_ARCH) \ DESTDIR=$(TARGET_DIR) \ prefix=/usr \ WERROR=0 \ NO_LIBAUDIT=1 \ NO_NEWT=1 \ NO_GTK2=1 \ NO_LIBPERL=1 \ NO_LIBPYTHON=1 \ NO_LIBBIONIC=1 # We need to pass an argument to ld for setting the endianness when # building it for MIPS architecture, otherwise the default one will # always be used (which is big endian) and the compilation for little # endian will always fail showing an error like this one: # LD foo.o # mips-linux-gnu-ld: foo.o: compiled for a little endian system and # target is big endian ifeq ($(BR2_mips)$(BR2_mips64),y) PERF_MAKE_FLAGS += LD="$(TARGET_LD) -EB" else ifeq ($(BR2_mipsel)$(BR2_mips64el),y) PERF_MAKE_FLAGS += LD="$(TARGET_LD) -EL" endif # The call to backtrace() function fails for ARC, because for some # reason the unwinder from libgcc returns early. Thus the usage of # backtrace() should be disabled in perf explicitly: at build time # backtrace() appears to be available, but it fails at runtime: the # backtrace will contain only several functions from the top of stack, # instead of the complete backtrace. ifeq ($(BR2_arc),y) PERF_MAKE_FLAGS += NO_BACKTRACE=1 endif ifeq ($(BR2_PACKAGE_SLANG),y) PERF_DEPENDENCIES += slang else PERF_MAKE_FLAGS += NO_SLANG=1 endif ifeq ($(BR2_PACKAGE_LIBUNWIND),y) PERF_DEPENDENCIES += libunwind else PERF_MAKE_FLAGS += NO_LIBUNWIND=1 endif ifeq ($(BR2_PACKAGE_NUMACTL),y) PERF_DEPENDENCIES += numactl else PERF_MAKE_FLAGS += NO_LIBNUMA=1 endif ifeq ($(BR2_PACKAGE_ELFUTILS),y) PERF_DEPENDENCIES += elfutils else PERF_MAKE_FLAGS += NO_LIBELF=1 NO_DWARF=1 endif ifeq ($(BR2_PACKAGE_ZLIB),y) PERF_DEPENDENCIES += zlib else PERF_MAKE_FLAGS += NO_ZLIB=1 endif # lzma is provided by xz ifeq ($(BR2_PACKAGE_XZ),y) PERF_DEPENDENCIES += xz else PERF_MAKE_FLAGS += NO_LZMA=1 endif # We really do not want to build the perf documentation, because it # has stringent requirement on the documentation generation tools, # like xmlto and asciidoc), which may be lagging behind on some # distributions. # We name it 'GNUmakefile' so that GNU make will use it instead of # the existing 'Makefile'. define PERF_DISABLE_DOCUMENTATION if [ -f $(@D)/tools/perf/Documentation/Makefile ]; then \ printf "%%:\n\t@:\n" >$(@D)/tools/perf/Documentation/GNUmakefile; \ fi endef LINUX_POST_PATCH_HOOKS += PERF_DISABLE_DOCUMENTATION # O must be redefined here to overwrite the one used by Buildroot for # out of tree build. We build perf in $(@D)/tools/perf/ and not just # $(@D) so that it isn't built in the root directory of the kernel # sources. define PERF_BUILD_CMDS $(Q)if test ! -f $(@D)/tools/perf/Makefile ; then \ echo "Your kernel version is too old and does not have the perf tool." ; \ echo "At least kernel 2.6.31 must be used." ; \ exit 1 ; \ fi $(Q)if test "$(BR2_PACKAGE_ELFUTILS)" = "" ; then \ if ! grep -q NO_LIBELF $(@D)/tools/perf/Makefile* ; then \ if ! test -r $(@D)/tools/perf/config/Makefile ; then \ echo "The perf tool in your kernel cannot be built without libelf." ; \ echo "Either upgrade your kernel to >= 3.7, or enable the elfutils package." ; \ exit 1 ; \ fi \ fi \ fi $(TARGET_MAKE_ENV) $(MAKE1) $(PERF_MAKE_FLAGS) \ -C $(@D)/tools/perf O=$(@D)/tools/perf/ endef # After installation, we remove the Perl and Python scripts from the # target. define PERF_INSTALL_TARGET_CMDS $(TARGET_MAKE_ENV) $(MAKE1) $(PERF_MAKE_FLAGS) \ -C $(@D)/tools/perf O=$(@D)/tools/perf/ install $(RM) -rf $(TARGET_DIR)/usr/libexec/perf-core/scripts/ $(RM) -rf $(TARGET_DIR)/usr/libexec/perf-core/tests/ endef
shibajee/buildroot
linux/linux-tool-perf.mk
mk
mit
3,938
################################################################################ # # selftests # ################################################################################ LINUX_TOOLS += selftests ifeq ($(KERNEL_ARCH),x86_64) SELFTESTS_ARCH=x86 else ifeq ($(KERNEL_ARCH),i386) SELFTESTS_ARCH=x86 else SELFTESTS_ARCH=$(KERNEL_ARCH) endif endif SELFTESTS_DEPENDENCIES = libcap-ng popt SELFTESTS_MAKE_FLAGS = \ $(LINUX_MAKE_FLAGS) \ ARCH=$(SELFTESTS_ARCH) # O must be redefined here to overwrite the one used by Buildroot for # out of tree build. We build the selftests in $(@D)/tools/selftests and # not just $(@D) so that it isn't built in the root directory of the kernel # sources. # # The headers_install step here is important as some kernel selftests use a # hardcoded CFLAGS to find kernel headers e.g: # CFLAGS += -I../../../../usr/include/ # The headers_install target will install the kernel headers locally inside # the Linux build dir define SELFTESTS_BUILD_CMDS $(TARGET_MAKE_ENV) $(MAKE1) -C $(@D) $(SELFTESTS_MAKE_FLAGS) \ headers_install $(TARGET_MAKE_ENV) $(MAKE1) -C $(@D)/tools/testing/selftests \ $(SELFTESTS_MAKE_FLAGS) O=$(@D)/tools/testing/selftests endef define SELFTESTS_INSTALL_TARGET_CMDS $(TARGET_MAKE_ENV) $(MAKE1) -C $(@D)/tools/testing/selftests \ $(SELFTESTS_MAKE_FLAGS) O=$(@D)/tools/testing/selftests \ INSTALL_PATH=$(TARGET_DIR)/usr/lib/kselftests install endef
shibajee/buildroot
linux/linux-tool-selftests.mk
mk
mit
1,420
################################################################################ # # Linux kernel target # ################################################################################ LINUX_VERSION = $(call qstrip,$(BR2_LINUX_KERNEL_VERSION)) LINUX_LICENSE = GPLv2 LINUX_LICENSE_FILES = COPYING define LINUX_HELP_CMDS @echo ' linux-menuconfig - Run Linux kernel menuconfig' @echo ' linux-savedefconfig - Run Linux kernel savedefconfig' @echo ' linux-update-defconfig - Save the Linux configuration to the path specified' @echo ' by BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE' endef # Compute LINUX_SOURCE and LINUX_SITE from the configuration ifeq ($(BR2_LINUX_KERNEL_CUSTOM_TARBALL),y) LINUX_TARBALL = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION)) LINUX_SITE = $(patsubst %/,%,$(dir $(LINUX_TARBALL))) LINUX_SOURCE = $(notdir $(LINUX_TARBALL)) BR_NO_CHECK_HASH_FOR += $(LINUX_SOURCE) else ifeq ($(BR2_LINUX_KERNEL_CUSTOM_LOCAL),y) LINUX_SITE = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_LOCAL_PATH)) LINUX_SITE_METHOD = local else ifeq ($(BR2_LINUX_KERNEL_CUSTOM_GIT),y) LINUX_SITE = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_REPO_URL)) LINUX_SITE_METHOD = git else ifeq ($(BR2_LINUX_KERNEL_CUSTOM_HG),y) LINUX_SITE = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_REPO_URL)) LINUX_SITE_METHOD = hg else ifeq ($(BR2_LINUX_KERNEL_CUSTOM_SVN),y) LINUX_SITE = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_REPO_URL)) LINUX_SITE_METHOD = svn else LINUX_SOURCE = linux-$(LINUX_VERSION).tar.xz ifeq ($(BR2_LINUX_KERNEL_CUSTOM_VERSION),y) BR_NO_CHECK_HASH_FOR += $(LINUX_SOURCE) endif # In X.Y.Z, get X and Y. We replace dots and dashes by spaces in order # to use the $(word) function. We support versions such as 4.0, 3.1, # 2.6.32, 2.6.32-rc1, 3.0-rc6, etc. ifeq ($(findstring x2.6.,x$(LINUX_VERSION)),x2.6.) LINUX_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v2.6 else ifeq ($(findstring x3.,x$(LINUX_VERSION)),x3.) LINUX_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v3.x else ifeq ($(findstring x4.,x$(LINUX_VERSION)),x4.) LINUX_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v4.x endif # release candidates are in testing/ subdir ifneq ($(findstring -rc,$(LINUX_VERSION)),) LINUX_SITE := $(LINUX_SITE)/testing endif # -rc endif LINUX_PATCHES = $(call qstrip,$(BR2_LINUX_KERNEL_PATCH)) # We rely on the generic package infrastructure to download and apply # remote patches (downloaded from ftp, http or https). For local # patches, we can't rely on that infrastructure, because there might # be directories in the patch list (unlike for other packages). LINUX_PATCH = $(filter ftp://% http://% https://%,$(LINUX_PATCHES)) LINUX_INSTALL_IMAGES = YES LINUX_DEPENDENCIES += host-kmod # host tools needed for kernel compression ifeq ($(BR2_LINUX_KERNEL_LZ4),y) LINUX_DEPENDENCIES += host-lz4 else ifeq ($(BR2_LINUX_KERNEL_LZMA),y) LINUX_DEPENDENCIES += host-lzma else ifeq ($(BR2_LINUX_KERNEL_LZO),y) LINUX_DEPENDENCIES += host-lzop else ifeq ($(BR2_LINUX_KERNEL_XZ),y) LINUX_DEPENDENCIES += host-xz endif LINUX_COMPRESSION_OPT_$(BR2_LINUX_KERNEL_GZIP) = CONFIG_KERNEL_GZIP LINUX_COMPRESSION_OPT_$(BR2_LINUX_KERNEL_LZ4) = CONFIG_KERNEL_LZ4 LINUX_COMPRESSION_OPT_$(BR2_LINUX_KERNEL_LZMA) = CONFIG_KERNEL_LZMA LINUX_COMPRESSION_OPT_$(BR2_LINUX_KERNEL_LZO) = CONFIG_KERNEL_LZO LINUX_COMPRESSION_OPT_$(BR2_LINUX_KERNEL_XZ) = CONFIG_KERNEL_XZ ifeq ($(BR2_LINUX_KERNEL_UBOOT_IMAGE),y) LINUX_DEPENDENCIES += host-uboot-tools endif LINUX_MAKE_FLAGS = \ HOSTCC="$(HOSTCC)" \ HOSTCFLAGS="$(HOSTCFLAGS)" \ ARCH=$(KERNEL_ARCH) \ INSTALL_MOD_PATH=$(TARGET_DIR) \ CROSS_COMPILE="$(TARGET_CROSS)" \ DEPMOD=$(HOST_DIR)/sbin/depmod LINUX_MAKE_ENV = \ $(TARGET_MAKE_ENV) \ BR_BINARIES_DIR=$(BINARIES_DIR) # Get the real Linux version, which tells us where kernel modules are # going to be installed in the target filesystem. LINUX_VERSION_PROBED = `$(MAKE) $(LINUX_MAKE_FLAGS) -C $(LINUX_DIR) --no-print-directory -s kernelrelease 2>/dev/null` ifeq ($(BR2_LINUX_KERNEL_USE_INTREE_DTS),y) KERNEL_DTS_NAME = $(call qstrip,$(BR2_LINUX_KERNEL_INTREE_DTS_NAME)) else ifeq ($(BR2_LINUX_KERNEL_USE_CUSTOM_DTS),y) # We keep only the .dts files, so that the user can specify both .dts # and .dtsi files in BR2_LINUX_KERNEL_CUSTOM_DTS_PATH. Both will be # copied to arch/<arch>/boot/dts, but only the .dts files will # actually be generated as .dtb. KERNEL_DTS_NAME = $(basename $(filter %.dts,$(notdir $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_DTS_PATH))))) endif KERNEL_DTBS = $(addsuffix .dtb,$(KERNEL_DTS_NAME)) ifeq ($(BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM),y) LINUX_IMAGE_NAME = $(call qstrip,$(BR2_LINUX_KERNEL_IMAGE_NAME)) LINUX_TARGET_NAME = $(call qstrip,$(BR2_LINUX_KERNEL_IMAGE_TARGET_NAME)) ifeq ($(LINUX_IMAGE_NAME),) LINUX_IMAGE_NAME = $(LINUX_TARGET_NAME) endif else ifeq ($(BR2_LINUX_KERNEL_UIMAGE),y) LINUX_IMAGE_NAME = uImage else ifeq ($(BR2_LINUX_KERNEL_APPENDED_UIMAGE),y) LINUX_IMAGE_NAME = uImage else ifeq ($(BR2_LINUX_KERNEL_BZIMAGE),y) LINUX_IMAGE_NAME = bzImage else ifeq ($(BR2_LINUX_KERNEL_ZIMAGE),y) LINUX_IMAGE_NAME = zImage else ifeq ($(BR2_LINUX_KERNEL_ZIMAGE_EPAPR),y) LINUX_IMAGE_NAME = zImage.epapr else ifeq ($(BR2_LINUX_KERNEL_APPENDED_ZIMAGE),y) LINUX_IMAGE_NAME = zImage else ifeq ($(BR2_LINUX_KERNEL_CUIMAGE),y) LINUX_IMAGE_NAME = cuImage.$(KERNEL_DTS_NAME) else ifeq ($(BR2_LINUX_KERNEL_SIMPLEIMAGE),y) LINUX_IMAGE_NAME = simpleImage.$(KERNEL_DTS_NAME) else ifeq ($(BR2_LINUX_KERNEL_IMAGE),y) LINUX_IMAGE_NAME = Image else ifeq ($(BR2_LINUX_KERNEL_LINUX_BIN),y) LINUX_IMAGE_NAME = linux.bin else ifeq ($(BR2_LINUX_KERNEL_VMLINUX_BIN),y) LINUX_IMAGE_NAME = vmlinux.bin else ifeq ($(BR2_LINUX_KERNEL_VMLINUX),y) LINUX_IMAGE_NAME = vmlinux else ifeq ($(BR2_LINUX_KERNEL_VMLINUZ),y) LINUX_IMAGE_NAME = vmlinuz else ifeq ($(BR2_LINUX_KERNEL_VMLINUZ_BIN),y) LINUX_IMAGE_NAME = vmlinuz.bin endif # The if-else blocks above are all the image types we know of, and all # come from a Kconfig choice, so we know we have LINUX_IMAGE_NAME set # to something LINUX_TARGET_NAME = $(LINUX_IMAGE_NAME) endif LINUX_KERNEL_UIMAGE_LOADADDR = $(call qstrip,$(BR2_LINUX_KERNEL_UIMAGE_LOADADDR)) ifneq ($(LINUX_KERNEL_UIMAGE_LOADADDR),) LINUX_MAKE_FLAGS += LOADADDR="$(LINUX_KERNEL_UIMAGE_LOADADDR)" endif # Compute the arch path, since i386 and x86_64 are in arch/x86 and not # in arch/$(KERNEL_ARCH). Even if the kernel creates symbolic links # for bzImage, arch/i386 and arch/x86_64 do not exist when copying the # defconfig file. ifeq ($(KERNEL_ARCH),i386) KERNEL_ARCH_PATH = $(LINUX_DIR)/arch/x86 else ifeq ($(KERNEL_ARCH),x86_64) KERNEL_ARCH_PATH = $(LINUX_DIR)/arch/x86 else KERNEL_ARCH_PATH = $(LINUX_DIR)/arch/$(KERNEL_ARCH) endif ifeq ($(BR2_LINUX_KERNEL_VMLINUX),y) LINUX_IMAGE_PATH = $(LINUX_DIR)/$(LINUX_IMAGE_NAME) else ifeq ($(BR2_LINUX_KERNEL_VMLINUZ),y) LINUX_IMAGE_PATH = $(LINUX_DIR)/$(LINUX_IMAGE_NAME) else ifeq ($(BR2_LINUX_KERNEL_VMLINUZ_BIN),y) LINUX_IMAGE_PATH = $(LINUX_DIR)/$(LINUX_IMAGE_NAME) else LINUX_IMAGE_PATH = $(KERNEL_ARCH_PATH)/boot/$(LINUX_IMAGE_NAME) endif # BR2_LINUX_KERNEL_VMLINUX define LINUX_APPLY_LOCAL_PATCHES for p in $(filter-out ftp://% http://% https://%,$(LINUX_PATCHES)) ; do \ if test -d $$p ; then \ $(APPLY_PATCHES) $(@D) $$p \*.patch || exit 1 ; \ else \ $(APPLY_PATCHES) $(@D) `dirname $$p` `basename $$p` || exit 1; \ fi \ done endef LINUX_POST_PATCH_HOOKS += LINUX_APPLY_LOCAL_PATCHES # Older linux kernels use deprecated perl constructs in timeconst.pl # that were removed for perl 5.22+ so it breaks on newer distributions # Try a dry-run patch to see if this applies, if it does go ahead define LINUX_TRY_PATCH_TIMECONST @if patch -p1 --dry-run -f -s -d $(@D) <$(LINUX_PKGDIR)/0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional >/dev/null ; then \ $(APPLY_PATCHES) $(@D) $(LINUX_PKGDIR) 0001-timeconst.pl-Eliminate-Perl-warning.patch.conditional ; \ fi endef LINUX_POST_PATCH_HOOKS += LINUX_TRY_PATCH_TIMECONST ifeq ($(BR2_LINUX_KERNEL_USE_DEFCONFIG),y) LINUX_KCONFIG_DEFCONFIG = $(call qstrip,$(BR2_LINUX_KERNEL_DEFCONFIG))_defconfig else ifeq ($(BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG),y) LINUX_KCONFIG_DEFCONFIG = defconfig else ifeq ($(BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG),y) LINUX_KCONFIG_FILE = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE)) endif LINUX_KCONFIG_FRAGMENT_FILES = $(call qstrip,$(BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES)) LINUX_KCONFIG_EDITORS = menuconfig xconfig gconfig nconfig LINUX_KCONFIG_OPTS = $(LINUX_MAKE_FLAGS) # If no package has yet set it, set it from the Kconfig option LINUX_NEEDS_MODULES ?= $(BR2_LINUX_NEEDS_MODULES) # Make sure the Linux kernel is built with the right endianness. Not # all architectures support # CONFIG_CPU_BIG_ENDIAN/CONFIG_CPU_LITTLE_ENDIAN in Linux, but the # option will be thrown away and ignored if it doesn't exist. ifeq ($(BR2_ENDIAN),"BIG") define LINUX_FIXUP_CONFIG_ENDIANNESS $(call KCONFIG_ENABLE_OPT,CONFIG_CPU_BIG_ENDIAN,$(@D)/.config) endef else define LINUX_FIXUP_CONFIG_ENDIANNESS $(call KCONFIG_ENABLE_OPT,CONFIG_CPU_LITTLE_ENDIAN,$(@D)/.config) endef endif define LINUX_KCONFIG_FIXUP_CMDS $(if $(LINUX_NEEDS_MODULES), $(call KCONFIG_ENABLE_OPT,CONFIG_MODULES,$(@D)/.config)) $(call KCONFIG_ENABLE_OPT,$(LINUX_COMPRESSION_OPT_y),$(@D)/.config) $(foreach opt, $(LINUX_COMPRESSION_OPT_), $(call KCONFIG_DISABLE_OPT,$(opt),$(@D)/.config) ) $(LINUX_FIXUP_CONFIG_ENDIANNESS) $(if $(BR2_arm)$(BR2_armeb), $(call KCONFIG_ENABLE_OPT,CONFIG_AEABI,$(@D)/.config)) $(if $(BR2_TARGET_ROOTFS_CPIO), $(call KCONFIG_ENABLE_OPT,CONFIG_BLK_DEV_INITRD,$(@D)/.config)) # As the kernel gets compiled before root filesystems are # built, we create a fake cpio file. It'll be # replaced later by the real cpio archive, and the kernel will be # rebuilt using the linux-rebuild-with-initramfs target. $(if $(BR2_TARGET_ROOTFS_INITRAMFS), touch $(BINARIES_DIR)/rootfs.cpio $(call KCONFIG_SET_OPT,CONFIG_INITRAMFS_SOURCE,"$${BR_BINARIES_DIR}/rootfs.cpio",$(@D)/.config) $(call KCONFIG_SET_OPT,CONFIG_INITRAMFS_ROOT_UID,0,$(@D)/.config) $(call KCONFIG_SET_OPT,CONFIG_INITRAMFS_ROOT_GID,0,$(@D)/.config)) $(if $(BR2_ROOTFS_DEVICE_CREATION_STATIC),, $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config)) $(if $(BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV), $(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config)) $(if $(BR2_PACKAGE_KTAP), $(call KCONFIG_ENABLE_OPT,CONFIG_DEBUG_FS,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_ENABLE_DEFAULT_TRACERS,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_PERF_EVENTS,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_FUNCTION_TRACER,$(@D)/.config)) $(if $(BR2_PACKAGE_SYSTEMD), $(call KCONFIG_ENABLE_OPT,CONFIG_CGROUPS,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_FHANDLE,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_AUTOFS4_FS,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_TMPFS_POSIX_ACL,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_TMPFS_POSIX_XATTR,$(@D)/.config)) $(if $(BR2_PACKAGE_SMACK), $(call KCONFIG_ENABLE_OPT,CONFIG_SECURITY,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_SECURITY_SMACK,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_SECURITY_NETWORK,$(@D)/.config)) $(if $(BR2_PACKAGE_IPTABLES), $(call KCONFIG_ENABLE_OPT,CONFIG_IP_NF_IPTABLES,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_IP_NF_FILTER,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_NETFILTER,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_NETFILTER_XTABLES,$(@D)/.config)) $(if $(BR2_PACKAGE_XTABLES_ADDONS), $(call KCONFIG_ENABLE_OPT,CONFIG_NETFILTER_ADVANCED,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_NF_CONNTRACK,$(@D)/.config) $(call KCONFIG_ENABLE_OPT,CONFIG_NF_CONNTRACK_MARK,$(@D)/.config)) $(if $(BR2_LINUX_KERNEL_APPENDED_DTB), $(call KCONFIG_ENABLE_OPT,CONFIG_ARM_APPENDED_DTB,$(@D)/.config)) $(if $(BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV), $(call KCONFIG_DISABLE_OPT,CONFIG_MXC_GPU_VIV,$(@D)/.config)) endef ifeq ($(BR2_LINUX_KERNEL_DTS_SUPPORT),y) ifeq ($(BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT),) define LINUX_BUILD_DTB $(LINUX_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) $(KERNEL_DTBS) endef ifeq ($(BR2_LINUX_KERNEL_APPENDED_DTB),) define LINUX_INSTALL_DTB # dtbs moved from arch/<ARCH>/boot to arch/<ARCH>/boot/dts since 3.8-rc1 cp $(addprefix \ $(KERNEL_ARCH_PATH)/boot/$(if $(wildcard \ $(addprefix $(KERNEL_ARCH_PATH)/boot/dts/,$(KERNEL_DTBS))),dts/),$(KERNEL_DTBS)) \ $(1) endef endif # BR2_LINUX_KERNEL_APPENDED_DTB endif # BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT endif # BR2_LINUX_KERNEL_DTS_SUPPORT ifeq ($(BR2_LINUX_KERNEL_APPENDED_DTB),y) # dtbs moved from arch/$ARCH/boot to arch/$ARCH/boot/dts since 3.8-rc1 define LINUX_APPEND_DTB (cd $(KERNEL_ARCH_PATH)/boot; \ for dtb in $(KERNEL_DTS_NAME); do \ if test -e $${dtb}.dtb ; then \ dtbpath=$${dtb}.dtb ; \ else \ dtbpath=dts/$${dtb}.dtb ; \ fi ; \ cat zImage $${dtbpath} > zImage.$${dtb} || exit 1; \ done) endef ifeq ($(BR2_LINUX_KERNEL_APPENDED_UIMAGE),y) # We need to generate a new u-boot image that takes into # account the extra-size added by the device tree at the end # of the image. To do so, we first need to retrieve both load # address and entry point for the kernel from the already # generate uboot image before using mkimage -l. LINUX_APPEND_DTB += ; \ MKIMAGE_ARGS=`$(MKIMAGE) -l $(LINUX_IMAGE_PATH) |\ sed -n -e 's/Image Name:[ ]*\(.*\)/-n \1/p' -e 's/Load Address:/-a/p' -e 's/Entry Point:/-e/p'`; \ for dtb in $(KERNEL_DTS_NAME); do \ $(MKIMAGE) -A $(MKIMAGE_ARCH) -O linux \ -T kernel -C none $${MKIMAGE_ARGS} \ -d $(KERNEL_ARCH_PATH)/boot/zImage.$${dtb} $(LINUX_IMAGE_PATH).$${dtb}; \ done endif endif # Compilation. We make sure the kernel gets rebuilt when the # configuration has changed. define LINUX_BUILD_CMDS $(if $(BR2_LINUX_KERNEL_USE_CUSTOM_DTS), cp -f $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_DTS_PATH)) $(KERNEL_ARCH_PATH)/boot/dts/) $(LINUX_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) $(LINUX_TARGET_NAME) @if grep -q "CONFIG_MODULES=y" $(@D)/.config; then \ $(LINUX_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) modules ; \ fi $(LINUX_BUILD_DTB) $(LINUX_APPEND_DTB) endef ifeq ($(BR2_LINUX_KERNEL_APPENDED_DTB),y) # When a DTB was appended, install the potential several images with # appended DTBs. define LINUX_INSTALL_IMAGE mkdir -p $(1) cp $(KERNEL_ARCH_PATH)/boot/$(LINUX_IMAGE_NAME).* $(1) endef else # Otherwise, just install the unique image generated by the kernel # build process. define LINUX_INSTALL_IMAGE $(INSTALL) -m 0644 -D $(LINUX_IMAGE_PATH) $(1)/$(LINUX_IMAGE_NAME) endef endif ifeq ($(BR2_LINUX_KERNEL_INSTALL_TARGET),y) define LINUX_INSTALL_KERNEL_IMAGE_TO_TARGET $(call LINUX_INSTALL_IMAGE,$(TARGET_DIR)/boot) $(call LINUX_INSTALL_DTB,$(TARGET_DIR)/boot) endef endif define LINUX_INSTALL_HOST_TOOLS # Installing dtc (device tree compiler) as host tool, if selected if grep -q "CONFIG_DTC=y" $(@D)/.config; then \ $(INSTALL) -D -m 0755 $(@D)/scripts/dtc/dtc $(HOST_DIR)/usr/bin/linux-dtc ; \ if [ ! -e $(HOST_DIR)/usr/bin/dtc ]; then \ ln -sf linux-dtc $(HOST_DIR)/usr/bin/dtc ; \ fi \ fi endef define LINUX_INSTALL_IMAGES_CMDS $(call LINUX_INSTALL_IMAGE,$(BINARIES_DIR)) $(call LINUX_INSTALL_DTB,$(BINARIES_DIR)) endef define LINUX_INSTALL_TARGET_CMDS $(LINUX_INSTALL_KERNEL_IMAGE_TO_TARGET) # Install modules and remove symbolic links pointing to build # directories, not relevant on the target @if grep -q "CONFIG_MODULES=y" $(@D)/.config; then \ $(LINUX_MAKE_ENV) $(MAKE1) $(LINUX_MAKE_FLAGS) -C $(@D) modules_install; \ rm -f $(TARGET_DIR)/lib/modules/$(LINUX_VERSION_PROBED)/build ; \ rm -f $(TARGET_DIR)/lib/modules/$(LINUX_VERSION_PROBED)/source ; \ fi $(LINUX_INSTALL_HOST_TOOLS) endef # Include all our extensions and tools definitions. # # Note: our package infrastructure uses the full-path of the last-scanned # Makefile to determine what package we're currently defining, using the # last directory component in the path. As such, including other Makefile, # like below, before we call one of the *-package macro is usally not # working. # However, since the files we include here are in the same directory as # the current Makefile, we are OK. But this is a hard requirement: files # included here *must* be in the same directory! include $(sort $(wildcard linux/linux-ext-*.mk)) include $(sort $(wildcard linux/linux-tool-*.mk)) LINUX_PATCH_DEPENDENCIES += $(foreach ext,$(LINUX_EXTENSIONS),\ $(if $(BR2_LINUX_KERNEL_EXT_$(call UPPERCASE,$(ext))),$(ext))) LINUX_PRE_PATCH_HOOKS += $(foreach ext,$(LINUX_EXTENSIONS),\ $(if $(BR2_LINUX_KERNEL_EXT_$(call UPPERCASE,$(ext))),\ $(call UPPERCASE,$(ext))_PREPARE_KERNEL)) # Install Linux kernel tools in the staging directory since some tools # may install shared libraries and headers (e.g. cpupower). The kernel # image is NOT installed in the staging directory. LINUX_INSTALL_STAGING = YES LINUX_DEPENDENCIES += $(foreach tool,$(LINUX_TOOLS),\ $(if $(BR2_LINUX_KERNEL_TOOL_$(call UPPERCASE,$(tool))),\ $($(call UPPERCASE,$(tool))_DEPENDENCIES))) LINUX_POST_BUILD_HOOKS += $(foreach tool,$(LINUX_TOOLS),\ $(if $(BR2_LINUX_KERNEL_TOOL_$(call UPPERCASE,$(tool))),\ $(call UPPERCASE,$(tool))_BUILD_CMDS)) LINUX_POST_INSTALL_STAGING_HOOKS += $(foreach tool,$(LINUX_TOOLS),\ $(if $(BR2_LINUX_KERNEL_TOOL_$(call UPPERCASE,$(tool))),\ $(call UPPERCASE,$(tool))_INSTALL_STAGING_CMDS)) LINUX_POST_INSTALL_TARGET_HOOKS += $(foreach tool,$(LINUX_TOOLS),\ $(if $(BR2_LINUX_KERNEL_TOOL_$(call UPPERCASE,$(tool))),\ $(call UPPERCASE,$(tool))_INSTALL_TARGET_CMDS)) # Checks to give errors that the user can understand ifeq ($(BR_BUILDING),y) ifeq ($(BR2_LINUX_KERNEL_USE_DEFCONFIG),y) # We must use the user-supplied kconfig value, because # LINUX_KCONFIG_DEFCONFIG will at least contain the # trailing _defconfig ifeq ($(call qstrip,$(BR2_LINUX_KERNEL_DEFCONFIG)),) $(error No kernel defconfig name specified, check your BR2_LINUX_KERNEL_DEFCONFIG setting) endif endif ifeq ($(BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG),y) ifeq ($(LINUX_KCONFIG_FILE),) $(error No kernel configuration file specified, check your BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE setting) endif endif ifeq ($(BR2_LINUX_KERNEL_DTS_SUPPORT)$(KERNEL_DTS_NAME),y) $(error No kernel device tree source specified, check your \ BR2_LINUX_KERNEL_USE_INTREE_DTS / BR2_LINUX_KERNEL_USE_CUSTOM_DTS settings) endif endif # BR_BUILDING $(eval $(kconfig-package)) # Support for rebuilding the kernel after the cpio archive has # been generated in $(BINARIES_DIR)/rootfs.cpio. $(LINUX_DIR)/.stamp_initramfs_rebuilt: $(LINUX_DIR)/.stamp_target_installed $(LINUX_DIR)/.stamp_images_installed $(BINARIES_DIR)/rootfs.cpio @$(call MESSAGE,"Rebuilding kernel with initramfs") # Build the kernel. $(LINUX_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) $(LINUX_TARGET_NAME) $(LINUX_APPEND_DTB) # Copy the kernel image(s) to its(their) final destination $(call LINUX_INSTALL_IMAGE,$(BINARIES_DIR)) # If there is a .ub file copy it to the final destination test ! -f $(LINUX_IMAGE_PATH).ub || cp $(LINUX_IMAGE_PATH).ub $(BINARIES_DIR) $(Q)touch $@ # The initramfs building code must make sure this target gets called # after it generated the initramfs list of files. linux-rebuild-with-initramfs: $(LINUX_DIR)/.stamp_initramfs_rebuilt
shibajee/buildroot
linux/linux.mk
mk
mit
19,437
avoid regen during install Signed-off-by: Francois Perrad <francois.perrad@gadz.org> --- a/sources/Makefile +++ b/sources/Makefile @@ -120,7 +120,7 @@ ln -sf $(SHARED_LIB) $(LIBRARIES)/lib4th.so endif -mostlyinstall: libinstall all +mostlyinstall: libinstall cp 4th 4tsh pp4th $(BINARIES) install: mostlyinstall --
shibajee/buildroot
package/4th/0001-avoid-regen-during-install.patch
patch
mit
329
# Locally computed: sha256 1c7adbb1a56dad4c4c781e6e023d77ac862842560c05246b691d07e9a4460ab2 4th-3.62.4-unix.tar.gz
shibajee/buildroot
package/4th/4th.hash
hash
mit
117
################################################################################ # # 4th # ################################################################################ 4TH_VERSION = 3.62.4 4TH_SOURCE = 4th-$(4TH_VERSION)-unix.tar.gz 4TH_SITE = http://downloads.sourceforge.net/project/forth-4th/4th-$(4TH_VERSION) 4TH_LICENSE = GPLv3+, LGPLv3+ # The COPYING file only contains the text of the LGPLv3, but the # source code really contains parts under GPLv3+. 4TH_LICENSE_FILES = COPYING 4TH_DEPENDENCIES = host-4th 4TH_INSTALL_STAGING = YES 4TH_CFLAGS = $(TARGET_CFLAGS) -DUNIX -fsigned-char ifeq ($(BR2_STATIC_LIBS),y) 4TH_MAKE_ENV = STATIC=1 else 4TH_MAKE_ENV = SHARED=1 4TH_CFLAGS += -fPIC endif define 4TH_BUILD_CMDS $(4TH_MAKE_ENV) $(MAKE) -C $(@D)/sources all \ CROSS="$(TARGET_CROSS)" \ CFLAGS="$(4TH_CFLAGS)" \ FOURTH=$(HOST_DIR)/usr/bin/4th endef define 4TH_INSTALL_STAGING_CMDS $(4TH_MAKE_ENV) $(MAKE) -C $(@D)/sources libinstall \ LIBRARIES=$(STAGING_DIR)/usr/lib $(INSTALL) -D -m 0644 $(@D)/sources/4th.h \ $(STAGING_DIR)/usr/include/4th.h endef define 4TH_INSTALL_TARGET_CMDS mkdir -p $(TARGET_DIR)/usr/bin mkdir -p $(TARGET_DIR)/usr/lib $(4TH_MAKE_ENV) $(MAKE) -C $(@D)/sources mostlyinstall \ BINARIES=$(TARGET_DIR)/usr/bin \ LIBRARIES=$(TARGET_DIR)/usr/lib mkdir -p $(TARGET_DIR)/usr/share/4th/lib cp -dpf $(@D)/4th/*.4th $(TARGET_DIR)/usr/share/4th cp -dpf $(@D)/4th/lib/*.4th $(TARGET_DIR)/usr/share/4th/lib mkdir -p $(TARGET_DIR)/usr/share/4th/demo cp -dpf $(@D)/4th/demo/*.4th $(TARGET_DIR)/usr/share/4th/demo mkdir -p $(TARGET_DIR)/usr/share/4th/4pp/lib cp -dpf $(@D)/4th/4pp/*.4pp $(TARGET_DIR)/usr/share/4th/4pp cp -dpf $(@D)/4th/4pp/lib/*.4pp $(TARGET_DIR)/usr/share/4th/4pp/lib endef define HOST_4TH_BUILD_CMDS $(MAKE) -C $(@D)/sources all \ CFLAGS="$(HOST_CFLAGS) -DUNIX -fsigned-char" endef define HOST_4TH_INSTALL_CMDS mkdir -p $(HOST_DIR)/usr/bin mkdir -p $(HOST_DIR)/usr/lib $(MAKE) -C $(@D)/sources mostlyinstall \ BINARIES=$(HOST_DIR)/usr/bin \ LIBRARIES=$(HOST_DIR)/usr/lib endef $(eval $(generic-package)) $(eval $(host-generic-package))
shibajee/buildroot
package/4th/4th.mk
mk
mit
2,123
config BR2_PACKAGE_4TH bool "4th" help 4tH is a Forth compiler that can create bytecode, C-embeddable bytecode, standalone executables, but also works fine as a scripting language http://thebeez.home.xs4all.nl/4tH/
shibajee/buildroot
package/4th/Config.in
in
mit
230
menu "Target packages" source "package/busybox/Config.in" source "package/skeleton/Config.in" menu "Audio and video applications" source "package/alsa-utils/Config.in" source "package/aumix/Config.in" source "package/bellagio/Config.in" source "package/dvblast/Config.in" source "package/dvdauthor/Config.in" source "package/dvdrw-tools/Config.in" source "package/espeak/Config.in" source "package/faad2/Config.in" source "package/ffmpeg/Config.in" source "package/flac/Config.in" source "package/flite/Config.in" source "package/gmrender-resurrect/Config.in" source "package/gstreamer/Config.in" source "package/gstreamer1/Config.in" source "package/jack2/Config.in" source "package/kodi/Config.in" source "package/lame/Config.in" source "package/madplay/Config.in" source "package/miraclecast/Config.in" source "package/mjpegtools/Config.in" source "package/modplugtools/Config.in" source "package/mpd/Config.in" source "package/mpd-mpc/Config.in" source "package/mpg123/Config.in" source "package/mplayer/Config.in" source "package/mpv/Config.in" source "package/multicat/Config.in" source "package/musepack/Config.in" source "package/ncmpc/Config.in" source "package/omxplayer/Config.in" source "package/on2-8170-libs/Config.in" source "package/opus-tools/Config.in" source "package/pulseaudio/Config.in" source "package/sox/Config.in" source "package/squeezelite/Config.in" source "package/tidsp-binaries/Config.in" source "package/tovid/Config.in" source "package/tstools/Config.in" source "package/twolame/Config.in" source "package/upmpdcli/Config.in" source "package/v4l2grab/Config.in" source "package/vlc/Config.in" source "package/vorbis-tools/Config.in" source "package/wavpack/Config.in" source "package/yavta/Config.in" source "package/ympd/Config.in" endmenu menu "Compressors and decompressors" source "package/bzip2/Config.in" source "package/gzip/Config.in" source "package/lz4/Config.in" source "package/lzip/Config.in" source "package/lzop/Config.in" source "package/p7zip/Config.in" source "package/unrar/Config.in" source "package/unzip/Config.in" source "package/xz/Config.in" source "package/zip/Config.in" endmenu menu "Debugging, profiling and benchmark" source "package/blktrace/Config.in" source "package/bonnie/Config.in" source "package/cache-calibrator/Config.in" source "package/dhrystone/Config.in" source "package/dmalloc/Config.in" source "package/dropwatch/Config.in" source "package/dstat/Config.in" source "package/dt/Config.in" source "package/duma/Config.in" source "package/fio/Config.in" source "package/gdb/Config.in" source "package/google-breakpad/Config.in" source "package/iozone/Config.in" source "package/kexec/Config.in" source "package/kexec-lite/Config.in" source "package/ktap/Config.in" source "package/kyua/Config.in" source "package/latencytop/Config.in" source "package/lmbench/Config.in" source "package/lsof/Config.in" source "package/ltp-testsuite/Config.in" source "package/ltrace/Config.in" source "package/lttng-babeltrace/Config.in" source "package/lttng-modules/Config.in" source "package/lttng-tools/Config.in" source "package/mcelog/Config.in" source "package/memstat/Config.in" source "package/netperf/Config.in" source "package/netsniff-ng/Config.in" source "package/oprofile/Config.in" source "package/pax-utils/Config.in" source "package/pv/Config.in" source "package/racehound/Config.in" source "package/ramsmp/Config.in" source "package/ramspeed/Config.in" source "package/rt-tests/Config.in" source "package/spidev_test/Config.in" source "package/strace/Config.in" source "package/stress/Config.in" source "package/stress-ng/Config.in" source "package/sysdig/Config.in" source "package/sysprof/Config.in" source "package/tinymembench/Config.in" source "package/trace-cmd/Config.in" source "package/trinity/Config.in" source "package/valgrind/Config.in" source "package/whetstone/Config.in" endmenu menu "Development tools" source "package/binutils/Config.in" source "package/bsdiff/Config.in" source "package/bustle/Config.in" source "package/check/Config.in" source "package/cmake/Config.in" source "package/cppunit/Config.in" source "package/cvs/Config.in" source "package/cxxtest/Config.in" source "package/diffutils/Config.in" source "package/dos2unix/Config.in" source "package/findutils/Config.in" source "package/flex/Config.in" source "package/gawk/Config.in" source "package/gettext/Config.in" source "package/git/Config.in" source "package/gperf/Config.in" source "package/grep/Config.in" source "package/intltool/Config.in" source "package/jq/Config.in" source "package/libtool/Config.in" source "package/make/Config.in" source "package/patch/Config.in" source "package/pkgconf/Config.in" source "package/sed/Config.in" source "package/sstrip/Config.in" source "package/subversion/Config.in" source "package/tree/Config.in" source "package/yasm/Config.in" endmenu menu "Filesystem and flash utilities" source "package/autofs/Config.in" source "package/btrfs-progs/Config.in" source "package/cifs-utils/Config.in" source "package/cpio/Config.in" source "package/cramfs/Config.in" source "package/curlftpfs/Config.in" source "package/dosfstools/Config.in" source "package/e2fsprogs/Config.in" source "package/e2tools/Config.in" source "package/ecryptfs-utils/Config.in" source "package/exfat/Config.in" source "package/exfat-utils/Config.in" source "package/f2fs-tools/Config.in" source "package/flashbench/Config.in" source "package/fwup/Config.in" source "package/genext2fs/Config.in" source "package/genpart/Config.in" source "package/genromfs/Config.in" source "package/makedevs/Config.in" source "package/mmc-utils/Config.in" source "package/mtd/Config.in" source "package/mtools/Config.in" source "package/nfs-utils/Config.in" source "package/ntfs-3g/Config.in" source "package/simicsfs/Config.in" source "package/sp-oops-extract/Config.in" source "package/squashfs/Config.in" source "package/sshfs/Config.in" source "package/sunxi-tools/Config.in" source "package/unionfs/Config.in" source "package/xfsprogs/Config.in" endmenu menu "Fonts, cursors, icons, sounds and themes" comment "Cursors" source "package/comix-cursors/Config.in" source "package/obsidian-cursors/Config.in" comment "Fonts" source "package/bitstream-vera/Config.in" source "package/cantarell/Config.in" source "package/dejavu/Config.in" source "package/font-awesome/Config.in" source "package/ghostscript-fonts/Config.in" source "package/inconsolata/Config.in" source "package/liberation/Config.in" comment "Icons" source "package/adwaita-icon-theme/Config.in" source "package/google-material-design-icons/Config.in" source "package/hicolor-icon-theme/Config.in" comment "Sounds" source "package/sound-theme-borealis/Config.in" source "package/sound-theme-freedesktop/Config.in" comment "Themes" source "package/gtk2-engines/Config.in" endmenu menu "Games" source "package/chocolate-doom/Config.in" source "package/doom-wad/Config.in" source "package/gnuchess/Config.in" source "package/lbreakout2/Config.in" source "package/ltris/Config.in" source "package/opentyrian/Config.in" source "package/opentyrian-data/Config.in" source "package/prboom/Config.in" source "package/rubix/Config.in" source "package/sl/Config.in" source "package/stella/Config.in" source "package/supertuxkart/Config.in" endmenu menu "Graphic libraries and applications (graphic/text)" comment "Graphic applications" source "package/expedite/Config.in" source "package/fswebcam/Config.in" source "package/glmark2/Config.in" source "package/gnuplot/Config.in" source "package/jhead/Config.in" source "package/mesa3d-demos/Config.in" source "package/qt5cinex/Config.in" source "package/rrdtool/Config.in" comment "Graphic libraries" source "package/cegui06/Config.in" source "package/directfb/Config.in" source "package/directfb-examples/Config.in" source "package/efl/Config.in" source "package/elementary/Config.in" source "package/fbdump/Config.in" source "package/fbgrab/Config.in" source "package/fbset/Config.in" source "package/fb-test-app/Config.in" source "package/fbterm/Config.in" source "package/fbv/Config.in" source "package/freerdp/Config.in" source "package/imagemagick/Config.in" source "package/linux-fusion/Config.in" source "package/lite/Config.in" source "package/mesa3d/Config.in" source "package/mesa3d-headers/Config.in" source "package/ocrad/Config.in" source "package/psplash/Config.in" source "package/sdl/Config.in" source "package/sdl_gfx/Config.in" source "package/sdl_image/Config.in" source "package/sdl_mixer/Config.in" source "package/sdl_net/Config.in" source "package/sdl_sound/Config.in" source "package/sdl_ttf/Config.in" source "package/sdl2/Config.in" source "package/sdl2_gfx/Config.in" source "package/sdl2_image/Config.in" source "package/sdl2_ttf/Config.in" comment "Other GUIs" source "package/qt/Config.in" source "package/qt5/Config.in" if BR2_PACKAGE_QT || BR2_PACKAGE_QT5 comment "QT libraries and helper libraries" source "package/grantlee/Config.in" source "package/qextserialport/Config.in" source "package/qjson/Config.in" source "package/qtuio/Config.in" source "package/quazip/Config.in" source "package/qwt/Config.in" endif source "package/tekui/Config.in" source "package/weston/Config.in" source "package/x11r7/Config.in" comment "X applications" depends on BR2_PACKAGE_XORG7 source "package/alsamixergui/Config.in" source "package/apitrace/Config.in" source "package/dillo/Config.in" source "package/docker/Config.in" source "package/feh/Config.in" source "package/gmpc/Config.in" source "package/gqview/Config.in" source "package/gtkperf/Config.in" source "package/leafpad/Config.in" source "package/midori/Config.in" source "package/nodm/Config.in" source "package/pcmanfm/Config.in" source "package/qt-webkit-kiosk/Config.in" source "package/rdesktop/Config.in" source "package/synergy/Config.in" source "package/torsmo/Config.in" source "package/wmctrl/Config.in" source "package/x11vnc/Config.in" source "package/xdotool/Config.in" source "package/xscreensaver/Config.in" source "package/xterm/Config.in" source "package/xvkbd/Config.in" source "package/yad/Config.in" comment "X libraries and helper libraries" depends on BR2_PACKAGE_XORG7 source "package/libsexy/Config.in" source "package/x11r7/xkeyboard-config/Config.in" comment "X window managers" depends on BR2_PACKAGE_XORG7 source "package/enlightenment/Config.in" source "package/fluxbox/Config.in" source "package/matchbox/Config.in" source "package/metacity/Config.in" source "package/openbox/Config.in" endmenu menu "Hardware handling" menu "Firmware" source "package/am33x-cm3/Config.in" source "package/b43-firmware/Config.in" source "package/linux-firmware/Config.in" source "package/rpi-firmware/Config.in" source "package/sunxi-boards/Config.in" source "package/ux500-firmware/Config.in" source "package/wilc1000-firmware/Config.in" source "package/zd1211-firmware/Config.in" endmenu source "package/a10disp/Config.in" source "package/acpica/Config.in" source "package/acpid/Config.in" source "package/acpitool/Config.in" source "package/aer-inject/Config.in" source "package/am335x-pru-package/Config.in" source "package/avrdude/Config.in" source "package/bcache-tools/Config.in" source "package/biosdevname/Config.in" source "package/cc-tool/Config.in" source "package/cdrkit/Config.in" source "package/cryptsetup/Config.in" source "package/cwiid/Config.in" source "package/dbus/Config.in" source "package/dbus-cpp/Config.in" source "package/dbus-glib/Config.in" source "package/dbus-python/Config.in" source "package/dbus-triggerd/Config.in" source "package/devmem2/Config.in" source "package/dmidecode/Config.in" source "package/dmraid/Config.in" source "package/dtv-scan-tables/Config.in" source "package/dvb-apps/Config.in" source "package/dvbsnoop/Config.in" source "package/edid-decode/Config.in" source "package/eeprog/Config.in" source "package/eudev/Config.in" source "package/evemu/Config.in" source "package/evtest/Config.in" source "package/fan-ctrl/Config.in" source "package/fbtft/Config.in" source "package/fconfig/Config.in" source "package/fis/Config.in" source "package/flashrom/Config.in" source "package/fmtools/Config.in" source "package/freescale-imx/Config.in" source "package/fxload/Config.in" source "package/gadgetfs-test/Config.in" source "package/gpm/Config.in" source "package/gpsd/Config.in" source "package/gptfdisk/Config.in" source "package/gvfs/Config.in" source "package/hdparm/Config.in" source "package/hwdata/Config.in" source "package/hwloc/Config.in" source "package/i2c-tools/Config.in" source "package/i7z/Config.in" source "package/input-event-daemon/Config.in" source "package/input-tools/Config.in" source "package/intel-microcode/Config.in" source "package/iostat/Config.in" source "package/ipmitool/Config.in" source "package/ipmiutil/Config.in" source "package/iqvlinux/Config.in" source "package/irda-utils/Config.in" source "package/iucode-tool/Config.in" source "package/kbd/Config.in" source "package/lcdproc/Config.in" source "package/libuio/Config.in" source "package/libump/Config.in" source "package/linux-backports/Config.in" source "package/lirc-tools/Config.in" source "package/lm-sensors/Config.in" source "package/lshw/Config.in" source "package/lsuio/Config.in" source "package/lvm2/Config.in" source "package/mali-t76x/Config.in" source "package/mdadm/Config.in" source "package/memtest86/Config.in" source "package/memtester/Config.in" source "package/minicom/Config.in" source "package/msr-tools/Config.in" source "package/nanocom/Config.in" source "package/neard/Config.in" source "package/nvidia-driver/Config.in" source "package/nvidia-tegra23/Config.in" source "package/nvme/Config.in" source "package/odroid-mali/Config.in" source "package/odroid-scripts/Config.in" source "package/ofono/Config.in" source "package/ola/Config.in" source "package/on2-8170-modules/Config.in" source "package/open2300/Config.in" source "package/openipmi/Config.in" source "package/openocd/Config.in" source "package/openpowerlink/Config.in" source "package/owl-linux/Config.in" source "package/parted/Config.in" source "package/pciutils/Config.in" source "package/pdbg/Config.in" source "package/picocom/Config.in" source "package/pifmrds/Config.in" source "package/powertop/Config.in" source "package/pps-tools/Config.in" source "package/pulseview/Config.in" source "package/read-edid/Config.in" source "package/rfkill/Config.in" source "package/rng-tools/Config.in" source "package/rpi-userland/Config.in" source "package/rs485conf/Config.in" source "package/rtl8188eu/Config.in" source "package/rtl8821au/Config.in" source "package/sane-backends/Config.in" source "package/sdparm/Config.in" source "package/setserial/Config.in" source "package/sg3_utils/Config.in" source "package/sigrok-cli/Config.in" source "package/sispmctl/Config.in" source "package/smartmontools/Config.in" source "package/smstools3/Config.in" source "package/snowball-hdmiservice/Config.in" source "package/spi-tools/Config.in" source "package/sredird/Config.in" source "package/statserial/Config.in" source "package/stm32flash/Config.in" source "package/sunxi-cedarx/Config.in" source "package/sunxi-mali/Config.in" source "package/sysstat/Config.in" source "package/targetcli-fb/Config.in" source "package/ti-gfx/Config.in" source "package/ti-sgx-demos/Config.in" source "package/ti-sgx-km/Config.in" source "package/ti-sgx-um/Config.in" source "package/ti-uim/Config.in" source "package/ti-utils/Config.in" source "package/triggerhappy/Config.in" source "package/uboot-tools/Config.in" source "package/ubus/Config.in" source "package/udev/Config.in" source "package/udisks/Config.in" source "package/usb_modeswitch/Config.in" source "package/usb_modeswitch_data/Config.in" source "package/usbmount/Config.in" source "package/usbutils/Config.in" source "package/w_scan/Config.in" source "package/wf111/Config.in" source "package/wipe/Config.in" source "package/xorriso/Config.in" endmenu menu "Interpreter languages and scripting" source "package/4th/Config.in" source "package/enscript/Config.in" source "package/erlang/Config.in" if BR2_PACKAGE_ERLANG menu "Erlang libraries/modules" source "package/erlang-goldrush/Config.in" source "package/erlang-lager/Config.in" source "package/erlang-p1-cache-tab/Config.in" source "package/erlang-p1-iconv/Config.in" source "package/erlang-p1-sip/Config.in" source "package/erlang-p1-stringprep/Config.in" source "package/erlang-p1-stun/Config.in" source "package/erlang-p1-tls/Config.in" source "package/erlang-p1-utils/Config.in" source "package/erlang-p1-xml/Config.in" source "package/erlang-p1-yaml/Config.in" source "package/erlang-p1-zlib/Config.in" endmenu endif source "package/ficl/Config.in" source "package/gauche/Config.in" source "package/guile/Config.in" source "package/haserl/Config.in" source "package/jamvm/Config.in" source "package/jimtcl/Config.in" source "package/lua/Config.in" source "package/luainterpreter/Config.in" source "package/luajit/Config.in" if BR2_PACKAGE_HAS_LUAINTERPRETER && !BR2_STATIC_LIBS # lua modules are dynamically loaded, so not available on static builds menu "Lua libraries/modules" source "package/argparse/Config.in" source "package/cgilua/Config.in" source "package/copas/Config.in" source "package/cosmo/Config.in" source "package/coxpcall/Config.in" source "package/dado/Config.in" source "package/lbase64/Config.in" source "package/ljlinenoise/Config.in" source "package/ljsyscall/Config.in" source "package/lpeg/Config.in" source "package/lpty/Config.in" source "package/lrandom/Config.in" source "package/lsqlite3/Config.in" source "package/lua-cjson/Config.in" source "package/lua-coat/Config.in" source "package/lua-coatpersistent/Config.in" source "package/lua-csnappy/Config.in" source "package/lua-ev/Config.in" source "package/lua-iconv/Config.in" source "package/lua-messagepack/Config.in" source "package/lua-msgpack-native/Config.in" source "package/lua-periphery/Config.in" source "package/lua-testmore/Config.in" source "package/luabitop/Config.in" source "package/luacrypto/Config.in" source "package/luaexpat/Config.in" source "package/luaexpatutils/Config.in" source "package/luafilesystem/Config.in" source "package/luajson/Config.in" source "package/lualogging/Config.in" source "package/luaposix/Config.in" source "package/luasec/Config.in" source "package/luasocket/Config.in" source "package/luasql-sqlite3/Config.in" source "package/lunit/Config.in" source "package/luv/Config.in" source "package/luvi/Config.in" source "package/lzlib/Config.in" source "package/orbit/Config.in" source "package/rings/Config.in" source "package/turbolua/Config.in" source "package/wsapi/Config.in" source "package/xavante/Config.in" endmenu endif source "package/lutok/Config.in" source "package/micropython/Config.in" source "package/micropython-lib/Config.in" source "package/moarvm/Config.in" source "package/mono/Config.in" if BR2_PACKAGE_MONO menu "Mono libraries/modules" source "package/mono-gtksharp3/Config.in" endmenu endif source "package/nodejs/Config.in" source "package/perl/Config.in" if BR2_PACKAGE_PERL menu "Perl libraries/modules" source "package/perl-crypt-openssl-random/Config.in" source "package/perl-crypt-openssl-rsa/Config.in" source "package/perl-datetime-tiny/Config.in" source "package/perl-db-file/Config.in" source "package/perl-digest-hmac/Config.in" source "package/perl-digest-sha1/Config.in" source "package/perl-encode-detect/Config.in" source "package/perl-encode-locale/Config.in" source "package/perl-file-listing/Config.in" source "package/perl-file-util/Config.in" source "package/perl-gd/Config.in" source "package/perl-gdgraph/Config.in" source "package/perl-gdtextutil/Config.in" source "package/perl-html-parser/Config.in" source "package/perl-html-tagset/Config.in" source "package/perl-http-cookies/Config.in" source "package/perl-http-daemon/Config.in" source "package/perl-http-date/Config.in" source "package/perl-http-message/Config.in" source "package/perl-http-negotiate/Config.in" source "package/perl-io-html/Config.in" source "package/perl-io-socket-ssl/Config.in" source "package/perl-json-tiny/Config.in" source "package/perl-libwww-perl/Config.in" source "package/perl-lwp-mediatypes/Config.in" source "package/perl-mail-dkim/Config.in" source "package/perl-mailtools/Config.in" source "package/perl-mime-base64/Config.in" source "package/perl-mojolicious/Config.in" source "package/perl-net-dns/Config.in" source "package/perl-net-http/Config.in" source "package/perl-net-ssleay/Config.in" source "package/perl-netaddr-ip/Config.in" source "package/perl-path-tiny/Config.in" source "package/perl-time-hires/Config.in" source "package/perl-timedate/Config.in" source "package/perl-try-tiny/Config.in" source "package/perl-uri/Config.in" source "package/perl-www-robotrules/Config.in" source "package/perl-xml-libxml/Config.in" source "package/perl-xml-namespacesupport/Config.in" source "package/perl-xml-sax/Config.in" source "package/perl-xml-sax-base/Config.in" endmenu endif source "package/php/Config.in" if BR2_PACKAGE_PHP if !BR2_STATIC_LIBS menu "External php extensions" source "package/php-geoip/Config.in" source "package/php-gnupg/Config.in" source "package/php-imagick/Config.in" source "package/php-memcached/Config.in" source "package/php-ssh2/Config.in" source "package/php-yaml/Config.in" source "package/php-zmq/Config.in" endmenu endif if BR2_STATIC_LIBS comment "External PHP extensions need a toolchain w/ dynamic library" endif endif source "package/python/Config.in" source "package/python3/Config.in" if BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3 menu "External python modules" source "package/python-alsaaudio/Config.in" source "package/python-argh/Config.in" source "package/python-autobahn/Config.in" source "package/python-backports-abc/Config.in" source "package/python-beautifulsoup4/Config.in" source "package/python-bottle/Config.in" source "package/python-can/Config.in" source "package/python-cbor/Config.in" source "package/python-certifi/Config.in" source "package/python-cffi/Config.in" source "package/python-characteristic/Config.in" source "package/python-cheetah/Config.in" source "package/python-cherrypy/Config.in" source "package/python-click/Config.in" source "package/python-coherence/Config.in" source "package/python-configobj/Config.in" source "package/python-configshell-fb/Config.in" source "package/python-crc16/Config.in" source "package/python-crossbar/Config.in" source "package/python-cryptography/Config.in" source "package/python-cssselect/Config.in" source "package/python-daemon/Config.in" source "package/python-dataproperty/Config.in" source "package/python-dateutil/Config.in" source "package/python-dialog/Config.in" source "package/python-dialog3/Config.in" source "package/python-dicttoxml/Config.in" source "package/python-django/Config.in" source "package/python-docopt/Config.in" source "package/python-dominate/Config.in" source "package/python-dpkt/Config.in" source "package/python-ecdsa/Config.in" source "package/python-engineio/Config.in" source "package/python-enum/Config.in" source "package/python-enum34/Config.in" source "package/python-flask/Config.in" source "package/python-flask-jsonrpc/Config.in" source "package/python-flask-login/Config.in" source "package/python-flup/Config.in" source "package/python-gobject/Config.in" source "package/python-html5lib/Config.in" source "package/python-httplib2/Config.in" source "package/python-humanize/Config.in" source "package/python-id3/Config.in" source "package/python-idna/Config.in" source "package/python-iniparse/Config.in" source "package/python-iowait/Config.in" source "package/python-ipaddr/Config.in" source "package/python-ipaddress/Config.in" source "package/python-ipy/Config.in" source "package/python-ipython/Config.in" source "package/python-itsdangerous/Config.in" source "package/python-jinja2/Config.in" source "package/python-json-schema-validator/Config.in" source "package/python-keyring/Config.in" source "package/python-libconfig/Config.in" source "package/python-lmdb/Config.in" source "package/python-lxml/Config.in" source "package/python-mad/Config.in" source "package/python-mako/Config.in" source "package/python-markdown/Config.in" source "package/python-markupsafe/Config.in" source "package/python-meld3/Config.in" source "package/python-mistune/Config.in" source "package/python-msgpack/Config.in" source "package/python-netaddr/Config.in" source "package/python-netifaces/Config.in" source "package/python-networkmanager/Config.in" source "package/python-nfc/Config.in" source "package/python-numpy/Config.in" source "package/python-paho-mqtt/Config.in" source "package/python-pam/Config.in" source "package/python-paramiko/Config.in" source "package/python-pathtools/Config.in" source "package/python-pathvalidate/Config.in" source "package/python-pexpect/Config.in" source "package/python-pillow/Config.in" source "package/python-posix-ipc/Config.in" source "package/python-prompt-toolkit/Config.in" source "package/python-protobuf/Config.in" source "package/python-psutil/Config.in" source "package/python-ptyprocess/Config.in" source "package/python-pyasn/Config.in" source "package/python-pyasn-modules/Config.in" source "package/python-pycli/Config.in" source "package/python-pycparser/Config.in" source "package/python-pycrypto/Config.in" source "package/python-pydal/Config.in" source "package/python-pyftpdlib/Config.in" source "package/python-pygame/Config.in" source "package/python-pygments/Config.in" source "package/python-pyinotify/Config.in" source "package/python-pymysql/Config.in" source "package/python-pynacl/Config.in" source "package/python-pyopenssl/Config.in" source "package/python-pyparsing/Config.in" source "package/python-pyparted/Config.in" source "package/python-pypcap/Config.in" source "package/python-pyqt/Config.in" source "package/python-pyratemp/Config.in" source "package/python-pyro/Config.in" source "package/python-pyroute2/Config.in" source "package/python-pysendfile/Config.in" source "package/python-pysmb/Config.in" source "package/python-pysnmp/Config.in" source "package/python-pysnmp-apps/Config.in" source "package/python-pysnmp-mibs/Config.in" source "package/python-pysocks/Config.in" source "package/python-pytablewriter/Config.in" source "package/python-pytrie/Config.in" source "package/python-pytz/Config.in" source "package/python-pyudev/Config.in" source "package/python-pyusb/Config.in" source "package/python-pyxb/Config.in" source "package/python-pyyaml/Config.in" source "package/python-pyzmq/Config.in" source "package/python-requests/Config.in" source "package/python-rpi-gpio/Config.in" source "package/python-rtslib-fb/Config.in" source "package/python-scapy3k/Config.in" source "package/python-sdnotify/Config.in" source "package/python-serial/Config.in" source "package/python-service-identity/Config.in" source "package/python-setproctitle/Config.in" source "package/python-setuptools/Config.in" source "package/python-shutilwhich/Config.in" source "package/python-simplejson/Config.in" source "package/python-singledispatch/Config.in" source "package/python-sip/Config.in" source "package/python-six/Config.in" source "package/python-smbus-cffi/Config.in" source "package/python-socketio/Config.in" source "package/python-spidev/Config.in" source "package/python-thrift/Config.in" source "package/python-tomako/Config.in" source "package/python-tornado/Config.in" source "package/python-treq/Config.in" source "package/python-twisted/Config.in" source "package/python-txaio/Config.in" source "package/python-u-msgpack/Config.in" source "package/python-ubjson/Config.in" source "package/python-ujson/Config.in" source "package/python-urllib3/Config.in" source "package/python-urwid/Config.in" source "package/python-versiontools/Config.in" source "package/python-watchdog/Config.in" source "package/python-wcwidth/Config.in" source "package/python-web2py/Config.in" source "package/python-webpy/Config.in" source "package/python-werkzeug/Config.in" source "package/python-ws4py/Config.in" source "package/python-wsaccel/Config.in" source "package/python-xlrd/Config.in" source "package/python-xlsxwriter/Config.in" source "package/python-xlutils/Config.in" source "package/python-xlwt/Config.in" source "package/python-zope-interface/Config.in" endmenu endif source "package/ruby/Config.in" source "package/tcl/Config.in" if BR2_PACKAGE_TCL menu "Tcl libraries/modules" source "package/expect/Config.in" source "package/tcllib/Config.in" endmenu endif endmenu menu "Libraries" menu "Audio/Sound" source "package/alsa-lib/Config.in" source "package/audiofile/Config.in" source "package/celt051/Config.in" source "package/fdk-aac/Config.in" source "package/libao/Config.in" source "package/libasplib/Config.in" source "package/libbroadvoice/Config.in" source "package/libcdaudio/Config.in" source "package/libcddb/Config.in" source "package/libcdio/Config.in" source "package/libcodec2/Config.in" source "package/libcue/Config.in" source "package/libcuefile/Config.in" source "package/libebur128/Config.in" source "package/libg7221/Config.in" source "package/libid3tag/Config.in" source "package/libilbc/Config.in" source "package/liblo/Config.in" source "package/libmad/Config.in" source "package/libmodplug/Config.in" source "package/libmpd/Config.in" source "package/libmpdclient/Config.in" source "package/libreplaygain/Config.in" source "package/libsamplerate/Config.in" source "package/libsidplay2/Config.in" source "package/libsilk/Config.in" source "package/libsndfile/Config.in" source "package/libsoundtouch/Config.in" source "package/libsoxr/Config.in" source "package/libvorbis/Config.in" source "package/mp4v2/Config.in" source "package/openal/Config.in" source "package/opencore-amr/Config.in" source "package/opus/Config.in" source "package/opusfile/Config.in" source "package/portaudio/Config.in" source "package/sbc/Config.in" source "package/speex/Config.in" source "package/taglib/Config.in" source "package/tinyalsa/Config.in" source "package/tremor/Config.in" source "package/vo-aacenc/Config.in" source "package/webrtc-audio-processing/Config.in" endmenu menu "Compression and decompression" source "package/libarchive/Config.in" source "package/libsquish/Config.in" source "package/libzip/Config.in" source "package/lzo/Config.in" source "package/minizip/Config.in" source "package/snappy/Config.in" source "package/szip/Config.in" source "package/zlib/Config.in" endmenu menu "Crypto" source "package/beecrypt/Config.in" source "package/botan/Config.in" source "package/ca-certificates/Config.in" source "package/cryptodev/Config.in" source "package/gcr/Config.in" source "package/gnutls/Config.in" source "package/libassuan/Config.in" source "package/libgcrypt/Config.in" source "package/libgpg-error/Config.in" source "package/libgpgme/Config.in" source "package/libksba/Config.in" source "package/libmcrypt/Config.in" source "package/libmhash/Config.in" source "package/libnss/Config.in" source "package/libsecret/Config.in" source "package/libsha1/Config.in" source "package/libsodium/Config.in" source "package/libssh/Config.in" source "package/libssh2/Config.in" source "package/libtomcrypt/Config.in" source "package/libuecc/Config.in" source "package/mbedtls/Config.in" source "package/nettle/Config.in" source "package/openssl/Config.in" source "package/polarssl/Config.in" source "package/tinydtls/Config.in" source "package/trousers/Config.in" endmenu menu "Database" source "package/berkeleydb/Config.in" source "package/cppdb/Config.in" source "package/gdbm/Config.in" source "package/kompexsqlite/Config.in" source "package/leveldb/Config.in" source "package/libpqxx/Config.in" source "package/mongodb/Config.in" source "package/mysql/Config.in" source "package/postgresql/Config.in" source "package/redis/Config.in" source "package/sqlcipher/Config.in" source "package/sqlite/Config.in" source "package/unixodbc/Config.in" endmenu menu "Filesystem" source "package/gamin/Config.in" source "package/libconfig/Config.in" source "package/libconfuse/Config.in" source "package/libfuse/Config.in" source "package/liblockfile/Config.in" source "package/libnfs/Config.in" source "package/libsysfs/Config.in" source "package/lockdev/Config.in" endmenu menu "Graphics" source "package/assimp/Config.in" source "package/atk/Config.in" source "package/atkmm/Config.in" source "package/bullet/Config.in" source "package/cairo/Config.in" source "package/cairomm/Config.in" source "package/exiv2/Config.in" source "package/fltk/Config.in" source "package/fontconfig/Config.in" source "package/freetype/Config.in" source "package/gd/Config.in" source "package/gdk-pixbuf/Config.in" source "package/giblib/Config.in" source "package/giflib/Config.in" source "package/granite/Config.in" source "package/graphite2/Config.in" source "package/gtkmm3/Config.in" source "package/gtksourceview/Config.in" source "package/harfbuzz/Config.in" source "package/ijs/Config.in" source "package/imlib2/Config.in" source "package/jasper/Config.in" source "package/jpeg/Config.in" source "package/kmsxx/Config.in" source "package/lcms2/Config.in" source "package/lesstif/Config.in" source "package/libart/Config.in" source "package/libdmtx/Config.in" source "package/libdri2/Config.in" source "package/libdrm/Config.in" source "package/libepoxy/Config.in" source "package/libevas-generic-loaders/Config.in" source "package/libexif/Config.in" source "package/libfm/Config.in" source "package/libfm-extra/Config.in" source "package/libfreeglut/Config.in" source "package/libfreeimage/Config.in" source "package/libgail/Config.in" source "package/libgdiplus/Config.in" source "package/libgeotiff/Config.in" source "package/libglade/Config.in" source "package/libglew/Config.in" source "package/libglfw/Config.in" source "package/libglu/Config.in" source "package/libgtk2/Config.in" source "package/libgtk3/Config.in" source "package/libmng/Config.in" source "package/libpng/Config.in" source "package/libqrencode/Config.in" source "package/libraw/Config.in" source "package/librsvg/Config.in" source "package/libsoil/Config.in" source "package/libsvg/Config.in" source "package/libsvg-cairo/Config.in" source "package/libsvgtiny/Config.in" source "package/libva/Config.in" source "package/libva-intel-driver/Config.in" source "package/libvdpau/Config.in" source "package/libvips/Config.in" source "package/menu-cache/Config.in" source "package/opencv/Config.in" source "package/opencv3/Config.in" source "package/opengl/Config.in" source "package/openjpeg/Config.in" source "package/pango/Config.in" source "package/pangomm/Config.in" source "package/pixman/Config.in" source "package/poppler/Config.in" source "package/powervr/Config.in" source "package/tiff/Config.in" source "package/wayland/Config.in" source "package/wayland-protocols/Config.in" source "package/webkit/Config.in" source "package/webkitgtk/Config.in" source "package/webkitgtk24/Config.in" source "package/webp/Config.in" source "package/zbar/Config.in" source "package/zxing-cpp/Config.in" endmenu menu "Hardware handling" source "package/acsccid/Config.in" source "package/bcm2835/Config.in" source "package/c-periphery/Config.in" source "package/ccid/Config.in" source "package/dtc/Config.in" source "package/gnu-efi/Config.in" source "package/hidapi/Config.in" source "package/lcdapi/Config.in" source "package/libaio/Config.in" source "package/libatasmart/Config.in" source "package/libcec/Config.in" source "package/libfreefare/Config.in" source "package/libftdi/Config.in" source "package/libftdi1/Config.in" source "package/libgudev/Config.in" source "package/libhid/Config.in" source "package/libiio/Config.in" source "package/libinput/Config.in" source "package/libiqrf/Config.in" source "package/libllcp/Config.in" source "package/libmbim/Config.in" source "package/libnfc/Config.in" source "package/libpciaccess/Config.in" source "package/libphidget/Config.in" source "package/libqmi/Config.in" source "package/libraw1394/Config.in" source "package/librtas/Config.in" source "package/librtlsdr/Config.in" source "package/libserial/Config.in" source "package/libserialport/Config.in" source "package/libsigrok/Config.in" source "package/libsigrokdecode/Config.in" source "package/libsoc/Config.in" source "package/libusb/Config.in" source "package/libusb-compat/Config.in" source "package/libusbgx/Config.in" source "package/libv4l/Config.in" source "package/libxkbcommon/Config.in" source "package/mraa/Config.in" source "package/mtdev/Config.in" source "package/ne10/Config.in" source "package/neardal/Config.in" source "package/owfs/Config.in" source "package/pcsc-lite/Config.in" source "package/tslib/Config.in" source "package/urg/Config.in" source "package/wiringpi/Config.in" endmenu menu "Javascript" source "package/angularjs/Config.in" source "package/bootstrap/Config.in" source "package/explorercanvas/Config.in" source "package/flot/Config.in" source "package/jquery/Config.in" if BR2_PACKAGE_JQUERY menu "External jQuery plugins" source "package/jquery-datetimepicker/Config.in" source "package/jquery-keyboard/Config.in" source "package/jquery-mobile/Config.in" source "package/jquery-sidebar/Config.in" source "package/jquery-sparkline/Config.in" source "package/jquery-ui/Config.in" source "package/jquery-ui-themes/Config.in" source "package/jquery-validation/Config.in" endmenu endif source "package/jsmin/Config.in" source "package/json-javascript/Config.in" endmenu menu "JSON/XML" source "package/benejson/Config.in" source "package/cjson/Config.in" source "package/expat/Config.in" source "package/ezxml/Config.in" source "package/jansson/Config.in" source "package/json-c/Config.in" source "package/json-glib/Config.in" source "package/jsoncpp/Config.in" source "package/libfastjson/Config.in" source "package/libjson/Config.in" source "package/libroxml/Config.in" source "package/libucl/Config.in" source "package/libxml2/Config.in" source "package/libxmlpp/Config.in" source "package/libxmlrpc/Config.in" source "package/libxslt/Config.in" source "package/libyaml/Config.in" source "package/mxml/Config.in" source "package/rapidjson/Config.in" source "package/rapidxml/Config.in" source "package/raptor/Config.in" source "package/tinyxml/Config.in" source "package/tinyxml2/Config.in" source "package/valijson/Config.in" source "package/xerces/Config.in" source "package/yajl/Config.in" source "package/yaml-cpp/Config.in" endmenu menu "Logging" source "package/eventlog/Config.in" source "package/glog/Config.in" source "package/liblog4c-localtime/Config.in" source "package/liblogging/Config.in" source "package/log4cplus/Config.in" source "package/log4cpp/Config.in" source "package/log4cxx/Config.in" source "package/zlog/Config.in" endmenu menu "Multimedia" source "package/bitstream/Config.in" source "package/libaacs/Config.in" source "package/libamcodec/Config.in" source "package/libass/Config.in" source "package/libbdplus/Config.in" source "package/libbluray/Config.in" source "package/libdcadec/Config.in" source "package/libdvbcsa/Config.in" source "package/libdvbpsi/Config.in" source "package/libdvbsi/Config.in" source "package/libdvdcss/Config.in" source "package/libdvdnav/Config.in" source "package/libdvdread/Config.in" source "package/libebml/Config.in" source "package/libhdhomerun/Config.in" source "package/libimxvpuapi/Config.in" source "package/libmatroska/Config.in" source "package/libmms/Config.in" source "package/libmpeg2/Config.in" source "package/libogg/Config.in" source "package/libopenh264/Config.in" source "package/libplayer/Config.in" source "package/libtheora/Config.in" source "package/libvpx/Config.in" source "package/libyuv/Config.in" source "package/live555/Config.in" source "package/mediastreamer/Config.in" source "package/x264/Config.in" source "package/x265/Config.in" endmenu menu "Networking" source "package/agentpp/Config.in" source "package/alljoyn/Config.in" source "package/alljoyn-base/Config.in" source "package/alljoyn-tcl/Config.in" source "package/alljoyn-tcl-base/Config.in" source "package/batman-adv/Config.in" source "package/c-ares/Config.in" source "package/canfestival/Config.in" source "package/cgic/Config.in" source "package/cppzmq/Config.in" source "package/czmq/Config.in" source "package/filemq/Config.in" source "package/flickcurl/Config.in" source "package/fmlib/Config.in" source "package/freeradius-client/Config.in" source "package/geoip/Config.in" source "package/glib-networking/Config.in" source "package/gssdp/Config.in" source "package/gupnp/Config.in" source "package/gupnp-av/Config.in" source "package/gupnp-dlna/Config.in" source "package/ibrcommon/Config.in" source "package/ibrdtn/Config.in" source "package/libcgi/Config.in" source "package/libcgicc/Config.in" source "package/libcoap/Config.in" source "package/libcurl/Config.in" source "package/libdnet/Config.in" source "package/libeXosip2/Config.in" source "package/libfcgi/Config.in" source "package/libgsasl/Config.in" source "package/libhttpparser/Config.in" source "package/libidn/Config.in" source "package/libiscsi/Config.in" source "package/libldns/Config.in" source "package/libmbus/Config.in" source "package/libmemcached/Config.in" source "package/libmicrohttpd/Config.in" source "package/libminiupnpc/Config.in" source "package/libmnl/Config.in" source "package/libmodbus/Config.in" source "package/libnatpmp/Config.in" source "package/libndp/Config.in" source "package/libnet/Config.in" source "package/libnetfilter_acct/Config.in" source "package/libnetfilter_conntrack/Config.in" source "package/libnetfilter_cthelper/Config.in" source "package/libnetfilter_cttimeout/Config.in" source "package/libnetfilter_log/Config.in" source "package/libnetfilter_queue/Config.in" source "package/libnfnetlink/Config.in" source "package/libnftnl/Config.in" source "package/libnice/Config.in" source "package/libnl/Config.in" source "package/liboauth/Config.in" source "package/liboping/Config.in" source "package/libosip2/Config.in" source "package/libpcap/Config.in" source "package/libpjsip/Config.in" source "package/librsync/Config.in" source "package/libshairplay/Config.in" source "package/libshout/Config.in" source "package/libsocketcan/Config.in" source "package/libsoup/Config.in" source "package/libsrtp/Config.in" source "package/libstrophe/Config.in" source "package/libtirpc/Config.in" source "package/libtorrent/Config.in" source "package/libupnp/Config.in" source "package/libupnpp/Config.in" source "package/liburiparser/Config.in" source "package/libvncserver/Config.in" source "package/libwebsock/Config.in" source "package/libwebsockets/Config.in" source "package/lksctp-tools/Config.in" source "package/mongoose/Config.in" source "package/neon/Config.in" source "package/norm/Config.in" source "package/nss-mdns/Config.in" source "package/nss-pam-ldapd/Config.in" source "package/omniorb/Config.in" source "package/openldap/Config.in" source "package/openmpi/Config.in" source "package/openpgm/Config.in" source "package/openzwave/Config.in" source "package/ortp/Config.in" source "package/qdecoder/Config.in" source "package/qpid-proton/Config.in" source "package/rabbitmq-c/Config.in" source "package/rtmpdump/Config.in" source "package/slirp/Config.in" source "package/snmppp/Config.in" source "package/sofia-sip/Config.in" source "package/thrift/Config.in" source "package/usbredir/Config.in" source "package/wvstreams/Config.in" source "package/zeromq/Config.in" source "package/zmqpp/Config.in" source "package/zyre/Config.in" endmenu menu "Other" source "package/apr/Config.in" source "package/apr-util/Config.in" source "package/argp-standalone/Config.in" source "package/armadillo/Config.in" source "package/atf/Config.in" source "package/bdwgc/Config.in" source "package/boost/Config.in" source "package/clapack/Config.in" source "package/classpath/Config.in" source "package/cppcms/Config.in" source "package/dawgdic/Config.in" source "package/ding-libs/Config.in" source "package/eigen/Config.in" source "package/elfutils/Config.in" source "package/fftw/Config.in" source "package/flann/Config.in" source "package/gflags/Config.in" source "package/glibmm/Config.in" source "package/glm/Config.in" source "package/gmock/Config.in" source "package/gmp/Config.in" source "package/gsl/Config.in" source "package/gtest/Config.in" source "package/jemalloc/Config.in" source "package/lapack/Config.in" source "package/libargtable2/Config.in" source "package/libatomic_ops/Config.in" source "package/libbsd/Config.in" source "package/libcap/Config.in" source "package/libcap-ng/Config.in" source "package/libcgroup/Config.in" source "package/libcofi/Config.in" source "package/libcroco/Config.in" source "package/libcrossguid/Config.in" source "package/libdaemon/Config.in" source "package/libee/Config.in" source "package/libev/Config.in" source "package/libevdev/Config.in" source "package/libevent/Config.in" source "package/libffi/Config.in" source "package/libgee/Config.in" source "package/libglib2/Config.in" source "package/libical/Config.in" source "package/liblinear/Config.in" source "package/libnspr/Config.in" source "package/libpfm4/Config.in" source "package/libplatform/Config.in" source "package/libplist/Config.in" source "package/libpthread-stubs/Config.in" source "package/libpthsem/Config.in" source "package/libseccomp/Config.in" source "package/libsigc/Config.in" source "package/libsigsegv/Config.in" source "package/libtasn1/Config.in" source "package/libtommath/Config.in" source "package/libtpl/Config.in" source "package/libubox/Config.in" source "package/libuci/Config.in" source "package/libunwind/Config.in" source "package/liburcu/Config.in" source "package/libuv/Config.in" source "package/lightning/Config.in" source "package/linux-pam/Config.in" if BR2_PACKAGE_LINUX_PAM comment "linux-pam plugins" source "package/libpam-radius-auth/Config.in" source "package/libpam-tacplus/Config.in" endif source "package/liquid-dsp/Config.in" source "package/lttng-libust/Config.in" source "package/mpc/Config.in" source "package/mpdecimal/Config.in" source "package/mpfr/Config.in" source "package/msgpack/Config.in" source "package/mtdev2tuio/Config.in" source "package/musl-compat-headers/Config.in" source "package/openblas/Config.in" source "package/orc/Config.in" source "package/p11-kit/Config.in" source "package/poco/Config.in" source "package/protobuf/Config.in" source "package/protobuf-c/Config.in" source "package/qhull/Config.in" source "package/qlibc/Config.in" source "package/sphinxbase/Config.in" source "package/startup-notification/Config.in" source "package/tinycbor/Config.in" source "package/tz/Config.in" source "package/tzdata/Config.in" endmenu menu "Security" source "package/libselinux/Config.in" source "package/libsemanage/Config.in" source "package/libsepol/Config.in" endmenu menu "Text and terminal handling" source "package/enchant/Config.in" source "package/icu/Config.in" source "package/libcli/Config.in" source "package/libedit/Config.in" source "package/libenca/Config.in" source "package/libestr/Config.in" source "package/libfribidi/Config.in" source "package/libiconv/Config.in" source "package/libunistring/Config.in" source "package/linenoise/Config.in" source "package/ncurses/Config.in" source "package/newt/Config.in" source "package/pcre/Config.in" source "package/popt/Config.in" source "package/readline/Config.in" source "package/slang/Config.in" source "package/tclap/Config.in" source "package/ustr/Config.in" endmenu endmenu menu "Mail" source "package/dovecot/Config.in" source "package/exim/Config.in" source "package/fetchmail/Config.in" source "package/heirloom-mailx/Config.in" source "package/libesmtp/Config.in" source "package/msmtp/Config.in" source "package/mutt/Config.in" source "package/sylpheed/Config.in" endmenu menu "Miscellaneous" source "package/aespipe/Config.in" source "package/bc/Config.in" source "package/clamav/Config.in" source "package/collectd/Config.in" source "package/domoticz/Config.in" source "package/empty/Config.in" source "package/gnuradio/Config.in" source "package/googlefontdirectory/Config.in" source "package/gr-osmosdr/Config.in" source "package/gsettings-desktop-schemas/Config.in" source "package/haveged/Config.in" source "package/mcrypt/Config.in" source "package/mobile-broadband-provider-info/Config.in" source "package/qemu/Config.in" source "package/qpdf/Config.in" source "package/shared-mime-info/Config.in" source "package/snowball-init/Config.in" source "package/taskd/Config.in" source "package/wine/Config.in" source "package/xutil_util-macros/Config.in" endmenu menu "Networking applications" source "package/aiccu/Config.in" source "package/aircrack-ng/Config.in" source "package/apache/Config.in" source "package/argus/Config.in" source "package/arptables/Config.in" source "package/atftp/Config.in" source "package/autossh/Config.in" source "package/avahi/Config.in" source "package/axel/Config.in" source "package/babeld/Config.in" source "package/bandwidthd/Config.in" source "package/batctl/Config.in" source "package/bcusdk/Config.in" source "package/bind/Config.in" source "package/bluez_utils/Config.in" source "package/bluez5_utils/Config.in" source "package/bmon/Config.in" source "package/boa/Config.in" source "package/bridge-utils/Config.in" source "package/bwm-ng/Config.in" source "package/c-icap/Config.in" source "package/c-icap-modules/Config.in" source "package/can-utils/Config.in" source "package/cannelloni/Config.in" source "package/chrony/Config.in" source "package/civetweb/Config.in" source "package/connman/Config.in" source "package/connman-gtk/Config.in" source "package/conntrack-tools/Config.in" source "package/crda/Config.in" source "package/ctorrent/Config.in" source "package/cups/Config.in" source "package/dante/Config.in" source "package/dhcp/Config.in" source "package/dhcpcd/Config.in" source "package/dhcpdump/Config.in" source "package/dnsmasq/Config.in" source "package/drbd-utils/Config.in" source "package/dropbear/Config.in" source "package/ebtables/Config.in" source "package/ejabberd/Config.in" source "package/ethtool/Config.in" source "package/faifa/Config.in" source "package/fastd/Config.in" source "package/fcgiwrap/Config.in" source "package/flannel/Config.in" source "package/fmc/Config.in" source "package/fping/Config.in" source "package/freeswitch/Config.in" source "package/gupnp-tools/Config.in" source "package/gesftpserver/Config.in" source "package/gutenprint/Config.in" source "package/hans/Config.in" source "package/hiawatha/Config.in" source "package/hostapd/Config.in" source "package/hplip/Config.in" source "package/httping/Config.in" source "package/ibrdtn-tools/Config.in" source "package/ibrdtnd/Config.in" source "package/ifplugd/Config.in" source "package/iftop/Config.in" source "package/ifupdown/Config.in" source "package/igd2-for-linux/Config.in" source "package/igh-ethercat/Config.in" source "package/igmpproxy/Config.in" source "package/inadyn/Config.in" source "package/iodine/Config.in" source "package/iperf/Config.in" source "package/iperf3/Config.in" source "package/iproute2/Config.in" source "package/ipsec-tools/Config.in" source "package/ipset/Config.in" source "package/iptables/Config.in" source "package/iptraf-ng/Config.in" source "package/iputils/Config.in" source "package/irssi/Config.in" source "package/iw/Config.in" source "package/janus-gateway/Config.in" source "package/kismet/Config.in" source "package/knock/Config.in" source "package/leafnode2/Config.in" source "package/lft/Config.in" source "package/lftp/Config.in" source "package/lighttpd/Config.in" source "package/linknx/Config.in" source "package/links/Config.in" source "package/linphone/Config.in" source "package/linux-zigbee/Config.in" source "package/lldpd/Config.in" source "package/lrzsz/Config.in" source "package/macchanger/Config.in" source "package/memcached/Config.in" source "package/mii-diag/Config.in" source "package/minidlna/Config.in" source "package/minissdpd/Config.in" source "package/mjpg-streamer/Config.in" source "package/modem-manager/Config.in" source "package/mongrel2/Config.in" source "package/monkey/Config.in" source "package/mosh/Config.in" source "package/mosquitto/Config.in" source "package/mrouted/Config.in" source "package/mtr/Config.in" source "package/nbd/Config.in" source "package/ncftp/Config.in" source "package/ndisc6/Config.in" source "package/netatalk/Config.in" source "package/netcat/Config.in" source "package/netcat-openbsd/Config.in" source "package/netplug/Config.in" source "package/netsnmp/Config.in" source "package/netstat-nat/Config.in" source "package/net-tools/Config.in" source "package/network-manager/Config.in" source "package/nfacct/Config.in" source "package/nftables/Config.in" source "package/nginx/Config.in" if BR2_PACKAGE_NGINX menu "External nginx modules" source "package/nginx-naxsi/Config.in" source "package/nginx-upload/Config.in" endmenu endif source "package/ngircd/Config.in" source "package/ngrep/Config.in" source "package/nload/Config.in" source "package/nmap/Config.in" source "package/noip/Config.in" source "package/ntp/Config.in" source "package/nuttcp/Config.in" source "package/odhcp6c/Config.in" source "package/odhcploc/Config.in" source "package/olsr/Config.in" source "package/open-plc-utils/Config.in" source "package/openntpd/Config.in" source "package/openobex/Config.in" source "package/openssh/Config.in" source "package/openswan/Config.in" source "package/openvpn/Config.in" source "package/p910nd/Config.in" source "package/phidgetwebservice/Config.in" source "package/portmap/Config.in" source "package/pound/Config.in" source "package/pppd/Config.in" source "package/pptp-linux/Config.in" source "package/privoxy/Config.in" source "package/proftpd/Config.in" source "package/proxychains-ng/Config.in" source "package/ptpd/Config.in" source "package/ptpd2/Config.in" source "package/pure-ftpd/Config.in" source "package/putty/Config.in" source "package/quagga/Config.in" source "package/radvd/Config.in" source "package/rp-pppoe/Config.in" source "package/rpcbind/Config.in" source "package/rsh-redone/Config.in" source "package/rsync/Config.in" source "package/rtorrent/Config.in" source "package/rtptools/Config.in" source "package/samba4/Config.in" source "package/sconeserver/Config.in" source "package/ser2net/Config.in" source "package/shairport-sync/Config.in" source "package/shellinabox/Config.in" source "package/smcroute/Config.in" source "package/socat/Config.in" source "package/socketcand/Config.in" source "package/softether/Config.in" source "package/spawn-fcgi/Config.in" source "package/spice/Config.in" source "package/spice-protocol/Config.in" source "package/squid/Config.in" source "package/sshpass/Config.in" source "package/strongswan/Config.in" source "package/stunnel/Config.in" source "package/tcpdump/Config.in" source "package/tcping/Config.in" source "package/tcpreplay/Config.in" source "package/tftpd/Config.in" source "package/thttpd/Config.in" source "package/tinc/Config.in" source "package/tinyhttpd/Config.in" source "package/tn5250/Config.in" source "package/tor/Config.in" source "package/transmission/Config.in" source "package/tunctl/Config.in" source "package/tvheadend/Config.in" source "package/udpcast/Config.in" source "package/ulogd/Config.in" source "package/ushare/Config.in" source "package/ussp-push/Config.in" source "package/vde2/Config.in" source "package/vnstat/Config.in" source "package/vpnc/Config.in" source "package/vsftpd/Config.in" source "package/vtun/Config.in" source "package/wavemon/Config.in" source "package/wget/Config.in" source "package/whois/Config.in" source "package/wireless-regdb/Config.in" source "package/wireless_tools/Config.in" source "package/wireshark/Config.in" source "package/wpa_supplicant/Config.in" source "package/wpan-tools/Config.in" source "package/wvdial/Config.in" source "package/xinetd/Config.in" source "package/xl2tp/Config.in" source "package/xtables-addons/Config.in" source "package/znc/Config.in" endmenu menu "Package managers" comment "-------------------------------------------------------" comment "Please note: " comment "- Buildroot does *not* generate binary packages, " comment "- Buildroot does *not* install any package database. " comment "* " comment "It is up to you to provide those by yourself if you " comment "want to use any of those package managers. " comment "* " comment "See the manual: " comment "http://buildroot.org/manual.html#faq-no-binary-packages" comment "-------------------------------------------------------" source "package/ipkg/Config.in" source "package/opkg/Config.in" source "package/rpm/Config.in" endmenu menu "Real-Time" source "package/rtai/Config.in" source "package/xenomai/Config.in" endmenu menu "Security" source "package/setools/Config.in" endmenu menu "Shell and utilities" comment "Shells" source "package/bash/Config.in" source "package/dash/Config.in" source "package/zsh/Config.in" comment "Utilities" source "package/at/Config.in" source "package/ccrypt/Config.in" source "package/crudini/Config.in" source "package/dialog/Config.in" source "package/dtach/Config.in" source "package/file/Config.in" source "package/gnupg/Config.in" source "package/gnupg2/Config.in" source "package/inotify-tools/Config.in" source "package/lockfile-progs/Config.in" source "package/logrotate/Config.in" source "package/logsurfer/Config.in" source "package/pinentry/Config.in" source "package/ranger/Config.in" source "package/screen/Config.in" source "package/sudo/Config.in" source "package/terminology/Config.in" source "package/time/Config.in" source "package/tmux/Config.in" source "package/which/Config.in" source "package/xmlstarlet/Config.in" source "package/xxhash/Config.in" endmenu menu "System tools" source "package/acl/Config.in" source "package/android-tools/Config.in" source "package/attr/Config.in" source "package/audit/Config.in" source "package/bootutils/Config.in" source "package/cgroupfs-mount/Config.in" source "package/circus/Config.in" source "package/coreutils/Config.in" source "package/cpuload/Config.in" source "package/dcron/Config.in" source "package/debianutils/Config.in" source "package/docker-containerd/Config.in" source "package/docker-engine/Config.in" source "package/dsp-tools/Config.in" source "package/efibootmgr/Config.in" source "package/efivar/Config.in" source "package/emlog/Config.in" source "package/ftop/Config.in" source "package/getent/Config.in" source "package/htop/Config.in" source "package/initscripts/Config.in" source "package/iotop/Config.in" source "package/iprutils/Config.in" source "package/irqbalance/Config.in" source "package/keyutils/Config.in" source "package/kmod/Config.in" source "package/kvmtool/Config.in" source "package/lxc/Config.in" source "package/monit/Config.in" source "package/ncdu/Config.in" source "package/numactl/Config.in" source "package/nut/Config.in" source "package/openvmtools/Config.in" source "package/polkit/Config.in" source "package/powerpc-utils/Config.in" source "package/procps-ng/Config.in" source "package/procrank_linux/Config.in" source "package/psmisc/Config.in" source "package/pwgen/Config.in" source "package/quota/Config.in" source "package/rsyslog/Config.in" source "package/runc/Config.in" source "package/scrub/Config.in" source "package/scrypt/Config.in" source "package/smack/Config.in" source "package/start-stop-daemon/Config.in" source "package/supervisor/Config.in" source "package/swupdate/Config.in" source "package/sysklogd/Config.in" source "package/syslog-ng/Config.in" source "package/systemd/Config.in" source "package/systemd-bootchart/Config.in" source "package/sysvinit/Config.in" source "package/tar/Config.in" source "package/tpm-tools/Config.in" source "package/unscd/Config.in" source "package/util-linux/Config.in" source "package/xen/Config.in" endmenu menu "Text editors and viewers" source "package/ed/Config.in" source "package/joe/Config.in" source "package/less/Config.in" source "package/mc/Config.in" source "package/nano/Config.in" source "package/uemacs/Config.in" source "package/vim/Config.in" endmenu endmenu
shibajee/buildroot
package/Config.in
in
mit
61,789
menu "Host utilities" source "package/aespipe/Config.in.host" source "package/android-tools/Config.in.host" source "package/cbootimage/Config.in.host" source "package/checkpolicy/Config.in.host" source "package/cramfs/Config.in.host" source "package/dfu-util/Config.in.host" source "package/dos2unix/Config.in.host" source "package/dosfstools/Config.in.host" source "package/dtc/Config.in.host" source "package/e2fsprogs/Config.in.host" source "package/e2tools/Config.in.host" source "package/faketime/Config.in.host" source "package/fwup/Config.in.host" source "package/genext2fs/Config.in.host" source "package/genimage/Config.in.host" source "package/genpart/Config.in.host" source "package/go/Config.in.host" source "package/gptfdisk/Config.in.host" source "package/imx-usb-loader/Config.in.host" source "package/jq/Config.in.host" source "package/jsmin/Config.in.host" source "package/lpc3250loader/Config.in.host" source "package/mke2img/Config.in.host" source "package/mtd/Config.in.host" source "package/mtools/Config.in.host" source "package/mxsldr/Config.in.host" source "package/omap-u-boot-utils/Config.in.host" source "package/openocd/Config.in.host" source "package/parted/Config.in.host" source "package/patchelf/Config.in.host" source "package/pwgen/Config.in.host" source "package/qemu/Config.in.host" source "package/sam-ba/Config.in.host" source "package/squashfs/Config.in.host" source "package/sunxi-tools/Config.in.host" source "package/tegrarcm/Config.in.host" source "package/uboot-tools/Config.in.host" source "package/util-linux/Config.in.host" source "package/vboot-utils/Config.in.host" source "package/xorriso/Config.in.host" source "package/zip/Config.in.host" endmenu
shibajee/buildroot
package/Config.in.host
host
mit
1,742
ifndef MAKE MAKE := make endif ifndef HOSTMAKE HOSTMAKE = $(MAKE) endif HOSTMAKE := $(shell which $(HOSTMAKE) || type -p $(HOSTMAKE) || echo make) # If BR2_JLEVEL is 0, scale the maximum concurrency with the number of # CPUs. An additional job is used in order to keep processors busy # while waiting on I/O. # If the number of processors is not available, assume one. ifeq ($(BR2_JLEVEL),0) PARALLEL_JOBS := $(shell echo \ $$((1 + `getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1`))) else PARALLEL_JOBS := $(BR2_JLEVEL) endif MAKE1 := $(HOSTMAKE) -j1 override MAKE = $(HOSTMAKE) \ $(if $(findstring j,$(filter-out --%,$(MAKEFLAGS))),,-j$(PARALLEL_JOBS)) ifeq ($(BR2_TOOLCHAIN_BUILDROOT),y) TARGET_VENDOR = $(call qstrip,$(BR2_TOOLCHAIN_BUILDROOT_VENDOR)) else TARGET_VENDOR = buildroot endif # Sanity checks ifeq ($(TARGET_VENDOR),) $(error BR2_TOOLCHAIN_BUILDROOT_VENDOR is not allowed to be empty) endif ifeq ($(TARGET_VENDOR),unknown) $(error BR2_TOOLCHAIN_BUILDROOT_VENDOR cannot be 'unknown'. \ It might be confused with the native toolchain) endif # Compute GNU_TARGET_NAME GNU_TARGET_NAME = $(ARCH)-$(TARGET_VENDOR)-$(TARGET_OS)-$(LIBC)$(ABI) # FLAT binary format needs uclinux ifeq ($(BR2_BINFMT_FLAT),y) TARGET_OS = uclinux else TARGET_OS = linux endif ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y) LIBC = uclibc else ifeq ($(BR2_TOOLCHAIN_USES_MUSL),y) LIBC = musl else LIBC = gnu endif # The ABI suffix is a bit special on ARM, as it needs to be # -uclibcgnueabi for uClibc EABI, and -gnueabi for glibc EABI. # This means that the LIBC and ABI aren't strictly orthogonal, # which explains why we need the test on LIBC below. ifeq ($(BR2_arm)$(BR2_armeb),y) ifeq ($(LIBC),uclibc) ABI = gnueabi else ABI = eabi endif ifeq ($(BR2_ARM_EABIHF),y) ABI := $(ABI)hf endif endif # For FSL PowerPC there's SPE ifeq ($(BR2_powerpc_SPE),y) ABI = spe # MPC8540s are e500v1 with single precision FP ifeq ($(BR2_powerpc_8540),y) TARGET_ABI += -mabi=spe -mfloat-gprs=single -Wa,-me500 endif ifeq ($(BR2_powerpc_8548),y) TARGET_ABI += -mabi=spe -mfloat-gprs=double -Wa,-me500x2 endif ifeq ($(BR2_powerpc_e500mc),y) TARGET_ABI += -mabi=spe -mfloat-gprs=double -Wa,-me500mc endif endif # Use longcalls option for Xtensa globally. # The 'longcalls' option allows calls across a greater range of addresses, # and is required for some packages. While this option can degrade both # code size and performance, the linker can usually optimize away the # overhead when a call ends up within a certain range. # # Use auto-litpools for Xtensa globally. # Collecting literals into separate section can be advantageous if that # section is placed into DTCM at link time. This is applicable for code # running on bare metal, but makes no sense under linux, where userspace # is isolated from the physical memory details. OTOH placing literals into # separate section breaks build of huge source files, because l32r # instruction can only access literals in 256 KBytes range. # ifeq ($(BR2_xtensa),y) TARGET_ABI += -mlongcalls -mauto-litpools endif ifeq ($(BR2_arc)$(BR2_ARC_ATOMIC_EXT),yy) TARGET_ABI += -matomic endif STAGING_SUBDIR = usr/$(GNU_TARGET_NAME)/sysroot STAGING_DIR = $(HOST_DIR)/$(STAGING_SUBDIR) ifeq ($(BR2_OPTIMIZE_0),y) TARGET_OPTIMIZATION = -O0 endif ifeq ($(BR2_OPTIMIZE_1),y) TARGET_OPTIMIZATION = -O1 endif ifeq ($(BR2_OPTIMIZE_2),y) TARGET_OPTIMIZATION = -O2 endif ifeq ($(BR2_OPTIMIZE_3),y) TARGET_OPTIMIZATION = -O3 endif ifeq ($(BR2_OPTIMIZE_G),y) TARGET_OPTIMIZATION = -Og endif ifeq ($(BR2_OPTIMIZE_S),y) TARGET_OPTIMIZATION = -Os endif ifeq ($(BR2_DEBUG_1),y) TARGET_DEBUGGING = -g1 endif ifeq ($(BR2_DEBUG_2),y) TARGET_DEBUGGING = -g2 endif ifeq ($(BR2_DEBUG_3),y) TARGET_DEBUGGING = -g3 endif TARGET_CPPFLAGS += -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 TARGET_CFLAGS = $(TARGET_CPPFLAGS) $(TARGET_ABI) $(TARGET_OPTIMIZATION) $(TARGET_DEBUGGING) TARGET_CXXFLAGS = $(TARGET_CFLAGS) TARGET_FCFLAGS = $(TARGET_ABI) $(TARGET_OPTIMIZATION) $(TARGET_DEBUGGING) TARGET_LDFLAGS = $(call qstrip,$(BR2_TARGET_LDFLAGS)) ifeq ($(BR2_BINFMT_FLAT),y) TARGET_CFLAGS += $(if $($(PKG)_FLAT_STACKSIZE),-Wl$(comma)-elf2flt=-s$($(PKG)_FLAT_STACKSIZE),\ -Wl$(comma)-elf2flt) TARGET_CXXFLAGS += $(if $($(PKG)_FLAT_STACKSIZE),-Wl$(comma)-elf2flt=-s$($(PKG)_FLAT_STACKSIZE),\ -Wl$(comma)-elf2flt) TARGET_FCFLAGS += $(if $($(PKG)_FLAT_STACKSIZE),-Wl$(comma)-elf2flt=-s$($(PKG)_FLAT_STACKSIZE),\ -Wl$(comma)-elf2flt) TARGET_LDFLAGS += $(if $($(PKG)_FLAT_STACKSIZE),-Wl$(comma)-elf2flt=-s$($(PKG)_FLAT_STACKSIZE),-Wl$(comma)-elf2flt) endif ifeq ($(BR2_BINFMT_FLAT_SHARED),y) TARGET_LDFLAGS += -mid-shared-library -mshared-library-id=0 TARGET_CFLAGS += -mid-shared-library -mshared-library-id=0 TARGET_FCFLAGS += -mid-shared-library -mshared-library-id=0 TARGET_CXXFLAGS += -mid-shared-library -mshared-library-id=0 endif ifeq ($(BR2_BINFMT_FLAT_SEP_DATA),y) TARGET_LDFLAGS += -msep-data TARGET_CFLAGS += -msep-data TARGET_FCFLAGS += -msep-data TARGET_CXXFLAGS += -msep-data endif ifeq ($(BR2_SSP_REGULAR),y) TARGET_CFLAGS += -fstack-protector TARGET_CXXFLAGS += -fstack-protector TARGET_FCFLAGS += -fstack-protector else ifeq ($(BR2_SSP_STRONG),y) TARGET_CFLAGS += -fstack-protector-strong TARGET_CXXFLAGS += -fstack-protector-strong TARGET_FCFLAGS += -fstack-protector-strong else ifeq ($(BR2_SSP_ALL),y) TARGET_CFLAGS += -fstack-protector-all TARGET_CXXFLAGS += -fstack-protector-all TARGET_FCFLAGS += -fstack-protector-all endif ifeq ($(BR2_TOOLCHAIN_BUILDROOT),y) TARGET_CROSS = $(HOST_DIR)/usr/bin/$(GNU_TARGET_NAME)- else TARGET_CROSS = $(HOST_DIR)/usr/bin/$(call qstrip,$(BR2_TOOLCHAIN_EXTERNAL_PREFIX))- endif # Define TARGET_xx variables for all common binutils/gcc TARGET_AR = $(TARGET_CROSS)ar TARGET_AS = $(TARGET_CROSS)as TARGET_CC = $(TARGET_CROSS)gcc TARGET_CPP = $(TARGET_CROSS)cpp TARGET_CXX = $(TARGET_CROSS)g++ TARGET_FC = $(TARGET_CROSS)gfortran TARGET_LD = $(TARGET_CROSS)ld TARGET_NM = $(TARGET_CROSS)nm TARGET_RANLIB = $(TARGET_CROSS)ranlib TARGET_READELF = $(TARGET_CROSS)readelf TARGET_OBJCOPY = $(TARGET_CROSS)objcopy TARGET_OBJDUMP = $(TARGET_CROSS)objdump ifeq ($(BR2_STRIP_strip),y) STRIP_STRIP_DEBUG := --strip-debug STRIP_STRIP_UNNEEDED := --strip-unneeded STRIP_STRIP_ALL := --strip-all TARGET_STRIP = $(TARGET_CROSS)strip STRIPCMD = $(TARGET_CROSS)strip --remove-section=.comment --remove-section=.note KSTRIPCMD = $(STRIPCMD) $(STRIP_STRIP_UNNEEDED) endif ifeq ($(BR2_STRIP_none),y) TARGET_STRIP = true STRIPCMD = $(TARGET_STRIP) KSTRIPCMD = $(TARGET_STRIP) endif INSTALL := $(shell which install || type -p install) FLEX := $(shell which flex || type -p flex) BISON := $(shell which bison || type -p bison) SED := $(shell which sed || type -p sed) -i -e UNZIP := $(shell which unzip || type -p unzip) -q APPLY_PATCHES = support/scripts/apply-patches.sh $(if $(QUIET),-s) HOST_CPPFLAGS = -I$(HOST_DIR)/usr/include HOST_CFLAGS ?= -O2 HOST_CFLAGS += $(HOST_CPPFLAGS) HOST_CXXFLAGS += $(HOST_CFLAGS) HOST_LDFLAGS += -L$(HOST_DIR)/lib -L$(HOST_DIR)/usr/lib -Wl,-rpath,$(HOST_DIR)/usr/lib # host-intltool should be executed with the system perl, so we save # the path to the system perl, before a host-perl built by Buildroot # might get installed into $(HOST_DIR)/usr/bin and therefore appears # in our PATH. This system perl will be used as INTLTOOL_PERL. export PERL=$(shell which perl) # host-intltool needs libxml-parser-perl, which Buildroot installs in # $(HOST_DIR)/usr/lib/perl, so we must make sure that the system perl # finds this perl module by exporting the proper value for PERL5LIB. export PERL5LIB=$(HOST_DIR)/usr/lib/perl TARGET_CONFIGURE_OPTS = \ PATH=$(BR_PATH) \ AR="$(TARGET_AR)" \ AS="$(TARGET_AS)" \ LD="$(TARGET_LD)" \ NM="$(TARGET_NM)" \ CC="$(TARGET_CC)" \ GCC="$(TARGET_CC)" \ CPP="$(TARGET_CPP)" \ CXX="$(TARGET_CXX)" \ FC="$(TARGET_FC)" \ F77="$(TARGET_FC)" \ RANLIB="$(TARGET_RANLIB)" \ READELF="$(TARGET_READELF)" \ STRIP="$(TARGET_STRIP)" \ OBJCOPY="$(TARGET_OBJCOPY)" \ OBJDUMP="$(TARGET_OBJDUMP)" \ AR_FOR_BUILD="$(HOSTAR)" \ AS_FOR_BUILD="$(HOSTAS)" \ CC_FOR_BUILD="$(HOSTCC)" \ GCC_FOR_BUILD="$(HOSTCC)" \ CXX_FOR_BUILD="$(HOSTCXX)" \ LD_FOR_BUILD="$(HOSTLD)" \ CPPFLAGS_FOR_BUILD="$(HOST_CPPFLAGS)" \ CFLAGS_FOR_BUILD="$(HOST_CFLAGS)" \ CXXFLAGS_FOR_BUILD="$(HOST_CXXFLAGS)" \ LDFLAGS_FOR_BUILD="$(HOST_LDFLAGS)" \ FCFLAGS_FOR_BUILD="$(HOST_FCFLAGS)" \ DEFAULT_ASSEMBLER="$(TARGET_AS)" \ DEFAULT_LINKER="$(TARGET_LD)" \ CPPFLAGS="$(TARGET_CPPFLAGS)" \ CFLAGS="$(TARGET_CFLAGS)" \ CXXFLAGS="$(TARGET_CXXFLAGS)" \ LDFLAGS="$(TARGET_LDFLAGS)" \ FCFLAGS="$(TARGET_FCFLAGS)" \ FFLAGS="$(TARGET_FCFLAGS)" \ PKG_CONFIG="$(PKG_CONFIG_HOST_BINARY)" \ STAGING_DIR="$(STAGING_DIR)" \ INTLTOOL_PERL=$(PERL) TARGET_MAKE_ENV = PATH=$(BR_PATH) HOST_CONFIGURE_OPTS = \ PATH=$(BR_PATH) \ AR="$(HOSTAR)" \ AS="$(HOSTAS)" \ LD="$(HOSTLD)" \ NM="$(HOSTNM)" \ CC="$(HOSTCC)" \ GCC="$(HOSTCC)" \ CXX="$(HOSTCXX)" \ CPP="$(HOSTCPP)" \ OBJCOPY="$(HOSTOBJCOPY)" \ RANLIB="$(HOSTRANLIB)" \ CPPFLAGS="$(HOST_CPPFLAGS)" \ CFLAGS="$(HOST_CFLAGS)" \ CXXFLAGS="$(HOST_CXXFLAGS)" \ LDFLAGS="$(HOST_LDFLAGS)" \ PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 \ PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 \ PKG_CONFIG="$(PKG_CONFIG_HOST_BINARY)" \ PKG_CONFIG_SYSROOT_DIR="/" \ PKG_CONFIG_LIBDIR="$(HOST_DIR)/usr/lib/pkgconfig:$(HOST_DIR)/usr/share/pkgconfig" \ INTLTOOL_PERL=$(PERL) HOST_MAKE_ENV = \ PATH=$(BR_PATH) \ PKG_CONFIG="$(PKG_CONFIG_HOST_BINARY)" \ PKG_CONFIG_SYSROOT_DIR="/" \ PKG_CONFIG_LIBDIR="$(HOST_DIR)/usr/lib/pkgconfig" # This is extra environment we can not export ourselves (eg. because some # packages use that variable internally, eg. uboot), so we have to # explicitly pass it to user-supplied external hooks (eg. post-build, # post-images) EXTRA_ENV = \ PATH=$(BR_PATH) \ BR2_DL_DIR=$(BR2_DL_DIR) \ BUILD_DIR=$(BUILD_DIR) \ BR2_EXTERNAL=$(BR2_EXTERNAL) ################################################################################ # settings we need to pass to configure # does unaligned access trap? BR2_AC_CV_TRAP_CHECK = ac_cv_lbl_unaligned_fail=yes ifeq ($(BR2_i386),y) BR2_AC_CV_TRAP_CHECK = ac_cv_lbl_unaligned_fail=no endif ifeq ($(BR2_x86_64),y) BR2_AC_CV_TRAP_CHECK = ac_cv_lbl_unaligned_fail=no endif ifeq ($(BR2_m68k),y) BR2_AC_CV_TRAP_CHECK = ac_cv_lbl_unaligned_fail=no endif ifeq ($(BR2_powerpc)$(BR2_powerpc64)$(BR2_powerpc64le),y) BR2_AC_CV_TRAP_CHECK = ac_cv_lbl_unaligned_fail=no endif ifeq ($(BR2_ENDIAN),"BIG") BR2_AC_CV_C_BIGENDIAN = ac_cv_c_bigendian=yes else BR2_AC_CV_C_BIGENDIAN = ac_cv_c_bigendian=no endif # AM_GNU_GETTEXT misdetects musl gettext support. # musl currently implements api level 1 and 2 (basic + ngettext) # http://www.openwall.com/lists/musl/2015/04/16/3 ifeq ($(BR2_TOOLCHAIN_USES_MUSL),y) BR2_GT_CV_FUNC_GNUGETTEXT_LIBC = \ gt_cv_func_gnugettext1_libc=yes \ gt_cv_func_gnugettext2_libc=yes endif TARGET_CONFIGURE_ARGS = \ $(BR2_AC_CV_TRAP_CHECK) \ ac_cv_func_mmap_fixed_mapped=yes \ ac_cv_func_memcmp_working=yes \ ac_cv_have_decl_malloc=yes \ gl_cv_func_malloc_0_nonnull=yes \ ac_cv_func_malloc_0_nonnull=yes \ ac_cv_func_calloc_0_nonnull=yes \ ac_cv_func_realloc_0_nonnull=yes \ lt_cv_sys_lib_search_path_spec="" \ $(BR2_AC_CV_C_BIGENDIAN) \ $(BR2_GT_CV_FUNC_GNUGETTEXT_LIBC) ################################################################################ ifeq ($(BR2_ENABLE_LOCALE),y) DISABLE_NLS := else DISABLE_NLS :=--disable-nls endif ifneq ($(BR2_INSTALL_LIBSTDCPP),y) TARGET_CONFIGURE_OPTS += CXX=false endif ifeq ($(BR2_STATIC_LIBS),y) SHARED_STATIC_LIBS_OPTS = --enable-static --disable-shared TARGET_CFLAGS += -static TARGET_CXXFLAGS += -static TARGET_FCFLAGS += -static TARGET_LDFLAGS += -static else ifeq ($(BR2_SHARED_LIBS),y) SHARED_STATIC_LIBS_OPTS = --disable-static --enable-shared else ifeq ($(BR2_SHARED_STATIC_LIBS),y) SHARED_STATIC_LIBS_OPTS = --enable-static --enable-shared endif ifeq ($(BR2_COMPILER_PARANOID_UNSAFE_PATH),y) export BR_COMPILER_PARANOID_UNSAFE_PATH=enabled endif include package/pkg-download.mk include package/pkg-autotools.mk include package/pkg-cmake.mk include package/pkg-luarocks.mk include package/pkg-perl.mk include package/pkg-python.mk include package/pkg-virtual.mk include package/pkg-generic.mk include package/pkg-kconfig.mk include package/pkg-rebar.mk include package/pkg-kernel-module.mk
shibajee/buildroot
package/Makefile.in
in
mit
12,417
config BR2_PACKAGE_A10DISP bool "a10disp" depends on BR2_arm depends on BR2_LINUX_KERNEL help Program to change the display mode of Allwinner ARM SOCs running the linux-sunxi kernel (and not the mainline kernel.) http://github.com/hglm/a10disp comment "a10disp needs a Linux kernel to be built" depends on BR2_arm depends on !BR2_LINUX_KERNEL
shibajee/buildroot
package/a10disp/Config.in
in
mit
360
# Locally calculated sha256 5077405030e8f97a1edd4b86d469466abbc4d32b4a4609e58459347fcd1ba35b a10disp-v0.6.1.tar.gz
shibajee/buildroot
package/a10disp/a10disp.hash
hash
mit
115
################################################################################ # # a10disp # ################################################################################ A10DISP_VERSION = v0.6.1 A10DISP_SITE = $(call github,hglm,a10disp,$(A10DISP_VERSION)) A10DISP_LICENSE = MIT A10DISP_DEPENDENCIES = linux define A10DISP_BUILD_CMDS cp -f $(LINUX_DIR)/include/video/sunxi_disp_ioctl.h $(@D)/ $(TARGET_CC) $(TARGET_CFLAGS) $(@D)/a10disp.c -o $(@D)/a10disp endef define A10DISP_INSTALL_TARGET_CMDS $(INSTALL) -D -m 0755 $(@D)/a10disp $(TARGET_DIR)/usr/bin/a10disp endef $(eval $(generic-package))
shibajee/buildroot
package/a10disp/a10disp.mk
mk
mit
610
Support installation of .a file when doing static linking When doing static linking (i.e ENABLE_SHARED != yes), the acl build logic wasn't installing any library at all, not even the .a file which is needed for static linking. This patch fixes that. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Index: b/include/buildmacros =================================================================== --- a/include/buildmacros +++ b/include/buildmacros @@ -97,7 +97,15 @@ INSTALL_LTLIB_STATIC = \ cd $(TOPDIR)/$(LIBNAME)/.libs; \ - ../$(INSTALL) -m 755 -d $(PKG_DEVLIB_DIR); + ../$(INSTALL) -m 755 -d $(PKG_DEVLIB_DIR); \ + ../$(INSTALL) -m 644 -T old_lib $(LIBNAME).la $(PKG_DEVLIB_DIR); \ + ../$(INSTALL) -m 644 $(LIBNAME).la $(PKG_DEVLIB_DIR)/$(LIBNAME).la ; \ + ../$(INSTALL) -m 755 -d $(PKG_LIB_DIR); \ + ../$(INSTALL) -T so_base $(LIBNAME).la $(PKG_LIB_DIR); \ + if test "x$(PKG_DEVLIB_DIR)" != "x$(PKG_LIB_DIR)" ; then \ + ../$(INSTALL) -S $(PKG_DEVLIB_DIR)/$(LIBNAME).a $(PKG_LIB_DIR)/$(LIBNAME).a; \ + ../$(INSTALL) -S $(PKG_DEVLIB_DIR)/$(LIBNAME).la $(PKG_LIB_DIR)/$(LIBNAME).la; \ + fi INSTALL_MAN = \ @for d in $(MAN_PAGES); do \
shibajee/buildroot
package/acl/0001-support-static-installation.patch
patch
mit
1,171
config BR2_PACKAGE_ACL bool "acl" select BR2_PACKAGE_ATTR help POSIX Access Control Lists, which are used to define more fine-grained discretionary access rights for files and directories. This package also provides libacl. http://savannah.nongnu.org/projects/acl
shibajee/buildroot
package/acl/Config.in
in
mit
283
# Locally calculated after checking pgp signature sha256 179074bb0580c06c4b4137be4c5a92a701583277967acdb5546043c7874e0d23 acl-2.2.52.src.tar.gz
shibajee/buildroot
package/acl/acl.hash
hash
mit
144
################################################################################ # # acl # ################################################################################ ACL_VERSION = 2.2.52 ACL_SOURCE = acl-$(ACL_VERSION).src.tar.gz ACL_SITE = http://download.savannah.gnu.org/releases/acl ACL_INSTALL_STAGING = YES ACL_DEPENDENCIES = attr ACL_CONF_OPTS = --enable-gettext=no ACL_LICENSE = GPLv2+ (programs), LGPLv2.1+ (libraries) ACL_LICENSE_FILES = doc/COPYING doc/COPYING.LGPL # While the configuration system uses autoconf, the Makefiles are # hand-written and do not use automake. Therefore, we have to hack # around their deficiencies by passing installation paths. ACL_INSTALL_STAGING_OPTS = \ prefix=$(STAGING_DIR)/usr \ exec_prefix=$(STAGING_DIR)/usr \ PKG_DEVLIB_DIR=$(STAGING_DIR)/usr/lib \ install-dev install-lib ACL_INSTALL_TARGET_OPTS = \ prefix=$(TARGET_DIR)/usr \ exec_prefix=$(TARGET_DIR)/usr \ install install-lib # The libdir variable in libacl.la is empty, so let's fix it. This is # probably due to acl not using automake, and not doing fully the # right thing with libtool. define ACL_FIX_LIBTOOL_LA_LIBDIR $(SED) "s,libdir=.*,libdir='$(STAGING_DIR)'," \ $(STAGING_DIR)/usr/lib/libacl.la endef ACL_POST_INSTALL_STAGING_HOOKS += ACL_FIX_LIBTOOL_LA_LIBDIR $(eval $(autotools-package))
shibajee/buildroot
package/acl/acl.mk
mk
mit
1,325