Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Cc: herb.kuta@lge.com
Subject: Re: [yocto-docs][PATCH] ref-manual: mention PREPROCESS_RELOCATE_DIRS variable
Date: Fri, 6 Sep 2019 13:32:10 +0200	[thread overview]
Message-ID: <20190906113210.GA1530@jama> (raw)
In-Reply-To: <20190812195140.900-1-Martin.Jansa@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2988 bytes --]

On Mon, Aug 12, 2019 at 07:51:40PM +0000, Martin Jansa wrote:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>

ping

> ---
>  documentation/ref-manual/ref-classes.xml   |  5 ++++-
>  documentation/ref-manual/ref-variables.xml | 21 +++++++++++++++++++++
>  2 files changed, 25 insertions(+), 1 deletion(-)
> 
> diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
> index ece47e757..159efb3b1 100644
> --- a/documentation/ref-manual/ref-classes.xml
> +++ b/documentation/ref-manual/ref-classes.xml
> @@ -413,7 +413,10 @@
>          <filename>cross</filename>, and
>          <filename>cross-canadian</filename> recipes to change
>          <filename>RPATH</filename> records within binaries in order to make
> -        them relocatable.
> +        them relocatable. To extend the list of directories where it searches
> +        for binaries to relocate, you can set
> +        <link linkend='var-PREPROCESS_RELOCATE_DIRS'><filename>PREPROCESS_RELOCATE_DIRS</filename></link>
> +        variable in your recipe.
>      </para>
>  </section>
>  
> diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
> index 9470a780a..5ac766658 100644
> --- a/documentation/ref-manual/ref-variables.xml
> +++ b/documentation/ref-manual/ref-variables.xml
> @@ -11424,6 +11424,27 @@
>              </glossdef>
>          </glossentry>
>  
> +        <glossentry id='var-PREPROCESS_RELOCATE_DIRS'><glossterm>PREPROCESS_RELOCATE_DIRS</glossterm>
> +            <info>
> +                PREPROCESS_RELOCATE_DIRS[doc] = "List of extra directories where to search for binaries which should be relocatable."
> +            </info>
> +            <glossdef>
> +                <para role="glossdeffirst">
> +<!--                <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
> +                    List of extra directories with binaries.
> +                </para>
> +
> +                <para>
> +                    <filename>PREPROCESS_RELOCATE_DIRS</filename> is used by
> +                    chrpath.bbclass to allow extending the list where it searches
> +                    for binaries. By default it searches in:
> +                    ${bindir} ${sbindir} ${base_sbindir} ${base_bindir} ${libdir} ${base_libdir} ${libexecdir}
> +                    Thus, <filename>PREPROCESS_RELOCATE_DIRS</filename> usually doesn't
> +                    need to be set withing recipes.
> +                </para>
> +            </glossdef>
> +        </glossentry>
> +
>          <glossentry id='var-PRIORITY'><glossterm>PRIORITY</glossterm>
>              <info>
>                  PRIORITY[doc] = "Indicates the importance of a package.  The default value is 'optional'.  Other standard values are 'required', 'standard', and 'extra'."
> -- 
> 2.17.1
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  parent reply	other threads:[~2019-09-06 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 19:51 [yocto-docs][PATCH] ref-manual: mention PREPROCESS_RELOCATE_DIRS variable Martin Jansa
2019-08-12 20:02 ` ✗ patchtest: failure for " Patchwork
2019-09-06 11:32 ` Martin Jansa [this message]
2019-12-11 17:32   ` [yocto-docs][PATCH] " Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190906113210.GA1530@jama \
    --to=martin.jansa@gmail.com \
    --cc=herb.kuta@lge.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox