Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Set up native build environment for kernel and application dev on target
Date: Wed, 12 Jun 2019 22:13:52 +0200	[thread overview]
Message-ID: <20190612201352.GG2647@scaer> (raw)
In-Reply-To: <1560368655649-0.post@n4.nabble.com>


Bharat,
On 2019-06-12 14:44 -0500, bbacha spake thusly:
> Hi, I am trying to include a GCC or any other compatible toolchain in the
> target image. Also kernel headers for kernel module development. 
> Does buildroot generate image supporting native development on the target?

No, this is not supported, on purpose. See the explanations in the manual:
https://buildroot.org/downloads/manual/manual.html#faq-no-compiler-on-target

Regards,
Yann E. MORIN.

> Any help is appreciated.
> Processor: iMX8MQ (Cortex-A53)
> 
> Thanks,
> Bharat
> 
> 
> 
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-06-12 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 19:44 [Buildroot] Set up native build environment for kernel and application dev on target bbacha
2019-06-12 20:13 ` Yann E. MORIN [this message]
2019-06-12 20:59   ` bbacha

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=20190612201352.GG2647@scaer \
    --to=yann.morin.1998@free.fr \
    --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