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:28:40 +0000 (UTC)	[thread overview]
Message-ID: <nmo5b7$8um$1@ger.gmane.org> (raw)
In-Reply-To: nmo4t3$rs$1@ger.gmane.org

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!

      reply	other threads:[~2016-07-20 15:28 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
2016-07-20 15:28         ` Grant Edwards [this message]

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='nmo5b7$8um$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