* [Buildroot] Porting a vendor specific yocto layer to the buildroot
@ 2021-01-25 8:13 scdrj
2021-01-25 19:28 ` Peter Korsgaard
0 siblings, 1 reply; 6+ messages in thread
From: scdrj @ 2021-01-25 8:13 UTC (permalink / raw)
To: buildroot
How do I port a vendor specific yocto layer to the buildroot?
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Porting a vendor specific yocto layer to the buildroot
2021-01-25 8:13 [Buildroot] Porting a vendor specific yocto layer to the buildroot scdrj
@ 2021-01-25 19:28 ` Peter Korsgaard
2021-01-25 20:33 ` scd rjcom
0 siblings, 1 reply; 6+ messages in thread
From: Peter Korsgaard @ 2021-01-25 19:28 UTC (permalink / raw)
To: buildroot
>>>>> "scdrj" == scdrj <scdrjcom@gmail.com> writes:
> How do I port a vendor specific yocto layer to the buildroot?
One step at a time?
No seriously, it is hard to know without knowing what that layer
does. You will need to have a look at everything it does and add
packages and rootfs overlays / post-build scripts to do the same thing
in Buildroot.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Porting a vendor specific yocto layer to the buildroot
2021-01-25 19:28 ` Peter Korsgaard
@ 2021-01-25 20:33 ` scd rjcom
2021-01-25 21:15 ` Matthew Weber
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: scd rjcom @ 2021-01-25 20:33 UTC (permalink / raw)
To: buildroot
Thank you! I understand that the vendor specific layers have their own
packages and customizations.
I was looking for some generic guidelines to perform this. (Assuming that
all the packages are open source)
It would be great if buildroot documentation will provide some guidelines
to perform the porting of the Yocto layers to Buildroot.
Thanks!
On Mon, Jan 25, 2021 at 11:28 AM Peter Korsgaard <peter@korsgaard.com>
wrote:
> >>>>> "scdrj" == scdrj <scdrjcom@gmail.com> writes:
>
> > How do I port a vendor specific yocto layer to the buildroot?
>
> One step at a time?
>
> No seriously, it is hard to know without knowing what that layer
> does. You will need to have a look at everything it does and add
> packages and rootfs overlays / post-build scripts to do the same thing
> in Buildroot.
>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210125/9028d0dc/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] Porting a vendor specific yocto layer to the buildroot
2021-01-25 20:33 ` scd rjcom
@ 2021-01-25 21:15 ` Matthew Weber
2021-01-25 21:17 ` Peter Korsgaard
2021-01-26 8:48 ` Baruch Siach
2 siblings, 0 replies; 6+ messages in thread
From: Matthew Weber @ 2021-01-25 21:15 UTC (permalink / raw)
To: buildroot
On Mon, Jan 25, 2021 at 2:33 PM scd rjcom <scdrjcom@gmail.com> wrote:
>
> Thank you! I understand that the vendor specific layers have their own packages and customizations.
>
> I was looking for some generic guidelines to perform this. (Assuming that all the packages are open source)
>
> It would be great if buildroot documentation will provide some guidelines to perform the porting of the Yocto layers to Buildroot.
>
It would be an interesting embedded conference presentation :-)
-Matt
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Porting a vendor specific yocto layer to the buildroot
2021-01-25 20:33 ` scd rjcom
2021-01-25 21:15 ` Matthew Weber
@ 2021-01-25 21:17 ` Peter Korsgaard
2021-01-26 8:48 ` Baruch Siach
2 siblings, 0 replies; 6+ messages in thread
From: Peter Korsgaard @ 2021-01-25 21:17 UTC (permalink / raw)
To: buildroot
>>>>> "scd" == scd rjcom <scdrjcom@gmail.com> writes:
Hi,
> Thank you! I understand that the vendor specific layers have their own
> packages and customizations.
> I was looking for some generic guidelines to perform this. (Assuming that
> all the packages are open source)
Well, besides the suggestions I provided already, I don't really know
what else I can tell. In Buildroot, the content of the rootfs comes from
packages, rootfs overlays and post-build scripts, so you need to match
the things that the yocto layer does to these 3 things.
> It would be great if buildroot documentation will provide some guidelines
> to perform the porting of the Yocto layers to Buildroot.
But the Buildroot developers may not be Yocto experts (I'm certainly
not), so I am not sure we are the best people to provide a 1-to-1
mapping between yocto concepts and the Buildroot equivalent.
But if you do, I don't see why we couldn't carry such a cheat sheet in
the manual.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Porting a vendor specific yocto layer to the buildroot
2021-01-25 20:33 ` scd rjcom
2021-01-25 21:15 ` Matthew Weber
2021-01-25 21:17 ` Peter Korsgaard
@ 2021-01-26 8:48 ` Baruch Siach
2 siblings, 0 replies; 6+ messages in thread
From: Baruch Siach @ 2021-01-26 8:48 UTC (permalink / raw)
To: buildroot
Hi scd,
On Mon, Jan 25 2021, scd rjcom wrote:
> Thank you! I understand that the vendor specific layers have their own
> packages and customizations.
>
> I was looking for some generic guidelines to perform this. (Assuming that
> all the packages are open source)
>
> It would be great if buildroot documentation will provide some guidelines
> to perform the porting of the Yocto layers to Buildroot.
Not exactly what you are asking, but these might help you anyway:
https://elinux.org/images/9/9a/Buildroot-vs-Yocto-Differences-for-Your-Daily-Job-Luca-Ceresoli-AIM-Sportline.pdf
https://youtu.be/wCVYQWFIvBs
Thanks to Luca.
baruch
> On Mon, Jan 25, 2021 at 11:28 AM Peter Korsgaard <peter@korsgaard.com>
> wrote:
>
>> >>>>> "scdrj" == scdrj <scdrjcom@gmail.com> writes:
>>
>> > How do I port a vendor specific yocto layer to the buildroot?
>>
>> One step at a time?
>>
>> No seriously, it is hard to know without knowing what that layer
>> does. You will need to have a look at everything it does and add
>> packages and rootfs overlays / post-build scripts to do the same thing
>> in Buildroot.
>>
>> --
>> Bye, Peter Korsgaard
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-01-26 8:48 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-25 8:13 [Buildroot] Porting a vendor specific yocto layer to the buildroot scdrj
2021-01-25 19:28 ` Peter Korsgaard
2021-01-25 20:33 ` scd rjcom
2021-01-25 21:15 ` Matthew Weber
2021-01-25 21:17 ` Peter Korsgaard
2021-01-26 8:48 ` Baruch Siach
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.