From: scd rjcom <scdrjcom@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Porting a vendor specific yocto layer to the buildroot
Date: Mon, 25 Jan 2021 12:33:02 -0800 [thread overview]
Message-ID: <CAGF7ZoZ8MUBbEB=6gXOCCSPNFJcF_Kva=XQducEx_u+O0EeATg@mail.gmail.com> (raw)
In-Reply-To: <877do07r4c.fsf@dell.be.48ers.dk>
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>
next prev parent reply other threads:[~2021-01-25 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2021-01-25 21:15 ` Matthew Weber
2021-01-25 21:17 ` Peter Korsgaard
2021-01-26 8:48 ` Baruch Siach
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='CAGF7ZoZ8MUBbEB=6gXOCCSPNFJcF_Kva=XQducEx_u+O0EeATg@mail.gmail.com' \
--to=scdrjcom@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 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.