[Buildroot] How to include prebuilt binary using buildroot?

[Buildroot] How to include prebuilt binary using buildroot?

[Sourabh Hegde]

[-- Attachment #1.1: Type: text/plain, Size: 617 bytes --]

Hello All,

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. 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

[-- Attachment #1.2: Type: text/html, Size: 799 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] How to include prebuilt binary using buildroot?

[Thomas Petazzoni via buildroot]

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

Re: [Buildroot] How to include prebuilt binary using buildroot?

[Grant Edwards]

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

Re: [Buildroot] How to include prebuilt binary using buildroot?

[David Laight]

From: Grant Edwards
> Sent: 07 September 2022 21:33
> 
> 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

We just use fakeroot again to expand the cpio archive
buildroot generates, delete some stuff, copy some more files in,
and then archive it back up.

That also means we can change our bits without having
to rerun all the buildroot makefiles.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot