buildroot-novena/Makefile, branch 2013.02_rc2

Update for 2013.02-rc2

2013-02-19T21:05:42+00:00

Signed-off-by: Peter Korsgaard

Update for 2013.02-rc1

2013-02-10T10:07:12+00:00

Signed-off-by: Peter Korsgaard

rootfs-overlay: also exclude .empty files

2013-02-08T21:11:24+00:00

This makes it possible to put empty directories in the overlay. Thanks to Aras Vaichas for pointing that out. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: Samuel Martin Signed-off-by: Peter Korsgaard

Add a post-image script mechanism

2013-02-08T20:46:13+00:00

Just like we have a post-build script mechanism that gets executed after the build of all packages but before the creation of the filesystem images, let's introduce a post-image script mechanism, that gets executed once all filesystem images have been generated. This can for example be used to call a tool building a firmware image from different images generated by Buildroot, or automatically extract the tarball root filesystem image into some location exported by NFS, or any other custom action. [Peter: fix image script check] Signed-off-by: Thomas Petazzoni Tested-by: "Yann E. MORIN" Acked-by: "Yann E. MORIN" Acked-by: Luca Ceresoli Acked-by: Samuel Martin Signed-off-by: Peter Korsgaard

Make savedefconfig save to a configured file.

2013-02-05T20:43:51+00:00

Store BR2_DEFCONFIG in .config, and use it to update the original input defconfig file after updating the configuration. When a config is created by using the BR2_DEFCONFIG=... option, this is saved in the .config file; later runs of savedefconfig will update that same location. It is also possible to configure this place in the interactive configuration. The BR2_DEFCONFIG value itself is not saved into the generated defconfig, since Kconfig considers it at its default. This is intentional, to avoid hard-coding an absolute path in the defconfig. It will anyway be set again when the defconfig is used with the 'make BR2_DEFCONFIG=... defconfig' command. As a side-effect of this change, the *config options have been moved out of the BR2_HAVE_DOT_CONFIG condition. This doesn't make any functional difference, because the .config is still not read for the *config targets. However, the defconfig and savedefconfig targets do need to include .config now, which makes them slightly slower. [Peter: slightly tweak help text] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: Luca Ceresoli Signed-off-by: Peter Korsgaard

target/generic: add filesystem overlay option

2013-02-05T20:35:33+00:00

The filesystem overlay is a tree that is copied over the target fs after building everything - which is currently usually done in the post-build script. [Peter: don't ignore missing directories] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: Luca Ceresoli Signed-off-by: Peter Korsgaard

Makefile: rename cross target -> toolchain

2013-01-15T08:44:30+00:00

- Use a more descriptive name, the same of the "toolchain" directory. - Add missing dependencies to be able to successfully use the target right after the configuration. - Move to a better position. - Documentation it in the help target. - Use toolchain target in the world target Signed-off-by: Fabio Porcedda Reviewed-by: Markos Chandras Acked-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: Samuel Martin Signed-off-by: Peter Korsgaard

Integration with Buildroot Toolchain Eclipse plugin

2013-01-14T15:33:30+00:00

The Eclipse plugin at https://github.com/mbats/eclipse-buildroot-toolchain-plugin allows users of Eclipse to easily use the toolchain available in Buildroot. To do so, this plugin reads ~/.buildroot-eclipse.toolchains, which contains the list of Buildroot toolchains available on the system, and then offer those toolchains to compile Eclipse projects. In order to interface with this plugin, this commit adds an option that allows the user to tell whether (s)he wants the Buildroot project toolchain to be visible under this Eclipse plugin. It simply adds a line in this ~/.buildroot-eclipse.toolchains file. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

Makefile: don't export O to the environment

2013-01-14T09:04:21+00:00

Several projects use the kernel style O= syntax to build out of tree, and atleast uClibc doesn't check that it was explictly passed on the command line, so setting it in the environment breaks the build. Signed-off-by: Peter Korsgaard

Makefile: use newly-introduced BUILDROOT_CONFIG

2013-01-13T22:14:24+00:00

Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard