From: Dimitrios Siganos <dimitris@siganos.org>
To: buildroot@busybox.net
Subject: [Buildroot] uboot-tools and uboot being separate
Date: Thu, 14 Feb 2013 02:15:11 +0000 [thread overview]
Message-ID: <511C48AF.5060106@siganos.org> (raw)
In-Reply-To: <511C1FE8.60103@mind.be>
On 13/02/13 23:21, Arnout Vandecappelle wrote:
> On 14/02/13 00:14, Thomas Petazzoni wrote:
>> Dear Arnout Vandecappelle,
>>
>> On Wed, 13 Feb 2013 23:57:03 +0100, Arnout Vandecappelle wrote:
>>
>>> I've had the same issue once: a patch to add some functionality to
>>> mkimage that I needed both on the host and on the target.
>>
>> Then easy enough; put your patch in package/uboot-tools/. It handles
>> the build and installation of both the host *and* target variant of the
>> U-Boot tools.
>
> In my particular use case (IIRC), the patched mkimage was used to
> process u-boot.bin into a ROM-bootable image. So the same patch had to
> be applied to uboot-tools and uboot. But it was not in fact the same
> patch, because the uboot version was different. What we did in the end
> is just change the uboot-tools site to the same git repository.
Hi Thomas, Arnout,
So if I understand this well, the consensus is that the preferred way to
solve this is to set both packages to point to the same site, method and
version and have two identical copies of the same uboot source code, one
in uboot package and one in uboot-tools package.
That certainly sounds the simplest way although I agree with Arnout that
it is also the strangest and less intuitive approach. Some people will
still raise an eyebrow at such an arrangement.
Regards,
Dimitris
next prev parent reply other threads:[~2013-02-14 2:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 17:22 [Buildroot] uboot-tools and uboot being separate Dimitrios Siganos
2013-02-13 20:20 ` Thomas Petazzoni
2013-02-13 22:57 ` Arnout Vandecappelle
2013-02-13 23:14 ` Thomas Petazzoni
2013-02-13 23:21 ` Arnout Vandecappelle
2013-02-14 2:15 ` Dimitrios Siganos [this message]
2013-02-14 7:57 ` Thomas Petazzoni
2013-02-14 16:18 ` Dimitrios Siganos
2013-02-14 0:09 ` Dimitrios Siganos
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=511C48AF.5060106@siganos.org \
--to=dimitris@siganos.org \
--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