buildroot-novena/Makefile, branch 2012.11.1

Update for 2012.11.1

2013-01-03T20:43:39Z

Signed-off-by: Peter Korsgaard

Update for 2012.11

2012-12-03T00:33:09Z

Signed-off-by: Peter Korsgaard

unexport PKG_CONFIG_SYSROOT_DIR

2012-12-03T00:32:28Z

If this is not done then pkg-config can get confused. Thomas and Arnout really deserve the credit for this - I just did the testing. Signed-off-by: Charles Manning Signed-off-by: Peter Korsgaard

{rand,allyes}packageconfig: ensure legacy test options don't get enabled

2012-12-02T02:13:05Z

The legacy BR2_PACKAGE_* options in Config.in.legacy are not supposed to be user selectable, so {rand,allyes}packageconfig shouldn't enable them. Signed-off-by: Peter Korsgaard

Update for 2012.11-rc2

2012-12-01T06:59:02Z

Signed-off-by: Peter Korsgaard

Makefile: fix thread libraries stripping

2012-11-30T21:59:40Z

Strip libthread_db the same as any other library, but strip libpthread with --strip-debug. See the relevant mailing list discussion [1] for additional details. [1] http://lists.busybox.net/pipermail/buildroot/2012-October/060126.html Signed-off-by: Richard Braun Signed-off-by: Peter Korsgaard

pkg-infra: introduce errors for legacy API

2012-11-30T20:06:40Z

As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Update for 2012.11-rc1

2012-11-17T22:55:55Z

Signed-off-by: Peter Korsgaard

Allow to run severals post build scripts instead of only one

2012-11-17T16:23:59Z

Using severals post build scripts is usefull to share script between severals boards/projects. [Peter: fix trailing spaces in Config.in] Signed-off-by: Philippe Reynes Signed-off-by: Peter Korsgaard

Warn the user about the usage of output/target as the root filesystem

2012-11-17T16:12:49Z

A very common mistake done by our users is that they use output/target/ directory as their root filesystem. Even though this is loudly documented in our Buildroot manual, people don't read documentation, so it is not sufficient. This patch adds a text file named output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM which explains why output/target isn't appropriate to use as the root filesystem. The process is: * At the beginning of the build, right after the skeleton has been copied, support/misc/target-dir-warning.txt is copied to output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM * In the filesystem images creation code, this file is removed before launching fakeroot, and restored right after that, so that this file is not present in the generated root filesystem images. Note that the file has not been added to the default skeleton for two reasons: * It would have annoying to have in our source tree a file named in capital letters inside system/skeleton/ * The proposed way works even if the user uses a custom skeleton. [Peter: fixed typo] Signed-off-by: Thomas Petazzoni Cc: Juha Lumme Acked-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard