From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Workflow question - separating the distribution from embedded applications
Date: Wed, 20 Jul 2016 14:41:55 +0000 (UTC) [thread overview]
Message-ID: <nmo2jj$mnc$1@ger.gmane.org> (raw)
In-Reply-To: CAOsp8o8U3=xT4u6y33Om125WCk+wPzn_bYbzKEBYbiV=dUqzig@mail.gmail.com
On 2016-07-20, Michael Habibi <mikehabibi@gmail.com> wrote:
> With buildroot, I imagine we can do the same thing since it also
> builds a root filesystem. However I am trying to understand a workflow
> where we could build the distribution's root filesystem of the
> distribution separate from our embedded applications.
We use buildroot to build the root filesystem (including the ipkg
package manager).
Application developers build applications separately and package them
as .ipk packages.
We then install each set of .ipk packages into a JFFS2 filesystem
image. [This is don't on a development host, not on the target.]
We then distribute two images: the kermel+rootfs uImage, and the JFFS2
filesystem image containing all of the applications. The former
rarely gets updated and is common across several products. The latter
gets updated much more frequently and there are various different
flavors of it for different products.
--
Grant Edwards grant.b.edwards Yow! I feel partially
at hydrogenated!
gmail.com
next prev parent reply other threads:[~2016-07-20 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 14:26 [Buildroot] Workflow question - separating the distribution from embedded applications Michael Habibi
2016-07-20 14:41 ` Grant Edwards [this message]
2016-07-20 14:49 ` Michael Habibi
2016-07-20 15:16 ` Michael Habibi
2016-07-20 15:21 ` Grant Edwards
2016-07-20 15:28 ` Grant Edwards
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='nmo2jj$mnc$1@ger.gmane.org' \
--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