Porting a vendor specific yocto layer to the buildroot
How do I port a vendor specific yocto layer to the buildroot?
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
Quoted 3 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"scdrj" == scdrj <[email protected]> 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.
Signature · 1 line
Bye, Peter Korsgaard
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!
Quoted 6 lines · Peter Korsgaard
Quoted 3 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"scdrj" == scdrj <[email protected]> writes:
How do I port a vendor specific yocto layer to the buildroot?
One step at a time?
Quoted 8 lines
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>
Quoted 7 lines · scd rjcom
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"scd" == scd rjcom <[email protected]> writes:
Hi,
Quoted 5 lines
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.
Quoted 2 lines
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.
Signature · 1 line
Bye, Peter Korsgaard
Hi scd,
Quoted 8 lines · scd rjcom
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
Quoted 21 lines
Quoted 6 lines · Peter Korsgaard
Quoted 3 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"scdrj" == scdrj <[email protected]> writes:
How do I port a vendor specific yocto layer to the buildroot?
One step at a time?
Quoted 8 lines
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
Signature · 3 lines
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -