All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jameson Collins <jameson.collins@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Defining a package with no dependencies
Date: Thu, 4 Aug 2022 12:53:33 +0200	[thread overview]
Message-ID: <20220804125333.11005bc9@windsurf> (raw)
In-Reply-To: <CACoTCHeTKbTU4QSBs4qtyUXKDNOH+5u4Y-rGhy4QeuvK=kAENw@mail.gmail.com>

Hello,

On Wed, 3 Aug 2022 19:30:07 -0400
Jameson Collins <jameson.collins@gmail.com> wrote:

> If I have a package that doesn't build anything, doesn't depend on
> anything, and doesn't have anything depending on it, is it possible to tell
> buildroot to build this package without first building the toolchain?

You could do:

<pkg>_ADD_TOOLCHAIN_DEPENDENCY = NO

but that's normally reserved for packages that are part of the
toolchain build.

> An example of a package like this might be the `flash-my-board` recipe that
> is shown in the manual.  Yes, in this case the package doesn't make any
> sense unless boot.bin existed, but you can see how it might be useful to
> have a package that performs a task and not necessarily generate a build
> product.

flash-my-board inside the manual is *not* a package. It's just an
example in the external.mk, to show that external.mk can be used to
provide additional custom make targets. It has nothing to do with a
package.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-04 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 23:30 [Buildroot] Defining a package with no dependencies Jameson Collins
2022-08-04 10:53 ` Thomas Petazzoni via buildroot [this message]
2022-08-08 12:02   ` Jameson Collins
2022-08-04 15:06 ` Arnout Vandecappelle

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=20220804125333.11005bc9@windsurf \
    --to=buildroot@buildroot.org \
    --cc=jameson.collins@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.