Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Pohanka <xhpohanka@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] why to have separate uboot-tools?
Date: Mon, 24 Jun 2013 13:18:37 +0200	[thread overview]
Message-ID: <51C82B0D.2040105@gmail.com> (raw)
In-Reply-To: <51C82A53.90403@zacarias.com.ar>

Dne 24.6.2013 13:15, Gustavo Zacarias napsal(a):
> On 06/24/2013 07:55 AM, Jan Pohanka wrote:
>
>> Hi all,
>>
>> currently I'm trying to customize buildroot a bit to allow it to be used
>> by my colleagues as a base of their development environment.
>> I have noticed that there is separate package for u-boot-tools (mkimage,
>> etc.) Can please someone tell me why these tools are not installed from
>> u-boot package defined in bootloaders section?
>>
>> Once we use our own u-boot with its own tools (uflash from TI) I need to
>> alter two packages and also u-boot sources are downloaded two times.
>> I can prepare a patch to use just u-boot in bootloaders section, but the
>> question is if it is not worthless...
> Hi.
> Because maybe you are just building an uImage and not the bootloader for
> your target?
> Hence saving time building a complete bootloader and (also) maybe you
> lack the customized bootloader source to build a complete target which
> would preclude you from building just the tools which don't have
> board-specific bits. (not saying this is nice, but it happens sometimes)
> Regards.
>
Hi,
I'm reconsidering it once again and it seems that current approach is 
probably the best... anyway thank you for answer.

regards

  reply	other threads:[~2013-06-24 11:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 10:55 [Buildroot] why to have separate uboot-tools? Jan Pohanka
2013-06-24 11:15 ` Gustavo Zacarias
2013-06-24 11:18   ` Jan Pohanka [this message]
2013-06-24 16:46 ` Arnout Vandecappelle

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=51C82B0D.2040105@gmail.com \
    --to=xhpohanka@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