buildroot/docs/manual, branch 2016.05

docs: Fixed syntax error in makedev-syntax example.

2016-05-23T20:44:22+00:00

In the makedev syntax documentation, one of the examples lacks the "mode" value. This patch fixes that example. Signed-off-by: Alan Yaniger Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

Revert "core: add the possibility to provide help for custom rules"

2016-04-17T08:55:37+00:00

This reverts commit 84c825f8e893bfb56847ab4a880c46066a41744f. Turns out that the custom help is not available when the $(O) directory has not been configure yet (i.e. when there is no .config already filled). Rather than trying to work around this limitation with dirty hacks, just revert this feature. After all, this will not prevent an external.mk from providing custom help anyway; it's just not gonna be advertised nor displayed with the main help. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Peter Korsgaard Cc: Jérôme Pouiller Signed-off-by: Peter Korsgaard

core: add the possibility to provide help for custom rules

2016-03-19T15:41:22+00:00

When using a br2-external tree, it is possible (as stated in our manual) to implement whatever arbitrary extra make rules (such as flashing a board, or extracting the rootfs in an NFS export...). Some of those extra rules might be exposed to the user as new entry points that the user can call by itself. However, there is no way for the br2-external to advertise those new rules in the help text. We add the possibility to do so, by adding a new make rule, called help-custom, advertised in our own help info. It is up to the br2-external tree to provide whatever help text is deemed necessary. The format of the help is completely free-form. Note that we need to provide an empty, dummy help-custom rule, since it is always advertised (making it .PHONY does not work). Since this rule is empty, make gently reports that there is "Nothing to be done for `help-local'", which is pretty well fitting when help-local was not provided (either because there's no br2-external tree, or when the br2-external tree does not provide it. Signed-off-by: "Yann E. MORIN" Cc: Jérôme Pouiller Cc: Arnout Vandecappelle Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

docs/manual: document format for specifying licenses

2016-03-06T20:52:57+00:00

Signed-off-by: Rahul Bedarkar [Thomas: minor tweaks for clarity.] Signed-off-by: Thomas Petazzoni

Merge branch 'next'

2016-03-02T20:25:00+00:00

Signed-off-by: Peter Korsgaard

docs/manual: add section about patch licensing

2016-03-01T11:46:58+00:00

Use the same text that is used in COPYING. Signed-off-by: Luca Ceresoli Cc: "Yann E. MORIN" Cc: Arnout Vandecappelle (Essensium/Mind) Cc: Peter Korsgaard Cc: Thomas Petazzoni Cc: Steve Calfee Acked-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

docs/manual: slightly clarify patch licensing

2016-02-25T10:33:00+00:00

Adding a patch is a modification to Buildroot. Thus this sentence might be interpreted as "Patches are released under the Buildroot license". Being a legal matter, the last thing we want is to be ambiguous. Reword the sentence to avoid any misunderstandings. Signed-off-by: Luca Ceresoli Cc: Thomas Petazzoni Acked-by: "Yann E. MORIN" Acked-by: "Yann E. MORIN" Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

docs/manual/contribute.txt: add formatting patches section

2016-02-23T23:04:19+00:00

Thomas P. has sent a few big feedback mails recently that explain how a patch should be formatted. Indeed, this was not explained much in the manual, so add a section that explains how patches should be formatted. This is based heavily on the feedback that Thomas P. gave. Also, specific examples for new packages and version bumps are added. This will allow us to refer to https://buildroot.org/manual.html#submitting-patches in the future instead of composing long mails. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: Yegor Yefremov [Thomas: rewrap to our normal formatting practice.] Signed-off-by: Thomas Petazzoni

docs/manual/contribute.txt: add section for preparing patch series

2016-02-23T23:04:12+00:00

In subsequent patches, we will add more explanation about how to prepare patches, so it will be worthwhile to have a separate section for the series preparation. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: Yegor Yefremov [Thomas: rewrap to our normal formatting practice.] Signed-off-by: Thomas Petazzoni

docs/manual: add "python-package CFFI backend" section

2016-02-23T16:25:06+00:00

Signed-off-by: Yegor Yefremov [Thomas: formatting/redaction tweaks.] Signed-off-by: Thomas Petazzoni