[Buildroot] uboot-tools and uboot being separate

Dimitrios Siganos dimitris at siganos.org
Thu Feb 14 02:15:11 UTC 2013

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.


More information about the buildroot mailing list