From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Paolo Bonzini <bonzini@gnu.org>,
Glauber Costa <glommer@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Filip Navara <filip.navara@gmail.com>,
Jan Ondrej <ondrejj@salstar.sk>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Fix checksum writing in signboot.sh
Date: Sun, 02 Aug 2009 21:30:43 -0500 [thread overview]
Message-ID: <4A764BD3.1070003@codemonkey.ws> (raw)
In-Reply-To: <60A4FD72-56B3-4670-BB82-1CE1878467CA@suse.de>
Alexander Graf wrote:
>
> On 02.08.2009, at 13:15, Avi Kivity <avi@redhat.com> wrote:
>
>> On 08/02/2009 01:25 PM, Filip Navara wrote:
>>>> While the patch is good, the code is unreadable. Can we mandate
>>>> python for
>>>> such tricks?
>>>>
>>>
>>> No, please, no! Throwing additional tools at the problem is only going
>>> to make it worse for Windows users. I'm not happy with using sh script
>>> as it already added dependency on coreutils, but at least that's easy
>>> to install. Python is a nightmare compared to that.
>>>
>>
>> Is Python really so difficult to install under Windows? How many
>> times do you have to click 'Next'?
>>
>> Note that Windows users can usually use prebuilt binaries, so the
>> 'Next' nightmare only affects a small number of Windows developers.
>>
>>> BTW, for years in ReactOS we had a way to build host tools with host
>>> CC and these tools were written in plain ordinary C. This worked great
>>> for both Windows and Linux builds and also for cross-compiling.
>>>
>>
>> But then you have to write those tools in C, which is annoying.
>
> Right. In fact we just switched from C to sh for portability reasons.
The problem is with cross compilers. Our build system is based around a
single tool chain and we only do feature probing, sanity checking,
cflags modifications, etc. on the target tool chain. If we build and
run a C program using the host compiler (which is needed in order to be
able to run the program), things get complicated quickly.
sh is preferred because it's a minimal dependency. I would be concerned
about perl or python for the main build because those tools aren't
available by default for windows. For something like a rom where we
ship a default binary, as long as we detected the appropriate tools and
disabled the build, I think it would be more reasonable.
> I really think we should just make the current code work as is and be
> done. The script is pretty small and really readable IMHO.
We're going to have to revisit this for pc-bios since it depends on perl
and it has a similar rom signing tool (biossums). It's far more
sophisticated though and it's currently implemented in C. It may make
sense to rewrite that tool in python/perl and have a single tool used
for all of our roms.
We don't need to do this now though.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-08-03 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 9:48 [Qemu-devel] [PATCH] Fix checksum writing in signboot.sh Alexander Graf
2009-08-02 10:04 ` [Qemu-devel] " Avi Kivity
2009-08-02 10:25 ` Filip Navara
2009-08-02 11:15 ` Avi Kivity
2009-08-02 11:58 ` Alexander Graf
2009-08-02 12:21 ` Avi Kivity
2009-08-02 21:29 ` [Qemu-devel] " Sebastian Herbszt
2009-08-03 2:30 ` Anthony Liguori [this message]
2009-08-03 6:12 ` [Qemu-devel] " Paolo Bonzini
2009-08-03 12:55 ` Avi Kivity
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=4A764BD3.1070003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=bonzini@gnu.org \
--cc=filip.navara@gmail.com \
--cc=glommer@redhat.com \
--cc=ondrejj@salstar.sk \
--cc=qemu-devel@nongnu.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.