[Buildroot] [PATCH 2/6] docs/manual: indicate how to handle BR2_TOOLCHAIN_HAS_THREADS_NPTL

[Thomas De Schampheleire]

On Thu, Feb 13, 2014 at 2:22 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
> ---
>  docs/manual/adding-packages-directory.txt | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
> index 754a145..e1299c3 100644
> --- a/docs/manual/adding-packages-directory.txt
> +++ b/docs/manual/adding-packages-directory.txt
> @@ -235,7 +235,13 @@ use in the comment.
>
>  * thread support
>  ** Dependency symbol: +BR2_TOOLCHAIN_HAS_THREADS+
> -** Comment string: +threads+
> +** Comment string: +threads+ (unless +BR2_TOOLCHAIN_HAS_THREADS_NPTL+
> +   is also needed, in which case, specifying only +NPTL threads+ is
> +   sufficient)
> +
> +* NPTL thread support
> +** Dependency symbol: +BR2_TOOLCHAIN_HAS_THREADS_NPTL+
> +** Comment string: +NPTL threads+
>
>  * RPC support
>  ** Dependency symbol: +BR2_TOOLCHAIN_HAS_NATIVE_RPC+

Should we maybe use 'NPTL' rather than 'NPTL threads' to make the
string shorter? (we want to fit in 80chars).
It's true that it's a bit more cryptic, but so is RPC, wchar, etc.
The biggest point is that a user can go to the Toolchain menu and
recognize a string that matches, in this case the keyword NPTL.

Best regards,
Thomas