From: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Nicolas Escande <nico.escande-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Makefile: allow to install libfdt without building executables
Date: Wed, 26 Jul 2023 18:49:43 -0600 [thread overview]
Message-ID: <CAPnjgZ1OZBF6YWUCrKUW1FEHaR4EzZMGVn00k62vcQSA91ubzg@mail.gmail.com> (raw)
In-Reply-To: <20230726144336.677135-1-nico.escande-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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?
>
> diff --git a/Makefile b/Makefile
> index 784e2f8..c0b68a2 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -238,7 +238,7 @@ install-bin: all $(SCRIPTS)
> $(INSTALL_PROGRAM) $(BIN) $(DESTDIR)$(BINDIR)
> $(INSTALL_SCRIPT) $(SCRIPTS) $(DESTDIR)$(BINDIR)
>
> -install-lib: all
> +install-lib: libfdt
> @$(VECHO) INSTALL-LIB
> $(INSTALL) -d $(DESTDIR)$(LIBDIR)
> $(INSTALL_LIB) $(LIBFDT_lib) $(DESTDIR)$(LIBDIR)
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-07-27 0:49 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 [this message]
[not found] ` <CAPnjgZ1OZBF6YWUCrKUW1FEHaR4EzZMGVn00k62vcQSA91ubzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-27 8:45 ` Nicolas Escande
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=CAPnjgZ1OZBF6YWUCrKUW1FEHaR4EzZMGVn00k62vcQSA91ubzg@mail.gmail.com \
--to=sjg-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nico.escande-Re5JQEeQqe8AvxtiuMwx3w@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).