buildroot/Makefile, branch 2017.08

Update for 2017.08

2017-09-01T23:17:43+00:00

Signed-off-by: Peter Korsgaard

Update for 2017.08-rc3

2017-08-23T21:38:05+00:00

Signed-off-by: Thomas Petazzoni

Update for 2017.08-rc2

2017-08-11T20:36:39+00:00

Signed-off-by: Thomas Petazzoni

Update for 2017.08-rc1

2017-08-02T21:00:13+00:00

Signed-off-by: Thomas Petazzoni

Makefile: add alldefconfig target

2017-07-25T21:06:58+00:00

It is used by Kconfig's merge_config.sh. No alldefpackageconfig is added, since it's rather pointless: it would only enable busybox. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

Makefile: refactor *config targets

2017-07-25T21:06:49+00:00

The rules for the *config targets are all very similar, so factor them together using $@. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

system: provide package-wide system variables and macros

2017-07-22T19:51:17+00:00

Some macros, soon some variables, currently defined in the skeleton are going to be used by other packages. Some of those variables will be used as Makefile conditions (e.g. in ifeq() conditions), so they *must* be defined before being used. Since the skeleton package, starting with an 's', is included quite late, those variables would not be available to most packages. Offload the existing macros into the new system/system.mk file, that is included early, before any package is. Rename the macros to appropriate names. Future commits will add new macros and variables in that file. Signed-off-by: "Yann E. MORIN" Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

core: introduce "sdk" target to make a relocatable SDK

2017-07-22T12:35:13+00:00

We use a separate make target to build a relocatable SDK. We first sanitize the RPATH in host tree. Next we also sanitize the staging tree. Therefore "sdk" must depend on world. Sanitizing staging is not really needed, in the sense that any rpath in there is simply not going to be used. We want to sanitize staging for the following reasons: - To avoid leaking references to the original output directory. This way, we can validate that the SDK is relocatable by running a simple "grep -r ${BASE_DIR} ${HOST_DIR}". Obviously RPATH sanitization is not sufficient (e.g. also the references to source files have to be stripped), but it's a step in the right direction. This reason is obviously only relevant for the SDK. - To make sure that when an executable is copied to target that it actually executes correctly. Since within Buildroot we never copy stuff from staging to target, this is clearly only relevant for the SDK. Finally we install the script "relocate-sdk.sh" into the top directory of the SDK (HOST_DIR) and the SDK location path is stored in the file "HOST_DIR/share/buildroot/sdk-location"- Signed-off-by: Wolfgang Grandegger Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

core: sanitize RPATH in target tree before copying the overlay

2017-07-20T20:47:04+00:00

We sanitize the RPATH of ELF files in the target tree to deal with stupid packages that don't correctly use --prefix/DESTDIR and that end up putting the full absolute build-time directory in the RPATH. We do it before copying the overlay and calling the post-build script. The user is completely responsible for what happens in the last two steps, and it should never be touched by us. Signed-off-by: Wolfgang Grandegger Signed-off-by: Thomas Petazzoni

Makefile: properly create $(HOST_DIR)/usr compatibility symlink

2017-07-10T15:45:57+00:00

Up to now we created the $(HOST_DIR)/usr compatibility symlink as part of the creation of $(HOST_DIR) itself. However, when the user specifies a custom BR2_HOST_DIR, it is possible that the directory already exists so this rule will never trigger. Therefore, add an explicit rule for creating $(HOST_DIR)/usr and add this rule to the dependencies of the dirs target. HOST_DIR itself goes back to the standard rule for directories. The order-only dependency of STAGING_DIR isn't needed any more either: HOST_DIR is implicitly created if needed by mkdir -p, and we don't need to trigger the HOST_DIR rule any more if the directory already exists. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni