buildroot/docs/manual, branch 2018.02.1

docs/manual: use SPDX short identifier for license

2018-04-08T19:30:21+00:00

Signed-off-by: Rahul Bedarkar Signed-off-by: Peter Korsgaard (cherry picked from commit 08bbbe73af0d60ffac4f4476d0583764b81fdfac) Signed-off-by: Peter Korsgaard

docs/manual: pass PARALLEL_JOBS to NINJA_OPTS

2018-04-06T14:42:50+00:00

Ninja understands the `-j` option which defines how many jobs are run in parallel. Signed-off-by: Jörg Krause Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard (cherry picked from commit f7479b538a3e1548172ba256001ebd96f1e7076c) Signed-off-by: Peter Korsgaard

support/check-bin-arch: exclude kernel modules for merged /usr

2018-03-30T20:11:20+00:00

When using a merged /usr, the kernel module path is really /usr/lib/modules, as /lib is a symlink to usr/lib . Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Peter Korsgaard Reviewed-by: Peter Korsgaard Signed-off-by: Peter Korsgaard (cherry picked from commit 1b9a57442d0a234b03585235f516d755372f29b3) Signed-off-by: Peter Korsgaard

spport/check-bin-arch: accept arbitrary per-package ignore paths

2018-03-30T20:11:10+00:00

Some packages (mostly, out-of-tree) may want to install binary blobs for another architecture, outside the locations we currently exclude, like in /opt or whatever... Add support in check-bin-arch to accept any arbitrary location, that individual package can each request to excude from the check, when they are installed. Signed-off-by: "Yann E. MORIN" Cc: Peter Korsgaard Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard (cherry picked from commit 01d90f0d093ff16ab3c1a9466430cee6fb7842d8) Signed-off-by: Peter Korsgaard

docs/manual: add documentation for the "make sdk" target

2018-02-25T22:26:28+00:00

Signed-off-by: Daniel Serpell Signed-off-by: Thomas Petazzoni

rustc: use RUSTC_{HOST,TARGET}_NAME

2018-02-13T22:09:47+00:00

utils/check-package complains as follows: package/rustc/rustc.mk:10: possible typo: RUST_TARGET_NAME -> *RUSTC* package/rustc/rustc.mk:18: possible typo: RUST_HOST_NAME -> *RUSTC* As RUST_{HOST,TARGET}_NAME are related to the Rust compiler, it sounds sensible to rename them to RUSTC_{HOST,TARGET}_NAME. So update all rust related packages to use the new variables. Signed-off-by: Eric Le Bihan Signed-off-by: Thomas Petazzoni

docs/manual: document cargo-based packages

2018-02-05T13:57:48+00:00

Add instructions for adding a package which uses Cargo as build system. [Peter: fix indentation] Signed-off-by: Eric Le Bihan Signed-off-by: Peter Korsgaard

Makefile, manual, website: Bump copyright year

2018-02-01T15:49:41+00:00

Happy 2018! Signed-off-by: Peter Korsgaard

docs/manual: document meson-based packages

2017-12-28T22:09:58+00:00

Add instructions for adding a package which uses the Meson build system. Signed-off-by: Jörg Krause Signed-off-by: Eric Le Bihan Reviewed-by: Yegor Yefremov Signed-off-by: Thomas Petazzoni

Revert "pkg-download: remove explicit PKG_VERSION from github helper"

2017-11-14T12:55:39+00:00

This reverts commit 1e5a8916b2ab4c9c99548fa6fbd4855eee323881. The idea was that the version string can be derived because we know the package name. However, this patch does not account for the fact that $(pkgname) always points to the latest pacakge scanned, which in all other situation we're using it, is the current package, because it is used inside one ot he xxx-inner macros that are $(eval)ualed. So $(pkgname) is evaluated "early" and gets the expected value. However, the github value is not in one of those macros, so it gets evaluated "late", when doing the actual download. So, by that time, $(pkgname) will expand to the last package scanned, which is actuall the manual (without a br2-external tree). That would require that the _SITE variable be assigned with the := assignment operator. This is weird, because that would make it the only variable to require that, but only when using the github helper, which is even less obvious and would cause a lot of trouble... The obvious fixup would seem to be to use $(PKG) instead, because that already contains the upper-case package name that vcan be used as a prefix to variables. However, that does not work either, because we have a check that forbids a trsailing slash in _SITE, check that is done in pacakge/pkg-generic, inside the xxx-inner macro, during the $(eval) call. And at that time, PKG is not yet defined, because it is only defined for an actual recipe. So we can't seem to have a workable solution. So, just revert the patch. Signed-off-by: "Yann E. MORIN" Cc: Marcin Nowakowski Cc: Peter Korsgaard Cc: Arnout Vandecappelle Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard