From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Renaming uboot-utils
Date: Mon, 17 Dec 2007 13:13:08 +0200 [thread overview]
Message-ID: <1674566773.20071217131308@gmail.com> (raw)
In-Reply-To: <4762E496.1040806@student.utwente.nl>
Hello Koen,
Friday, December 14, 2007, 10:16:22 PM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Andy Wilcox schreef:
>> Since uboot-utils builds a native binary (mkImage) it should really be
>> called
>> uboot-utils-native.
> That part makes sense. FWIW, we already have a uboot-mkimage-native
> recipe in OE.
>> My motivation is (a) I'd really like to build a few tools from uboot
>> which are cross-compiled
> And now you're talking about uboot-utils-cross, not uboot-utils-native
I had a look at mkimage source, it appears to generate
target-independent format (does htonl() and friends), so it at least
can stay uboot-utils-native as the actual commit made it.
More interestingly is that both u-boot and u-boot-utils-native stage
mkimage, and that's all what u-boot-utils-native does actually, so we
have redundancy here.
> regards,
> Koen
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-12-17 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 4:41 RFC: Renaming uboot-utils Andy Wilcox
2007-12-14 16:30 ` Philip Balister
2007-12-14 18:41 ` Khem Raj
2007-12-14 20:16 ` Koen Kooi
2007-12-15 13:14 ` Leon Woestenberg
2007-12-17 11:13 ` Paul Sokolovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-17 3:14 Andy Wilcox
2007-12-17 11:09 ` Paul Sokolovsky
[not found] ` <47668695.5010701@protium.com>
2007-12-17 15:02 ` Paul Sokolovsky
2007-12-17 18:23 ` Andy Wilcox
2007-12-17 21:31 ` Koen Kooi
2007-12-17 22:19 ` Paul Sokolovsky
2007-12-17 22:41 ` Marcin Juszkiewicz
2007-12-17 21:25 ` Rod Whitby
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=1674566773.20071217131308@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.