* [Buildroot] Workflow question - separating the distribution from embedded applications
@ 2016-07-20 14:26 Michael Habibi
2016-07-20 14:41 ` Grant Edwards
0 siblings, 1 reply; 6+ messages in thread
From: Michael Habibi @ 2016-07-20 14:26 UTC (permalink / raw)
To: buildroot
We are looking at switching to a buildroot-based distribution from our
current option for our embedded device. Right now, we have a giant
source tree that combines both the distribution and our applications
to build a root filesystem that contains everything. This makes things
simple as everything is co-located in one source tree. However it
complicates and extends the build because we must rebuild the
distribution with our code in order to build a complete image.
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. A workflow where
the application developers only have to build their code and not the
whole distribution, and can 'insert' their applications into the
distribution somehow and just regenerate the final images. I know I
can create packages for the embedded applications and separate them in
repos, but it seems that we still have to have the developers do the
distribution build in that scenario.
Are there some common workflows that I can use as a guide or basis in this area?
Thanks for your help
Michael
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Workflow question - separating the distribution from embedded applications
2016-07-20 14:26 [Buildroot] Workflow question - separating the distribution from embedded applications Michael Habibi
@ 2016-07-20 14:41 ` Grant Edwards
2016-07-20 14:49 ` Michael Habibi
0 siblings, 1 reply; 6+ messages in thread
From: Grant Edwards @ 2016-07-20 14:41 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] Workflow question - separating the distribution from embedded applications
2016-07-20 14:41 ` Grant Edwards
@ 2016-07-20 14:49 ` Michael Habibi
2016-07-20 15:16 ` Michael Habibi
0 siblings, 1 reply; 6+ messages in thread
From: Michael Habibi @ 2016-07-20 14:49 UTC (permalink / raw)
To: buildroot
Great, thanks for this info. I'll look into this in more detai.
On Wed, Jul 20, 2016 at 9:41 AM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> 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
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Workflow question - separating the distribution from embedded applications
2016-07-20 14:49 ` Michael Habibi
@ 2016-07-20 15:16 ` Michael Habibi
2016-07-20 15:21 ` Grant Edwards
0 siblings, 1 reply; 6+ messages in thread
From: Michael Habibi @ 2016-07-20 15:16 UTC (permalink / raw)
To: buildroot
I forgot to ask - are you using the same cross-tools, host-tools and
toolchain for your applications as your distribution? For example,
your libraries, autotools, gcc, etc. If so, how do you ensure you
don't get leakage from the wrong host tools if your applications are
built separately outside of the buildroot directories? Thanks again.
On Wed, Jul 20, 2016 at 9:49 AM, Michael Habibi <mikehabibi@gmail.com> wrote:
> Great, thanks for this info. I'll look into this in more detai.
>
> On Wed, Jul 20, 2016 at 9:41 AM, Grant Edwards
> <grant.b.edwards@gmail.com> wrote:
>> 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
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Workflow question - separating the distribution from embedded applications
2016-07-20 15:16 ` Michael Habibi
@ 2016-07-20 15:21 ` Grant Edwards
2016-07-20 15:28 ` Grant Edwards
0 siblings, 1 reply; 6+ messages in thread
From: Grant Edwards @ 2016-07-20 15:21 UTC (permalink / raw)
To: buildroot
On 2016-07-20, Michael Habibi <mikehabibi@gmail.com> wrote:
> I forgot to ask - are you using the same cross-tools, host-tools and
> toolchain for your applications as your distribution? For example,
> your libraries, autotools, gcc, etc.
Yes, we use the same toolchain for both buildroot and application
development (the toolchain is built outside of buildroot using ct-ng).
> If so, how do you ensure you don't get leakage from the wrong host
> tools if your applications are built separately outside of the
> buildroot directories?
I don't know what you mean by "leakage".
The autotools that are used for application development are those from
the development host. We haven't had any problems due to that (yet),
but it is a weak point in the workflow, since they aren't
archived/controlled the way the toolchain is.
--
Grant Edwards grant.b.edwards Yow! Today, THREE WINOS
at from DETROIT sold me a
gmail.com framed photo of TAB HUNTER
before his MAKEOVER!
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] Workflow question - separating the distribution from embedded applications
2016-07-20 15:21 ` Grant Edwards
@ 2016-07-20 15:28 ` Grant Edwards
0 siblings, 0 replies; 6+ messages in thread
From: Grant Edwards @ 2016-07-20 15:28 UTC (permalink / raw)
To: buildroot
On 2016-07-20, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2016-07-20, Michael Habibi <mikehabibi@gmail.com> wrote:
> Yes, we use the same toolchain for both buildroot and application
> development (the toolchain is built outside of buildroot using ct-ng).
>
>> If so, how do you ensure you don't get leakage from the wrong host
>> tools if your applications are built separately outside of the
>> buildroot directories?
>
> I don't know what you mean by "leakage".
By "leakage" he apparently means accidentally linking in host
libraries instead of target libraries.
That doesn't happen because
1) The toolchain doesn't search the host library directories.
2) If it did, the libraries it would find are the wrong architecture.
--
Grant Edwards grant.b.edwards Yow! An Italian is COMBING
at his hair in suburban DES
gmail.com MOINES!
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-07-20 15:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-20 14:26 [Buildroot] Workflow question - separating the distribution from embedded applications Michael Habibi
2016-07-20 14:41 ` Grant Edwards
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox