Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: Re: [Buildroot] How to include prebuilt binary using buildroot?
Date: Wed, 7 Sep 2022 20:33:24 -0000 (UTC)	[thread overview]
Message-ID: <tfav6k$uda$1@ciao.gmane.io> (raw)
In-Reply-To: CADYjeSu2TUq3Wkk-AFK8TM=xazH66jKPD8Vg6HA9W3WnX2xymg@mail.gmail.com

On 2022-09-07, Sourabh Hegde <hrsourabh011@gmail.com> wrote:
>
> I think this is rather a basic question:
>
> An application package is not part of buildroot But I am looking for
> possibilities to include it in my image.

I configured buildroot to run a post-build script. In that script, I
copy various files to various places in the output/target tree. I'm
admittedly


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?
>
> Thanks in advance
>
> -
> Sourabh
>
> _______________________________________________
> 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

  parent reply	other threads:[~2022-09-07 20:33 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
2022-09-07 20:33 ` Grant Edwards [this message]
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='tfav6k$uda$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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