All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] dev-manual: some minor cleanups to "Pre-Built Libraries"
Date: Tue, 24 Jun 2025 09:50:18 +0200	[thread overview]
Message-ID: <DAULKYBT3POY.38V8CSIV0F8K0@bootlin.com> (raw)
In-Reply-To: <b88499e3-e0d1-5aff-490c-ae13c2dbfb31@crashcourse.ca>

On Sun Jun 22, 2025 at 12:59 PM CEST, Robert P. J. Day wrote:
>
>   * Add note about new URL for FHS 3.0.
>   * Add wildcard for "INHIBIT_" variable.
>   * Fix font for ${PN}.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/documentation/dev-manual/prebuilt-libraries.rst b/documentation/dev-manual/prebuilt-libraries.rst
> index a05f39ca1..077184657 100644
> --- a/documentation/dev-manual/prebuilt-libraries.rst
> +++ b/documentation/dev-manual/prebuilt-libraries.rst
> @@ -22,6 +22,13 @@ To summarize, a versioned library must meet two conditions:
>  This section shows how to deal with both versioned and unversioned
>  pre-built libraries.
>
> +.. note::
> +
> +   In the shared library article referenced above, the link to the current
> +   version of the Filesystem Hierarchy Standard (FHS) is out of date;
> +   the current FHS 3.0 release can be found
> +   `here <https://refspecs.linuxfoundation.org/FHS_3.0/index.html>`__.

Not sure adding a note to say a link is outdated is the good approach.
Instead update the link above?

>  Versioned Libraries
>  ===================
>
> @@ -79,7 +86,7 @@ To write a recipe to use such a library in your system:
>  -  The vendor will typically ship release builds without debugging symbols.
>     Avoid errors by preventing the packaging task from stripping out the symbols
>     and adding them to a separate debug package. This is done by setting the
> -   ``INHIBIT_`` flags shown below.
> +   ``INHIBIT_*`` flags shown below.
>
>  The complete recipe would look like this::
>
> @@ -170,7 +177,7 @@ as follows::
>  The modifications cause the ``.so`` file to be the real library
>  and unset :term:`FILES_SOLIBSDEV` so that no libraries get packaged into
>  ``${PN}-dev``. The changes are required because unless :term:`PACKAGES` is changed,
> -``${PN}-dev`` collects files before `${PN}`. ``${PN}-dev`` must not collect any of
> +``${PN}-dev`` collects files before ``${PN}``. ``${PN}-dev`` must not collect any of

Can you send this in a separate patch?

>  the files you want in ``${PN}``.
>
>  Finally, loadable modules, essentially unversioned libraries that are linked


Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2025-06-24  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-22 10:59 [PATCH] dev-manual: some minor cleanups to "Pre-Built Libraries" Robert P. J. Day
2025-06-23 14:16 ` [docs] " Quentin Schulz
2025-06-23 15:19   ` Robert P. J. Day
2025-06-24  7:50 ` Antonin Godard [this message]
2025-06-24  8:19   ` Robert P. J. Day
2025-06-24  8:28     ` Antonin Godard
2025-06-24  8:31   ` Robert P. J. Day
2025-06-24  8:35     ` Antonin Godard
2025-06-24  8:43       ` Robert P. J. Day

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=DAULKYBT3POY.38V8CSIV0F8K0@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.