All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danomi Manchego <danomimanchego123@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] call with hooks
Date: Thu, 6 Jan 2022 09:20:50 -0500	[thread overview]
Message-ID: <CANxTyt5nhTZpB4VadypNDom3g4bdGPKj4cHnXumRT7eAUxS-Tg@mail.gmail.com> (raw)
In-Reply-To: <cfeacd99-c264-d440-5145-009440450287@mind.be>

Hu Arnout,

Thanks for the explanation.  I feel better now :)

Danomi -


On Thu, Jan 6, 2022 at 4:39 AM Arnout Vandecappelle <arnout@mind.be> wrote:
>
>
>
> On 05/01/2022 17:20, Danomi Manchego wrote:
> >   Hello all,
> >
> > I noticed a possible inconsistency, and thought I should post it.
> > Looking at places where buildroot uses hooks:
> >
> > $ grep -r '$(hook))$(sep)' .
>
> [snip]
> >
> > Notice that the one hit in Makefile uses "$($(hook))$(sep)" while the
> > hits in pkg-generic.mk use "$(call $(hook))$(sep)".  My Make-fu isn't
> > powerful enough to understand if there is an actual problem - should
> > there be a "call" in the Makefile line?  The general syntax for call
> > is "$(call variable,param,param,…)" so I don't follow what the extra
> > call in $(call $(hook) is doing for us.
>
>   Historical accident.
>
>   The person who first introduced the hooks back in the days didn't realize that
> $(call ...) is not for "something that looks like a function", but rather it is
> for "whenever you want to pass arguments". Reviewers also didn't realize this
> and just applied, and when more hooks were added later they copied the pattern.
>
>   Regards,
>   Arnout
>
> >
> > Thanks,
> > Danomi -
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
> >
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-06 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 16:20 [Buildroot] call with hooks Danomi Manchego
2022-01-06  9:39 ` Arnout Vandecappelle
2022-01-06 14:20   ` Danomi Manchego [this message]

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=CANxTyt5nhTZpB4VadypNDom3g4bdGPKj4cHnXumRT7eAUxS-Tg@mail.gmail.com \
    --to=danomimanchego123@gmail.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.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 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.