From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] How to include prebuilt binary using buildroot?
Date: Wed, 7 Sep 2022 22:30:25 +0200 [thread overview]
Message-ID: <20220907223025.35c93769@windsurf> (raw)
In-Reply-To: <CADYjeSu2TUq3Wkk-AFK8TM=xazH66jKPD8Vg6HA9W3WnX2xymg@mail.gmail.com>
On Wed, 7 Sep 2022 16:40:24 +0200
Sourabh Hegde <hrsourabh011@gmail.com> wrote:
> An application package is not part of buildroot But I am looking for
> possibilities to include it in my image. But there are prebuilt binary
> available for the application in github. Now I am thinking to include them
> by downloading and extracting the downloaded package (.tar.gz). I believe
> this is something possible using Yocto using SRC_URI. But is this feasible
> with buildroot also, may be with BR2_ROOTFS_POST_IMAGE_SCRIPT?
>
> *Or*, using rootfs overlay the only solution?
>
> Can someone please let me know what is the best approach?
Just do a package that is responsible for downloading the package. Its
CONFIGURE_CMDS and BUILD_CMDS will be left empty, and its
INSTALL_TARGET_CMDS will simply install the precompiled binary to
$(TARGET_DIR).
See the Buildroot manual for more details on how to create new packages.
Hope this helps!
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
next prev parent reply other threads:[~2022-09-07 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 14:40 [Buildroot] How to include prebuilt binary using buildroot? Sourabh Hegde
2022-09-07 20:30 ` Thomas Petazzoni via buildroot [this message]
2022-09-07 20:33 ` Grant Edwards
2022-09-07 22:07 ` David Laight
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=20220907223025.35c93769@windsurf \
--to=buildroot@buildroot.org \
--cc=hrsourabh011@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox