Buildroot - Revision history

Jcmvbkbc: move modern buildroot xtensa overlay configuration option to the top

2018-04-24T20:38:56Z

move modern buildroot xtensa overlay configuration option to the top

← Older revision		Revision as of 20:38, 24 April 2018
Line 32:		Line 32:
	** BR2_xtensa: must be selected when building for Xtensa		** BR2_xtensa: must be selected when building for Xtensa
	** BR2_XTENSA_CUSTOM: must be set when a custom core variant is used		** BR2_XTENSA_CUSTOM: must be set when a custom core variant is used
			** release 2017.08 and newer:
			*** BR2_XTENSA_OVERLAY_FILE: path to the overlay file. May be relative or absolute, may also be an URL.
	** release 2017.05 and older:		** release 2017.05 and older:
	*** BR2_XTENSA_CUSTOM_NAME: must specify custom core variant name. This name is used to derive configuration overlay file name.		*** BR2_XTENSA_CUSTOM_NAME: must specify custom core variant name. This name is used to derive configuration overlay file name.
	*** BR2_XTENSA_OVERLAY_DIR: path to the directory with overlay file. May be relative to the Buildroot directory (specified as $(TOPDIR)/...) or the build directory (specified as $(BASE_DIR)/...)		*** BR2_XTENSA_OVERLAY_DIR: path to the directory with overlay file. May be relative to the Buildroot directory (specified as $(TOPDIR)/...) or the build directory (specified as $(BASE_DIR)/...)
	** release 2017.08 and newer:
	*** BR2_XTENSA_OVERLAY_FILE: path to the overlay file. May be relative or absolute, may also be an URL.
	* Toolchain submenu: select toolchain component versions and options. Many packages depend on presence of specific options, like IPv6 support or WCHAR support. Usually a package that cannot be built with current settings will indicate missing options in the menu.		* Toolchain submenu: select toolchain component versions and options. Many packages depend on presence of specific options, like IPv6 support or WCHAR support. Usually a package that cannot be built with current settings will indicate missing options in the menu.
	* Target packages submenu: select individual packages and libraries that will be built and installed to the rootfs.		* Target packages submenu: select individual packages and libraries that will be built and installed to the rootfs.

Jcmvbkbc: drop special uclinux case

2018-04-24T20:35:17Z

drop special uclinux case

← Older revision		Revision as of 20:35, 24 April 2018
Line 7:		Line 7:
	* latest buildroot release archive: links in the Download section at http://buildroot.net/download.html		* latest buildroot release archive: links in the Download section at http://buildroot.net/download.html
	* mainline buildroot git tree: <code>git clone git://git.buildroot.net/buildroot</code>		* mainline buildroot git tree: <code>git clone git://git.buildroot.net/buildroot</code>
	* for the buildroot with uClinux support see [[uClinux]]

	Using tip of the cloned git tree for work is usually a bad idea, basing development branches on known releases (marked by tags) would give more predictable results.		Using tip of the cloned git tree for work is usually a bad idea, basing development branches on known releases (marked by tags) would give more predictable results.

Jcmvbkbc: add latest features and document changed overlay location specifier

2017-07-28T21:51:38Z

add latest features and document changed overlay location specifier

← Older revision		Revision as of 21:51, 28 July 2017
Line 33:		Line 33:
	** BR2_xtensa: must be selected when building for Xtensa		** BR2_xtensa: must be selected when building for Xtensa
	** BR2_XTENSA_CUSTOM: must be set when a custom core variant is used		** BR2_XTENSA_CUSTOM: must be set when a custom core variant is used
	** BR2_XTENSA_CUSTOM_NAME: must specify custom core variant name. This name is used to derive configuration overlay file name.		** release 2017.05 and older:
	** BR2_XTENSA_OVERLAY_DIR: path to the directory with overlay file. May be relative to the Buildroot directory (specified as $(TOPDIR)/...) or the build directory (specified as $(BASE_DIR)/...)		*** BR2_XTENSA_CUSTOM_NAME: must specify custom core variant name. This name is used to derive configuration overlay file name.
			*** BR2_XTENSA_OVERLAY_DIR: path to the directory with overlay file. May be relative to the Buildroot directory (specified as $(TOPDIR)/...) or the build directory (specified as $(BASE_DIR)/...)
			** release 2017.08 and newer:
			*** BR2_XTENSA_OVERLAY_FILE: path to the overlay file. May be relative or absolute, may also be an URL.
	* Toolchain submenu: select toolchain component versions and options. Many packages depend on presence of specific options, like IPv6 support or WCHAR support. Usually a package that cannot be built with current settings will indicate missing options in the menu.		* Toolchain submenu: select toolchain component versions and options. Many packages depend on presence of specific options, like IPv6 support or WCHAR support. Usually a package that cannot be built with current settings will indicate missing options in the menu.
	* Target packages submenu: select individual packages and libraries that will be built and installed to the rootfs.		* Target packages submenu: select individual packages and libraries that will be built and installed to the rootfs.
Line 63:		Line 66:

	= Features by release =		= Features by release =

			== 2017.08 ==
			* overlay overhaul: now overlay may be compressed, may have arbitrary name and may be specified as an URL
			* overlay is applied to linux
			* overlay is applied to U-Boot

			== 2017.05 ==
			* build xtensa linux kernel uImage

			== 2016.05 ==
			* support noMMU xtensa cores

	== 2014.11 ==		== 2014.11 ==

Jcmvbkbc: We now can build linux and U-Boot as a part of buildroot

2017-07-27T00:40:00Z

We now can build linux and U-Boot as a part of buildroot

← Older revision		Revision as of 00:40, 27 July 2017
Line 2:		Line 2:

	= Getting Buildroot and other prerequisites =		= Getting Buildroot and other prerequisites =
	Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system. Buildroot can generate a cross-compilation toolchain ~~and~~ a root filesystem~~. Building~~ linux kernel and bootloader ~~for arbitrary Xtensa core with the Buildroot is currently not supported~~.		Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system. Buildroot can generate a cross-compilation toolchain, a root filesystem, linux kernel and the U-Boot bootloader.
	== Getting Buildroot ==		== Getting Buildroot ==
	Depending on whether buildroot tree with full history is needed for development or not either release tarball should be downloaded or git tree cloned.		Depending on whether buildroot tree with full history is needed for development or not either release tarball should be downloaded or git tree cloned.

Jcmvbkbc: add uclinux link

2015-10-06T03:34:35Z

add uclinux link

← Older revision		Revision as of 03:34, 6 October 2015
Line 7:		Line 7:
	* latest buildroot release archive: links in the Download section at http://buildroot.net/download.html		* latest buildroot release archive: links in the Download section at http://buildroot.net/download.html
	* mainline buildroot git tree: <code>git clone git://git.buildroot.net/buildroot</code>		* mainline buildroot git tree: <code>git clone git://git.buildroot.net/buildroot</code>
			* for the buildroot with uClinux support see [[uClinux]]

	Using tip of the cloned git tree for work is usually a bad idea, basing development branches on known releases (marked by tags) would give more predictable results.		Using tip of the cloned git tree for work is usually a bad idea, basing development branches on known releases (marked by tags) would give more predictable results.

Jcmvbkbc: add 'features by release' for the Buildroot

2015-03-12T14:54:55Z

add 'features by release' for the Buildroot

← Older revision		Revision as of 14:54, 12 March 2015
Line 60:		Line 60:
	($(ARCH)-unknown-linux-gnu) Toolchain prefix		($(ARCH)-unknown-linux-gnu) Toolchain prefix
	External toolchain C library (glibc/eglibc)		External toolchain C library (glibc/eglibc)

			= Features by release =

			== 2014.11 ==
			* fix 'dangerous relocation: call8: call target out of range' linker bug
			* fix 'Error: jump target out of range; no usable trampoline found' and 'Error: operand 1 of 'j' has out of range ' assembler bugs

			== 2014.08 ==
			* fix xtensa linker segfault on linking linux modules

			== 2014.05 ==
			* fixes for building with -mtext-section-literals
			* assembler trampolines (able to assemble files with jumps longer than 128K)
			* fixes for 'dangerous relocation: call8: misaligned call target' and 'dangerous relocation: overflow after relaxation' linker bugs

			== 2014.02 ==
			* fix overlay application to gcc

			== 2012.11 ==
			* xtensa in the Buildroot mainline

Jcmvbkbc: Add the Buildroot instructions

2015-03-12T13:20:32Z

Add the Buildroot instructions

@@ Line 1: / Line 1: @@
 This page describes the steps to build a toolchain and root file system for a specific processor configuration based on the latest release of Buildroot.
-== Getting Buildroot and other prerequisites ==
+= Getting Buildroot and other prerequisites =
-* Buildroot
+Using tip of the cloned git tree for work is usually a bad idea, basing development branches on known releases (marked by tags) would give more predictable results.
-== Configuring and building Buildroot ==
+== Xtensa core overlay file ==
-The first step is to configure Buildroot <code>make menuconfig</code>. Select Xtensa, and for a custom configuration, provide a core name and absolute path to the directory containing the overlay file. The overlay file name must be xtensa_<CORE_NAME>.tar, where core name can be any user selected name.
+= Configuring and building Buildroot =
- Target Architecture (Xtensa)
+The Buildroot may be built in the same directory as its source (in-tree) or in a separate directory (out-of-tree). Building out-of-tree is usually cleaner and involves less actions when several configurations need to be built.
- Target Architecture Variant (Custom Xtensa processor configuration)
+Adding parameter O=''build-dir-path'' to make controls out-of-tree Buildroot configuration/building.
-Finally, run <code>make</code> to build the toolchain and root file system. For more information about Buildroot, please also read the documents provided by Buildroot under http://buildroot.net/docs.html.
+For more information about Buildroot, please also read the documents provided by Buildroot under http://buildroot.net/docs.html.
-== Build Buildroot with Crosstool-NG ==
+== Configuring the Buildroot ==
 Using the Crosstool-NG toolchain allows to build a version of a Buildroot image based on GlibC instead of uClibc. In the current version, Buildroot cannot build Crosstool-NG for Xtensa directly, but can be configured to use it as an ''external'' toolchain. The first step is to build and install Crosstool-NG, so Buildroot can use it to compile the root file system. More information to build Crosstool-NG for Xtensa can be found under [[Crosstool-NG]]. Assuming Crosstool-NG is installed in 'ABSOLUTE_PATH_TO_XTOOLS', which is typically <code>$HOME/x-tools</code>, you can make the following additional configurations changes in Buildroot:

Chris at 21:48, 18 March 2013

2013-03-18T21:48:24Z

← Older revision		Revision as of 21:48, 18 March 2013
Line 18:		Line 18:

	Finally, run <code>make</code> to build the toolchain and root file system. For more information about Buildroot, please also read the documents provided by Buildroot under http://buildroot.net/docs.html.		Finally, run <code>make</code> to build the toolchain and root file system. For more information about Buildroot, please also read the documents provided by Buildroot under http://buildroot.net/docs.html.

			== Build Buildroot with Crosstool-NG ==

			Using the Crosstool-NG toolchain allows to build a version of a Buildroot image based on GlibC instead of uClibc. In the current version, Buildroot cannot build Crosstool-NG for Xtensa directly, but can be configured to use it as an ''external'' toolchain. The first step is to build and install Crosstool-NG, so Buildroot can use it to compile the root file system. More information to build Crosstool-NG for Xtensa can be found under [[Crosstool-NG]]. Assuming Crosstool-NG is installed in 'ABSOLUTE_PATH_TO_XTOOLS', which is typically <code>$HOME/x-tools</code>, you can make the following additional configurations changes in Buildroot:

			Toolchain --->
			Toolchain type (External toolchain)
			Toolchain (Custom toolchain)
			Toolchain origin (Pre-installed toolchain)
			(ABSOLUTE_PATH_TO_XTOOLS) Toolchain path
			($(ARCH)-unknown-linux-gnu) Toolchain prefix
			External toolchain C library (glibc/eglibc)

Chris: New page: This page describes the steps to build a toolchain and root file system for a specific processor configuration based on the latest release of Buildroot. == Getting Buildroot and other pr...

2013-03-14T17:21:20Z

New page: This page describes the steps to build a toolchain and root file system for a specific processor configuration based on the latest release of Buildroot. == Getting Buildroot and other pr...

New page

This page describes the steps to build a toolchain and root file system for a specific processor configuration based on the latest release of Buildroot.

== Getting Buildroot and other prerequisites ==

* Buildroot
*: Download the latest release from http://buildroot.net/download.html or clone the development tree <code>git clone git://git.buildroot.net/buildroot</code>
* Xtensa overlay file
*: The overlay file includes patches for toolchain tools, such as compiler, assembler, and debugger, that are required to support a specific Xtensa processor configuration. Tensilica provides such an overlay as part of the processor download, however, it needs to be reformatted to match the specific format required by buildroot. For a script to convert the overlay file, and additional information, please go to [[Toolchain Overlay File]]. The current version of buildroot requires that the overlay file name has the format xtensa_<CORE_NAME>.tar, where CORE_NAME can be any user selected name.

== Configuring and building Buildroot ==

The first step is to configure Buildroot <code>make menuconfig</code>. Select Xtensa, and for a custom configuration, provide a core name and absolute path to the directory containing the overlay file. The overlay file name must be xtensa_<CORE_NAME>.tar, where core name can be any user selected name.

Target Architecture (Xtensa)
Target Architecture Variant (Custom Xtensa processor configuration)
(PROCESSOR_NAME) Custom Xtensa processor configuration name
(ABSOLUTE_OVERLAY_PATH) Overlay directory for custom configuration

Finally, run <code>make</code> to build the toolchain and root file system. For more information about Buildroot, please also read the documents provided by Buildroot under http://buildroot.net/docs.html.