buildroot-novena/Makefile, branch 2012.11_rc2

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

New top-level directory: system

2012-11-04T11:51:08Z

This directory groups the following elements: * the default root filesystem skeleton * the default device tables * the Config.in options for system configuration (UART port for getty, system hostname, etc.) * the make rules to apply the system configuration options Even though the skeleton and device tables could have lived in fs/, it would have been strange to have the UART, system hostname and other related options into fs/. A new system/ directory makes more sense. As a consequence, this patch also removes target/Makefile.in, which has become useless in the process. [Peter: fixup TARGET_SKELETON settings / documentation to match] Signed-off-by: Thomas Petazzoni Acked-by: Yann E. MORIN Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Support KERNEL_ARCH for AArch64

2012-11-02T20:08:50Z

The architecture tuple is 'aarch64', but the kernel people decided to call it 'arm64', so we have to do some mungling to get the kernel architecture name from the Buildroot architecture name. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

Makefile: Remove more pkgconfig files

2012-10-04T21:03:48Z

The pkgconfig files are located in /usr/lib/pkgconfig and /usr/share/pkgconfig directories. However, only /usr/lib/pkgconfig is removed when no development files are needed in the target filesystem. Remove pkgconfig directory from $(TARGET_DIR)/usr/share as well if BR2_HAVE_DEVFILES is not set. Signed-off-by: Valentine Barshak Signed-off-by: Peter Korsgaard

Remove the Xtensa architecture

2012-09-20T20:31:08Z

As stated in commit 555c2585bf28c3ef71f6d2dcdd983d17a19892af, the Xtensa architecture has been introduced in 2009 and never changed since its initial introduction. It requires some special handling that is a bit annoying, and despite our call to the initial developers, and the announcement of the deprecation of the architecture during the 2012.05, nothing has happened. Therefore, drop support for this architecture. Signed-off-by: Thomas Petazzoni Acked-by: me Signed-off-by: Peter Korsgaard