Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libbytesize: remove pcre2 runtime dependency
Date: Thu, 25 Mar 2021 16:39:42 +0100	[thread overview]
Message-ID: <20210325163942.7d8ecb69@windsurf.home> (raw)
In-Reply-To: <c1c09133e8e3d70f0458fd0da622062f@agner.ch>

On Thu, 25 Mar 2021 15:40:36 +0100
Stefan Agner <stefan@agner.ch> wrote:

> Hmm, I think I don't understand how runtime/compile time dependencies
> work in buildroot.
> 
> I read this section:
> https://buildroot.org/downloads/manual/manual.html#_gettext_integration_and_interaction_with_packages
> 
> But I think i got this wrong, gettext in that case is only a runtime
> dependency.

Yes, and because it's only a runtime dependency, we need to make sure
it is enabled in the configuration (which the "select" does), but we
don't need to ensure it is built *before* a certain package (which
<pkg>_DEPENDENCIES does).

> Is there a way to have something as compile time dependency but not a
> runtime dependency?

No, because it is fairly uncommon to have something that is a compile
time dependency but not necessary at runtime. Do you have specific
examples in mind ?

For example, in your patch, libbytesize links against the libpcre2
library. So there is a build time dependency, as libpcre2 needs to be
built before libbytesize, for the link of libbytesize to succeed. But
there is also a runtime dependency: libpcre2.so needs to be on the
target.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2021-03-25 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 14:17 [Buildroot] [PATCH] package/libbytesize: remove pcre2 runtime dependency Stefan Agner
2021-03-25 14:22 ` Baruch Siach
2021-03-25 14:40   ` Stefan Agner
2021-03-25 15:39     ` Thomas Petazzoni [this message]
2021-03-25 16:41       ` Stefan Agner
2021-03-28 14:52         ` Yann E. MORIN

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=20210325163942.7d8ecb69@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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