Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 15:21:07 +0000 (UTC)	[thread overview]
Message-ID: <nmo4t3$rs$1@ger.gmane.org> (raw)
In-Reply-To: CAOsp8o8jNLdhNoyDQByuLF40Z1_jockTV5rYcXF_wyGwRZMLhw@mail.gmail.com

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!

  reply	other threads:[~2016-07-20 15:21 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
2016-07-20 14:49   ` Michael Habibi
2016-07-20 15:16     ` Michael Habibi
2016-07-20 15:21       ` Grant Edwards [this message]
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='nmo4t3$rs$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