devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Makefile: allow to install libfdt without building executables
Date: Thu, 27 Jul 2023 10:45:40 +0200	[thread overview]
Message-ID: <CUCTN344O5PH.EOH73270TFQC@syracuse> (raw)
In-Reply-To: <CAPnjgZ1OZBF6YWUCrKUW1FEHaR4EzZMGVn00k62vcQSA91ubzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu Jul 27, 2023 at 2:49 AM CEST, Simon Glass wrote:
> On Wed, 26 Jul 2023 at 08:44, Nicolas Escande <nico.escande-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > When we only need the libfdt calling the target install-lib also builds the
> > executables listed in $(BINS) because this target depends on all
> > Instead lets make install-lib only depend on libfdt.
> >
> > Signed-off-by: Nicolas Escande <nico.escande-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > ---
> >  Makefile | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
>
> But why would you just want the libs?
>
Well some projects like qemu & uboot from the top of my head use the libfdt and
do not always need/build the dtc that goes with it.
It's cleary very corner case but I don't think it harms anyone doing so :)

  parent reply	other threads:[~2023-07-27  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 14:43 [PATCH] Makefile: allow to install libfdt without building executables Nicolas Escande
     [not found] ` <20230726144336.677135-1-nico.escande-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-27  0:49   ` Simon Glass
     [not found]     ` <CAPnjgZ1OZBF6YWUCrKUW1FEHaR4EzZMGVn00k62vcQSA91ubzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-27  8:45       ` Nicolas Escande [this message]
2023-07-29  3:08   ` David Gibson

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=CUCTN344O5PH.EOH73270TFQC@syracuse \
    --to=nico.escande-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).